The last release cycle added support for Android App Bundles, and the new worker mode, improved PNG compression, and faster remote previews are all significant changes that aren't just bug fixes and involved a lot of work! Regardless, there's more new coming in the next beta cycle.
Some things are not documented for a good reason (e.g. we intend to remove it), and other things aren't yet supported for a good reason (e.g. we intend to overhaul the feature before adding APIs for it).
I have to point out that the entire reason there are separate scripting APIs is so we can update them separately. For example we can overhaul the engine without breaking projects using scripting. Exposing the internal engine classes to scripting completely undermines this and risks causing compatibility nightmares. A worst case scenario is that so many people use this, that we cannot implement major new features or optimisations because it would break too many projects. I can't stop you publishing this addon, but I must strongly advise that nobody use this.
Note worker mode is documented in the scripting section of the manual under JavaScript in Construct. Also if you create a new project and choose to start with script, it leaves worker mode off, so you can still directly access DOM methods like alert.
I'd rather require addons are compatible than let addon developers get away with making ones which are broken with certain settings.
It's only enabled by default for new projects. Existing projects won't see any change. It was also enabled by default for a while last year before it got disabled again due to a Chrome bug, so it's already been pretty widely tested.
Yes, look at this text effects example.
I'm afraid it's simply impossible to help people reporting problems, unless there is enough information for us to be able to investigate. Otherwise all we can do is rely on telepathy, which is notoriously unreliable. We provide detailed guidelines to ensure customers are able to provide all the information we need to be able to help with any problems they have encountered.
It's impossible to help from just this information. If you think there is a problem with Construct please file a bug following all the guidelines: https://github.com/Scirra/Construct-3-bugs
If you think you've found a bug please file an issue following all the guidelines (we need all that information to be able to help): github.com/Scirra/Construct-3-bugs
As far as we're aware storage is working fine for everyone else.
The fix was for the runtime, that's the only place worker mode applies. It doesn't affect the editor.
Yes, Construct 3 is backwards compatible with C2 projects. Just drag and drop in your .capx file!
We have no power to remove things from people's Steam libraries. C2 will always be there until you remove it yourself.
The discount can only be used once, on your first payment (annual or monthly). Your discount will be biggest if you use it for an annual payment.
Construct 2 will not be getting any new features, it's on the path to being retired. You can however use Construct 3 to build Construct 2 Cordova exports, or import your project and use it to build it. Construct 3 is cheaper than some standalone build services, and you get both a full game development tool and a build service as well.
Yes, you can build APKs ready for publishing right from Construct 3 without having to install anything. For iOS you can get Xcode projects ready for testing and publishing (Apple's publishing restrictions make it difficult to do more).
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.