Let me explain:
Usually, Clickteam goes by certain rules when it comes to which conditions and events is activated before and after one another: usually by top to bottom, but sometimes immediate like when an object collides with something. There are three (I’ll call them “places”) that use the Event Editor: Global, Frames, and Objects. From what I gathered, which place is prioritized before the next is exactly how I listed formally. So we know that the events in the Object behaviors go after the events from Global and Frame so long as it isn’t triggered from an immediate condition.
Now back to the question:
If the application has multiple objects in the same frame with each having a behavior, which object behavior goes first? If Object A, B, and C all have Alterable Values that count up by 1 every frame, which one gets the first number and which one gets the last number before the cycle loops back? How do we make sure Object A will always be counted first and Object C will only be counted after A and B were counted? Is it Alphabetically? Is it based on which object was created first and if so: created first in Clickteam or created first during the application’s runtime?
So this question may be older than I assume, but I really want to know if there are any changes after the tons and tons of updates this program had since it was a problem for some, years ago.