ok if i have trigger:
| Trigger |
| Players: |
| ¤ 1 |
| Conditions: |
| ¤ player 1 commands 1 buildingx at location x |
| Actions: |
¤ wait 10000
|
¤ create 5 marine at location x
|
| ¤ preserve trigger |
then i have trigger:
| Trigger |
| Players: |
| ¤ 1 |
| Conditions: |
| ¤ player 1 commands 1 buildingy at location y |
| Actions: |
¤ wait 10000
|
¤ create 5 marine at location y
|
| ¤ preserve trigger |
do the waits from the different triggers stack on each other?
Yes, it's called a wait block, but they only stack on each other if they are owned by the same player.
yea screwed is exactly right. in your triggers they would "stack onto each other" if both of the conditions were met at nearly the same time because they are both owned by player 1.
sry if i double posted because my browser was acting wierd.
Yes for times that long it would be better to make a counter to keep the trigger from firing every second.
The waits don't really "add together" as many people say. They technacly delay eachother.
Another words if your first trigger fires then it will start to wait 10 seconds. If before that 10 seconds is up the condidtions for trigger B are met then the trigger will begin to fire but stop when it gets to the first wait. The second trigger will remain at a standstill untill the first wait has finished and the second gets priority to run a wait. Then once the first finishes the second will start.
This is differant than both triggers waiting for 20 seconds witch is what is implied when said they add together.
If you have any questions go ahead and ask. I try to simplfy things to stress the keypoints.
Try to make it so the players are limited to one building at Location X or Location Y.
Better yet, why not make one trigger owned by a different player?