Usually we update documentation at the next stable release. In the mean time look for the available APIs in the Chrome debugger, starting with an array at inst.effects.
You can do this in Construct 3 as well! Look up function maps.
Mirror/flip is just a negative size, and the set mirrored/flipped actions in the manual describe this. There are events fired for keyboard input, that's the normal way for detecting key presses in JavaScript.
Most of what you've suggested is already possible, such as keyboard input and mirroring. Also Construct's distance and random expressions just use the equivalent Math functions in JavaScript, so there doesn't seem to be any point in adding them when you can do things like Math.random() directly.
If there was an ARM Linux version of NW.js, it might be possible with that, but AFAIK none exists yet. At the moment by far the easiest way to run a game on the Raspberry Pi is with the Chromium browser. You should be able to add web games to the desktop too.
It's possible to make an SDK for them, but right now the feature only supports a very narrow set of options to complete the tour, so it's probably not going to be more widely useful until later down the line.
If you think you've found an issue in Construct please report it here: github.com/Scirra/Construct-3-bugs
We can't help without the requested information.
It's the 2nd item down the list in the main menu.
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.
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.