I mention in this blog post how, for this architecture, it's actually impossible to use event sheets fully, because it's going to use multithreading.
There are already loads of big and impressive games made almost entirely using events in Construct, so I don't really feel we still need to prove that point.
I don't know why someone deciding to code would jeapordise anything. The fact Construct lets you do coding too means if you make that decision you can keep using Construct. If we had no coding support at all, then someone in that position has to move to a different tool and so we definitely lose their subscription. And it's not all about Unity - there are other coding tools Construct is strongly competitive with.
I think that's a wilful misreading of the post. I'm not saying event sheets aren't important or can't do amazing things. There are plenty of big Construct games already made entirely from events. In this project I want to focus on a different approach.
I think I'm just repeating myself here, but the goal of the project is to show Construct can be used for coding, as well as event sheets. I guess it might not be for everyone, but I've set out the goals and gone in to detail about why I've gone in this direction.
Events don't really translate to clean or readable code as they are a completely different paradigm. However in many cases the APIs for specific plugins and behaviors relate closely to corresponding actions and expressions.
I'm using C3's own editor for the time being. I might switch to VS Code later down the line, but C3's own editor is working fine so far.
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".
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.