Aphrodite , thank you for the clarification. It's the concept behind some actions that confuses me. Since I am not a programer and I am introduced to programming concepts within Construct, I feel that sometimes the logic is very clear ("do x get y"), however the lack of foundational knowledge (in programing) other times make the logic behind conditions and procedures feel somewhat obscure. I can't really put in in words, it's more like a feeling, some steps seem to be way steeper than others. Perhaps this is something that someone that has a background in programming doesn't experience as vividly as I do.
Enough psychoanalysis for one post though, thanks again for the information ;o)
A quick exemple: I did a land generation concept based on arrays and tiledbackgrounds (was before the tilemap), and basically the land would generate in 4 times:
First populating the array
then correct some values in it
then apply some filtering
then create the objects
The way it was done, it took 4 ticks to do it
believe me, those 4 ticks were long (60 seconds for all of them combined), so you cann see the execution is stopped
Afaik the only heavy calculation C2 does that will not stop the game (aka: done in parralel) is the pathfinding algorythm.