Construct is also a JS engine, that's the point.
If you don't like the idea of the project, well... you don't have to follow it 🤷
Since the introduction of JavaScript coding in Construct back in 2019, we've been aiming to make Construct also good for coding, in addition to the event sheet system. We haven't, and aren't, neglecting the event sheet feature. We know lots of people use event sheets. But we'd like to draw some more attention to the coding feature and show what it's capable of. That's what this project is about.
As explained in part 1 this tutorial isn't intended to go in to detail about the quirks of old legacy features. If you stick to let/const then you don't need to learn about all those quirks.
Please report any issues here following all the guidelines, as we need all that information to be able to help: github.com/Scirra/Construct-3-bugs
I haven't heard of anyone else reporting such problems - maybe try disabling any browser extensions in case one is interfering with Construct? It's hard to help without more details, but if you can report any problems here following the guidelines we'll investigate: github.com/Scirra/Construct-3-bugs
We already get far more feature requests than we can possibly act on. Further, you can always take any specific part of Construct, and suggest dozens of improvements, or even radical overhauls. As much as I'd love to do it all it's just impossible with the resources we have.
For example the current approach of hiding instance variables is pretty simple and was straightforward to implement. Adding more UI controls to expand and collapse stuff makes it more complicated (I don't think we've developed a suitable UI control, and so we'd need to make one; developing new UIs is particularly time consuming), and raises usability questions (why did you hide it if you want to show it again?). So usually we have to be pragmatic about it and do something fairly simple but still useful, and then move on to the next thing.
Nothing else is editable in that list which is why clicking the eye icon did nothing... but it makes sense, so I added that for the next beta.
I'm afraid it's impossible to help without more information - if you run in to a problem please file it here following all the guidelines: github.com/Scirra/Construct-3-bugs
Are you doing something like loading sound files by name? Previously if a sound was in a folder, e.g. "beep" is in the folder "sfx", then you'd need to update a reference to "beep" to "sfx/beep".
You can already use source control like GitHub, which is covered in this tutorial. These updates probably make it work nicer as the project folder structure is better.
Please report any problems you find here following all the guidelines: github.com/Scirra/Construct-3-bugs
The change only means if the host is disconnected from the signalling server, it can keep its existing connections to peers.
It'll only be a known issue if it's already filed here: github.com/Scirra/Construct-3-bugs/issues
The change is that the host can disconnect from the signalling server and still communicate with peers. This does not change the fact that if the host disconnects it ends the game. (Host migration is very complicated and I suspect it would be error prone too - you could probably give it a go with events anyway and get the peers to rejoin a new room)
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.