Hi,
I'm a programmer familiar with various other game engines and gamedev libraries. I am looking into Construct3 now to see whether it's viable for quick prototyping of 2d games.
I want to code and experiment with more complex logic.
I've noticed one big issue so far. Construct is apparently targeted towards non-programmers. The whole design is around "event sheet" which means practically all logic (except maybe behaviours) is centralized. This might be ok for some small simple games, but in general it's a bad engineering practice.
I want to break up the logic and encapsulate/bundle it somehow with objects to make reusable components. Of course SOME logic may stay at top level.
Is there any clean way to organize game logic in C3?
PS. I was looking at the scripting possibilities. Unless I missed something, if I use scripted actions or events or even self-standing JS scripts, I need to anchor the logic to the top level explicitly (and it would not be directly associated with game objects). In other words, seems like I have to work around basic design of the framework. The documentation also does not mention such use of scripting.