Here is a detailed explanation of what is going on in my map.
Player 1 and Player 2 [Or any other combination] enter the end of level 1 at the same time. Causing the level 2 trigger to fire twice. Making 2 level 2 units instead of just making the normal 1 unit.
How can I make it so if 2 players enter the end of level 1 it doesn't fire the level 2 trigger twice?
If you can help me make a work around like if player '1-12' has 2 units in 'whole field' kill 1 unit.
Post has been edited 2 time(s), last time on Aug 18 2010, 10:00 pm by Vincent.
None.
Add this condition into the "Conditions" section of the trigger(s) in question:
Actions Queue is Empty == true
and I believe this will work too
(Number of times (Current trigger) has been executed) == 0
None.
Actions Queue is Empty == true
I don't understand this one...
I'd interpret it as "# Actions left to trigger: none", thus making me tend to say to set it to 'false'.
None.
Hmm, I thought it was number of times the trigger is queued to run, but I suppose what you said makes more sense.
None.
How about "Turn (current trigger) off" as the last action?
if you don't need the trigger anymore, it should work.
~TheFreak
None.
How about "Turn (current trigger) off" as the last action?
if you don't need the trigger anymore, it should work.
~TheFreak
I've tried this, the best is to use shmeeps 2nd option.
[SOLVED]
None.
How about "Turn (current trigger) off" as the last action?
if you don't need the trigger anymore, it should work.
~TheFreak
I believe the problem with this is that, if in the rare case that the two units cause the trigger to run side by side, most, if not all of the actions will still be run twice. I'm not sure if turning off the trigger even stops all running instances of it either.
None.
Err I meant First instead of "last".
@shmeeps: No, turning off a trigger only makes it not respond to events. It still executes all the remaining actions in all running instances.
also (Number of times (Current trigger) has been executed) == 0 would suffer exactly the same in those rare cases.
~TheFreak
None.
If the actions triggers two times, what about adding a prevention-trigger that would increment 1 to "x" for every time the trigger is set.
If ever you detect that x == 2, you fix the glitch.
None.
You could do it within the same trigger. It would cost you an extra global variable but it would work.
~TheFreak
None.