This might not be new to a lot of you, but I kind of stumbled upon it when thinking about how waits work.

The problem:You want to run a trigger for many players, but the actions of the trigger will make the conditions false. This means that the trigger will only execute for the first active player.

The solution: Create the trigger as normal, but put a wait(0) before the condition-destroying action. This will cause the trigger to run for the other players before executing that action.

[TRIGGER]
Example[CONDITIONS]
[*]Switch 1 is clear
[/CONDITIONS]
[ACTIONS]
[*]Create 1 marine for current player
[*]wait for 0 milliseconds
[*]Set switch 1
[/ACTIONS]
[/TRIGGER]

The above trigger creates 1 marine for each player that it is active for. Another good example would be for any trigger that needs to display text.

I always just had a trigger at the bottom of the trigger list that would do the condition-destroying action, this method is great and all, but it could cause slight wait blocks.

Only if you use the spammy 62xWait(0); kind of HTs.

I remember there being a tutorial about this on the old SEN. It has something to do with waits making a trigger cycle go through before finishing the trigger or something along the lines of that. My old memory is failing me!

Actually, no, as long as you put those at the bottom of the trigger list they turn off just like cross-player hypertriggers whenever another wait is hit. And a wait 0 would do the same thing as their wait 0s, so it wouldn't even turn off the hypers.

It's still annoying to have to arrange them. (And I just remembered that I already knew about the trigger order trick when I used to make some bound maps. )