How does the "skip remaining actions" trigger work?

Like, I've been doing this map where you click a unit, it kills that unit and gives you points or whatever. But here's the problem. With triggers, there's always a bit of what I call "trigger lag". That allows you to click the same unit TWICE or even THRICE before it dies. I didn't use any wait commands, it's nothing else than:
Player selects unit, explode triggering unit. Nothing else. But since you can click the same thing twice, I tought, lets do this:

If ((Number of triggers in the trigger queue) Greater than 1) then do (Skip remaining actions) else do (Do nothing)

Logically, it should work, right? but it doesn't. It still allows you to click twice, and for me, that's a BIG problem.

Any help, anyone? I'd be grateful.

Just use action: Trigger-turn off this trigger:Heh:

Nope, sorry, that's not it. It is used multiple times during the level, then when the level ends, it turn off. You don't seem to understand the problem. The thing is, you're not supposed to be able to click the SAME unit twice. When you click, it's supposed to IMMEDIATLY die. But it doesn't, it takes half a second which is enough to click again.

in general i find there is a certain 'laginess' between recieving user input and having a trigger respond to it

i'm not totally sure, but not much u can do besides just disabling whatever happens on the second click if the unit has already been clicked

Try this - immediately before you explode the unit, add a line that subtracts 1 from its acquisition range. Then add a condition making the trigger only work if the unit's acquisition range is it's default range. While an explosion may take a split second to execute, I suspect a unit parameter is modified instantly, for all practical purposes.

"Skip remaining actions", btw, only skips all remaining actions in that ONE instance of a trigger. It has no effect on subsequent runs of that trigger, and each time the trigger is spawned, it has no "memory" of what happened in previous runs (that's how the acquisition range trick would work, assuming it does indeed work - it would be your "memory" across multiple trigger runs).

Skip Remaining Actions gives an empty return statement, which causes the trigger to end.