Left Click Trigger - Events Order

Those aren't the same conditions though. On button clicked is totally separate from On button clicked on Sprite. I would fully expect that the engine would call all On button clicked triggers first, and then move on to On button clicked on Sprite.

Remember, triggers are called outside of the event sheet. You shouldn't make assumptions about the order of two separate triggers.

Also the outcome is kind of thin because I'm not sure how you can get into too much trouble if an 'on any click' triggers in the same tick but earlier than 'on clicked on an object'.

— it actually caused me a huge headache, as clicking on a certain object (a menu button) ran the function to pause the game. The left click was used in some of the in-game controls, but those events only fired if the game was not paused. So I found that when clicking the pause button some events were running during the pause that shouldn't have been, and when you unpaused the game a load stuff happened that should not have happened. I got round it, but as I said I'm more frustrated by not being able to find out this stuff from the documentation.

You've trapped yourself by having a game where any click does something but also clicking a pause button counts as any click. You can get around this by having conditions like 'on any click and cursor is not over pause button' but I see your point.

You can get around this by having conditions like 'on any click and cursor is not over pause button'

Exactly what I did! Yeah I'm not angry or anything, appreciate the replies. I just remember using Gamemaker there was a list provided of the exact order of things, like events, scripts, movements, physics, rendering the screen etc. I much prefer Construct but that level of info was super useful.

Those aren't the same conditions though. On button clicked is totally separate from On button clicked on Sprite. I would fully expect that the engine would call all On button clicked triggers first, and then move on to On button clicked on Sprite.

This is correct.

The order of triggers is actually pretty complicated, especially if you start bringing in things like triggers in sub-events and triggers via included event sheets. I'd recommend wherever possible avoiding depending on the order the engine fires triggers, especially since it's not clear from looking at an event sheet what the ordering really is. Generally you can do this by just using a single trigger event to do everything in one set of actions/sub-events, so you can clearly see the order things are done within that event.

Thanks for the reply Ashley, just doing some testing last night revealed that it's relatively few cases when this is a problem. There are a small number of triggers that fire multiple things - mouse clicks, key presses and animation finishing. I think my testing helped me understand them. Have I missed anything in the documentation that explains the order of things outside events? I always wondered if the various movement behaviours ran before or after events each tick.

The specific ordering in the engine is very complicated, varies depending on the feature, occasionally changes, and is the type of thing people really should avoid depending on if they can, so it's not documented.