In what order everything updates during a tick?

I posted this bug report and it was not really a bug. I misunderstood how everything is processed during a tick.

From what I understand from Ashley's answer to my bug report is that when I access a system variable, I do it before any behaviours. So if a behaviour change any system variable it will do it near the end of the tick and after an event accessed it. This way the new value can be read on the next tick. It's good to know. Now I'm curious of how everything is linked together during a tick. Specifically: In what order everything updates during a tick?

Note: I already know what the manual says about events. What I want to know is more in depth (I supposed).

Thanks!

Events run top to bottom, unless its a function.

As I wrote in my first post, I did read the manual. So yes, I know already what is explained there. I haven't find what I want to know in the manual. If my answer can be found there, I'll be happy to follow a link and read more.

Construct is mainly a set of events, plugins, objects and behaviors. Events run top to button but triggers runs when they are triggered and functions when they are called. Simple.

To clarify what I'm looking for:

Let's say an object have a behavior. At what time during a tick this behavior will be process? Before the events sheets? During the events sheets? After the events sheets? Before drawing to screen? While drawing to screen? After drawing to screen? ...

When a trigger is triggered. This event is process at the time it triggered? Before the events sheets on the next tick? After the events sheets on the next tick? ...

I understand it's not an easy question. Maybe there is a flowchart somewhere. Maybe it's super secret classified Scirra enterprise stuff. Or maybe no body knows.

I cannot answer your question, but maybe you can get some answers yourself by using the debug mode and breakpoints in C3 runtime.

This way you can exactly see at chosen points when a value is changed, for example.

More than secret, it actually is hard to answer as there is no set "flowchart".

Triggers will happen at different "execution" time, depending on the plugin, the behavior, the nature of what's triggered, functions are "false triggers", and even for the same trigger (for example a gamepad button press) this can happen at different time.

I guess Ashley could give a bit more details to clarify.

The answer is actually pretty complicated: different behaviors update at different times, both before and after events run, both before and after relative to other behaviors and plugins, depending on the specific plugin or behavior. I also think it's something games should avoid deliberately depending on, since it's implicit and inconsistent across addons.

Yeah I think behaviors are great to get you started and understand how the engine works and how to make games but the meat of construct 3 is it's event system and you can use events to create much more efficient games because the behaviors are made to work in pretty much every scenario but you can use events to make your game tailor made for your needs, instead of always relying on solids and requesting features for the solid behaivor you can make your own !!! The possibilities when creating your own are infinite !! Good luck out there !!

I think the biggest thing to watch out for is the fact that plugs, and behaviors will run quicker than events since there's less for them to look up. Its way less noticeable in the C3 runtime however.