Ruskul
Competition between the best coding environments... in my case, c# with visual studio support, or javascript without good intelesense/scope with construct. This isn't even a competition. [...]
In construct, starting a new project is fast. Creating new objects is fast. Prototyping features is a breeze, But refactoring is SLOW and gets even more tedious the larger the game gets. Construct, by its very nature, encourages poor architecture (with nearly EVERYTHING in global scope [...]
if you want add duck, duck rolling, ground pounds, jump forgivness, double jumps, wall runs, wall slides, phaseshifting, object lifting, rewind and timeshift, shooting and reloading, but only in some cases. No that original choice to use if/else trees looks pretty bad. You probably should be using some sort of state machine. But then what if you want the character abilities to be added and subtracted at runtime. [...]
It was easier to learn unity than grapple with c2 sdk [...]
but the addition of scripting is pointless as has been mentioned [...]
Effort should be spent making c3 have better event system features that enable us to do more in a scalable environment...
Based on the examples you mentioned, you already know the solution. There will be always a limit to what you can do with an easy no-code solution. You can't have the cake and eat it too.
You should use JavaScript (or TypeScript) to build the complex part of your game (like the state-machine/skills system you mentioned). You can choose to handle the more complex systems with code and use the event sheets for more systems.
construct.net/en/make-games/manuals/construct-3/scripting/guides/subclassing-instances
Using Construct with TypeScript and VS code is not much different than C# with VS. You should give it a try.
I've ported most of my 4x strategy game to Construct, and it is as scalable as it was before. (hex grid, pathfinding, splines, modular AI, etc... check it on itch). With good intelesense btw :)
skymen [...] with the recent addition of TS, and with the VS Code extension, I think Unity C# with Visual Studio isn't that much of a better coding environment compared to C3.
I agree with skymen . From my experience, I can say Construct 3 doesn't get in the way of having a scalable architecture (especially now with the official typescript support).
My two cents:
1) It's better to invest in promoting the TypeScript support (with tutorials, docs, examples and step-by-step guides), than trying to make event-sheets handle all use cases imaginable. When someone argues about how event-sheets are limiting, it shows that the way to go is to write actual code (be that with C3 or with any other tool).
2) The visual identity could improve
Everade Construct needs a major makeover. Their website, logo, mascots, and how they advertise their engine all seem too playful. [...]
I agree with Everade that this would benefit Construct3. An example is GameMaker, which rebranded in 2012 to present a more professional/studio image. Among other things, the dark theme should be the default. I had the chance to witness someone's reaction to launching the guided tour for the first time. The seemingly outdated theme immediately put them off.
3) As skymen said, keep doing what you are doing. I understand that there might be challenges along the way, but the Ashley is doing a great job in improving the engine. I have seen many of the suggestions on Construct's suggestions website being brought to life (like TS!), and although not all suggestions are taken to heart, the curation has been quite decent so far.