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...
IMO, It jeapordises many subscriptions because most I assume are here to use events and you guys are the best for that. If I start feeling the need to code then all of a sudden you have plenty of competition.
I wasn't aware that there were no mainly scripted large games made with construct, that does change the situation a bit. I could be biased and say that supports my claim made above but who am I?
I'm not suggesting to remove the ability to code entirely. And I definitely don't blame you for making your game whichever way you see fit. Maybe I read into this too much and I truly apologise if that is the case mate.
I just hope that you don't move forward with the mentality that advanced users switch to coding because I can't imagine how that wont translate into less time spent on improving further your main selling point and the reason why most of us are here.
It's not like we're taking away anything from event sheets. Everyone can choose whichever usage suits them! We're just providing extra options: event blocks, code, or a mix of both.