Since my first blog I've been putting together the overall architecture of the game. You can see some of the initial work in the commit log on GitHub. This can...
-"you can start with event sheets, add a few snippets of code in event sheets, and move on to using full coding"
-"as we would expect the most advanced users to shift from event sheets to coding"
I'm sorry but the promise of construct always has always been to be a nocode engine. That never was to stop using nocode feature ASAP
In fact after reading this i feel even less confident about it because you also don't recommand to mix JS and eventsheets, but to go full JS instead
Honestly this is a bit sickening. This looks like the whole argumentation about Events is against Construct itself and its original vision
We're expecting the actual No-Code features to not be considered as "just a toy". It's a bit weird the only way to prove C3 isn't a toy is skipping the NoCode part. The marketing and dev effort should instead go towards "yes NoCode is viable for serious stuff"
Also a bunch of us are experienced users and our path never was to move from ES to JS. I didn't learn JS using C3.
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.