We don't currently intend to backport any new features to LTS releases. The goal is only to maintain them with essential bug fixes and compatibility updates.
Send your project to supportpfa@construct.net and we'll take a look. Note most such recent cases have been due to an issue this guide covers.
If you run in to a problem please file an issue following all the guidelines.
You can already do a similar thing if you add instance variables to act as signal parameters.
All we did is change an audio playback workaround that was already used in some cases, to be used in more cases.
There are no changes in this update that should affect project compatibility. If you believe there is a new problem, please file an issue following all the guidelines.
Currently as the image formats are chosen on export, there isn't a way to choose which to use in preview - so at the moment it uses the default option which is WebP. Given how good AVIF is though we may update that in future, or make a project setting for the image formats.
See the section "Using it in Construct".
See this guide which might help.
It does property renaming but keeps the existing name, e.g. UglifyJS will rename obj.apples to obj._$apples$_. This can help you figure out why some code doesn't work in 'Advanced' minify mode, as it still renames properties, but you can still read the code.
You can export in 'bundle only' mode and then use an external tool - including UglifyJS - to minify yourself with custom options like source maps.
The addon is already updated in the latest beta release.
It's not possible to show an error for features that are not compatible either. Doing so means using a time machine to predict what changes are made in future and ensure a useful error message is shown for them.
It's not possible to detect features that are not compatible, as the older version doesn't know they even exist.
You should expect beta releases to be occasionally broken. If you don't want to deal with that, stick to stable releases and don't use beta releases.
It's impossible to reliably allow projects saved in newer versions to be opened in older versions. What happens if you use a new feature which the older version doesn't support? There's no solution to that.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.