QUOTE
the wait isnt my hyper trig..i was trying something ...i dont noo how to use death counter...wth is that ?
a deathcount is simply starcraft's way of counting how many times you personally have lost a unit due to razing (basically how many times each unit you have has been killed).
There are deathcounters for each and every possible unit you can imagine. Even some doodads (traps).
QUOTE
yes the spawning...
Heres my trigger ( i got 2 and its in SF )
Condition :
Bring(CurrentPlayer, AtLeast, 1, Civilian, low pressure 1);
Switch(lvl 1, Set);
Action :
CreateUnit(1, Drone, enemy 1 start, P8);
Wait(0);
MoveUnit(1, Civilian, P1, low pressure 1, low respwn 1);
Comment("Low 1");
PreserveTrigger();
2nd trigger.
Condition :
Bring(P1, AtLeast, 1, Civilian, low respwn 1);
Action :
Wait(0);
Order(Civilian, P1, low respwn 1, Move, low pressure 1);
PreserveTrigger();
Comment("Low 2");
You do not need the wait in your trigger if its 0. Actually, NEVER put a wait action if you don't need it, it will save you alot of greif.
Your problem is that the hyper trigger is probably being owned by all players or being owned by a player that is currently waiting. This results in "wait block," when two wait triggers attempt to wait at the same time!
"You can't wait twice."
To solve your problem, simply put the hyper triggers in a computer player who does not have any waits. I usually designate a computer player that does not have any waits and controls all the triggers without waits.