[color=lightgreen]k. More spawn problems for you guys. I'm using DCs to determine when units will spawn, instead of Waits because they create wait blocks. I have 3 different types of units, which spawn at different times. So Unit 1 will begin spawning after 120 game seconds, Unit 2 will begin spawning after 360 game seconds, and Unit 3 will begin spawning after 600 game seconds. This is where the DCs come in, I want the DCs so the spawn trigger will Preserve Trigger. [size=1](Hooray for good grammar)[/size] I've done a test, and every game second counts as 6 Death Counts with Hyper Triggers and no waits. So 120 game seconds would = 720 Death Counts. I add a Death Counter: [TRIGGER] [DESCRIPTION]Trigger[/DESCRIPTION] [PLAYERS] [*]Player 7 [/PLAYERS] [CONDITIONS] [*]Player 7 has suffered at most 719 deaths of Rhynadon [*]Elapsed scenario time is at least 1 second [/CONDITIONS] [ACTIONS] [*]Set deaths for Player 7: Add 1 death for Rhynadon [*]Preserve Trigger [*]Comment [/ACTIONS] [/TRIGGER] So to spawn Unit 1, I have: [TRIGGER] [DESCRIPTION]Trigger[/DESCRIPTION] [PLAYERS] [*]Player 7 [/PLAYERS] [CONDITIONS] [*]Elapsed scenario time is at least 120 game seconds [*]Player 7 has suffered at least 720 deaths of Rhynadon [/CONDITIONS] [ACTIONS] [*]Create 20 Zergling at Spawn 1 [*]Preserve Trigger [*]Comment [/ACTIONS] [/TRIGGER] And finally, to make sure that Unit 1 doesn't constantly spawn, I have the DC reset: [TRIGGER] [DESCRIPTION]Trigger[/DESCRIPTION] [PLAYERS] [*]Player 7 [/PLAYERS] [CONDITIONS] [*]Player 7 has suffered at least 720 deaths of Rhynadon [/CONDITIONS] [ACTIONS] [*]Set deaths for Player 7: Set to 0 for Rhynadon [*]Preserve Trigger [*]Comment [/ACTIONS] [/TRIGGER] The problem is, The only time Unit 1 will spawn, is when the Reset Trigger is removed. When Reset Trigger is present, the units won't spawn whatosever. Is the Reset Trigger just constantly setting the deaths for Rhynadon to 0? Is it just preventing the deaths from adding? Any help with my situation would be appreciated.[/color]

Well, first off, it's actually more like 12 deaths per game second, and to fix this up, remove all the elapsed game times, they are useless if you are preserving the trigger. And they are probably also the problem, since the deaths get there first, they reset before the timer, so when the timer finally makes it, the deaths are woefully behind.

Well, first off, it's actually more like 12 deaths per game second, and to fix this up, remove all the elapsed game times, they are useless if you are preserving the trigger. And they are probably also the problem, since the deaths get there first, they reset before the timer, so when the timer finally makes it, the deaths are woefully behind.

It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.

It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.

[color=lightgreen]Wouldn't the elapsed game times be necessary since I'm using countdown timers?[/color]

[quote=Impeached]It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.[/quote] Oh jeeez.... when will ppl finally realize it? (nothing personally, falk, but I already said that in NUMEROUS threads, and I'm getting tired of it.) We should really make a sticky note containing this sentence: [B]When hyper triggers run, the triggers are checked 8 times a game second and will be checked 12 times per real time second on speed 7. This (last) is the value you have to use when you replace waits, as waits are measured in real time.[/B]

Quote from Impeached

It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.

Oh jeeez.... when will ppl finally realize it? (nothing personally, falk, but I already said that in NUMEROUS threads, and I'm getting tired of it.)
We should really make a sticky note containing this sentence:

When hyper triggers run, the triggers are checked 8 times a game second and will be checked 12 times per real time second on speed 7. This (last) is the value you have to use when you replace waits, as waits are measured in real time.

..Ok, thanks for confirming what I said.

..Ok, thanks for confirming what I said.

You have 2 triggers there which act only when you have 720 deaths. One of those resets it. What's happening is it's resetting it before the 120 game second mark. The units will spawn when you get to 720 deaths the second time (after the 120 second mark). If you only want them to spawn once, why not just use elapsed time is 120/240/360? If you could explain what you want better, I could help you out even more.

You have 2 triggers there which act only when you have 720 deaths. One of those resets it. What's happening is it's resetting it before the 120 game second mark. The units will spawn when you get to 720 deaths the second time (after the 120 second mark).

If you only want them to spawn once, why not just use elapsed time is 120/240/360? If you could explain what you want better, I could help you out even more.

[QUOTE]It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.[/QUOTE] Sorry about that, it's odd that I would forget as I actually HAVE done that exact test... And rockz repeated what I said, although I think it's necessary to explain it a little better. Okay, I'm not going to use 8 deaths a second, as it is slightly off, the most perfect method of finding a time, is using 1 death every 84 milliseconds instead, so you would get about 1428.5714285714285714285714285714 deaths in 120 seconds. There is no need for elapsed game timer, just remove it and your trigger will work, trust me. Currently, your triggers WILL run, they just won't run the first time around, they will on the second time.

Quote

It's 8 actions per game second. If you dont' believe me, make a trigger that gives 1 ore per cycle, using an at least and at most elapsed time condition.

Sorry about that, it's odd that I would forget as I actually HAVE done that exact test...

And rockz repeated what I said, although I think it's necessary to explain it a little better.
Okay, I'm not going to use 8 deaths a second, as it is slightly off, the most perfect method of finding a time, is using 1 death every 84 milliseconds instead, so you would get about 1428.5714285714285714285714285714 deaths in 120 seconds. There is no need for elapsed game timer, just remove it and your trigger will work, trust me. Currently, your triggers WILL run, they just won't run the first time around, they will on the second time.

ooops

ooops

[color=lightgreen]Oh ok I see what you guys are saying. Yes, now my trigger is working. Thank you, yet again. =D[/color]

Yo, please, post your fixed trigger cause im havign a hard time doing mine...please

Yo, please, post your fixed trigger cause im havign a hard time doing mine...please