i am the foreinger in this forum, as u will notice in my english and in the way they drown my treaths to the bottom of time.
But, if you want an honest opinion, i can do that. Althought i know most will not agree.
Construct is Beta as ashley states. I think it is Beta in the shaders, but still alpha in the events.
I also think that it is inevitable that the event sheets very nearby in the future will break with today,
and be incompatible with what is implemented today.
A short pro-contra list.
Construct seems to be very alive. New releases come quick. Major bugs get fixed fast. And it is all done by Ashley reading those forums. And thats a BIG plus.
A lot of events take "expressions" as "input". And thats the real power of construct. Thats what lifts Construct above all other "game makers" that i used.
Behaviours, the way objects behave, are plug-in based. And that will be in the future a great thing. Especialy because there is a SDK available, and one day there will be Docs for it too.
The bugs are not a contra. They are still opportunitys. Construct is in beta.
Picking and isolating objects can be a real pain in the ****. The events/actions system is a puzzle.
Its not documented yet. Things that u expect to work as triggers, dont work as triggers. The events can be done with the power of an expression, but the action dont carry that power on, because it will force you to "pick" an object. Where it is more logical to let the events pick/isolate, and keep the acions general. This way the action will work on every object picked by an event. And thats not the case now. And although Ashley is not open towards those questions, it will be necensarely to change
the events-system to bring construct on again a higher level.
I asked Ahley if he planned individual "event sheets". He did't answer me (as usual). So i guess not.
No individual event sheets are a major draw back.
I guess, you must complete the ghost tutorial to understand what i am mumbling about.