Hundreds of features to explore
Games made in Construct
Your questions answered
Popular & trusted by schools and Universities world-wide
Construct 3 runs in the browser & works offline
Students do not need accounts with us
World class complete documentation
Official and community submitted guides
Learn and share with other game developers
Upload and play games from the Construct community
Game development stories & opinions
Hello, for some reason the event dummy.X != unit_dummy.X triggers even though the loop above isn't even finished yet:
Can anyone tell me why? As far as I know it should wait. Thank you
No, Wait is not blocking, it pushes the events below it (Move...) to run on a thread after the wait period. You should use a timer to managed timed events.
I see. So the loop is finished but the actions within the loop are still running as a new thread
Develop games in your browser. Powerful, performant & highly capable.