Report, edit, etc...Posted by tinypross(sp) on 2005-01-25 at 05:10:12
i makin a bound and wen i make the units to build a then kill
they do that too fast i
wanna noe r u able to slo dat down a lil bit
i hav slowed down other levls but sum other levels wont n e 1 noe wats wrong ?
i think i could b makin the waits a lil too small but they r at 1000 mili secs at the moment
they do that too fast i
wanna noe r u able to slo dat down a lil bit
i hav slowed down other levls but sum other levels wont n e 1 noe wats wrong ?
i think i could b makin the waits a lil too small but they r at 1000 mili secs at the moment
Report, edit, etc...Posted by AqoTrooper on 2005-01-25 at 06:49:04
Please use correct English, I had to read it three times to finally understand what you said.
Now - hyper triggers won't make your waits go faster or slower, they'll just remove the 2 seconds wait that accures when your trigger reaches the 'preserve trigger' action.
If your explosions in the bounds go too fast you can simply increase the waits.
Also, any wait between 1-83 won't really matter so increasing a wait from lets say 5 to 50 won't make a differece, make bigger changes and you'll get what you need.
Now - hyper triggers won't make your waits go faster or slower, they'll just remove the 2 seconds wait that accures when your trigger reaches the 'preserve trigger' action.
If your explosions in the bounds go too fast you can simply increase the waits.
Also, any wait between 1-83 won't really matter so increasing a wait from lets say 5 to 50 won't make a differece, make bigger changes and you'll get what you need.
Report, edit, etc...Posted by chuiu on 2005-01-25 at 11:05:40
You haven't really described your problem. We can only throw out wild guesses.
My wild guess is that you have different waits on those levels.
My wild guess is that you have different waits on those levels.
Report, edit, etc...Posted by notnuclearrabbit on 2005-01-25 at 14:54:22
[center]I can barely understand what you're trying to say... Is it that the wait time between explosions is too little? Well, that is an easy problem to fix! Just add more time to the 'Wait' actions.
Or is it that the units you're creating, that are supposed to explode, you want a short wait time between the time they create, and the time they explode? If it's that, add a 'Wait' action between 'Create Unit', and 'Kill Unit'.[/center]
Or is it that the units you're creating, that are supposed to explode, you want a short wait time between the time they create, and the time they explode? If it's that, add a 'Wait' action between 'Create Unit', and 'Kill Unit'.[/center]
Report, edit, etc...Posted by Screwed on 2005-01-25 at 14:58:40
It doesn't exactly remove the 2 second wait between preserve triggers, it just shortens it to 1/12.2 seconds.
Report, edit, etc...Posted by RexyRex on 2005-01-25 at 15:31:37
There is probably some error with the order of the triggers if increasing the wait is not working.
CONDITIONS:
'Level 1' is set
-or-
Custom score/Death counter.
ACTIONS:
Create 1 Dark Archon at 'Explosion 1' for player X.
Kill all men owned by all players at 'Explosion 1'
Wait for X milliseconds.
Repeat until obstacle is finished.
Wait for X milliseconds. (Subtract 12 from what number you really want...)
Preserve Trigger
CONDITIONS:
'Level 1' is set
-or-
Custom score/Death counter.
ACTIONS:
Create 1 Dark Archon at 'Explosion 1' for player X.
Kill all men owned by all players at 'Explosion 1'
Wait for X milliseconds.
Repeat until obstacle is finished.
Wait for X milliseconds. (Subtract 12 from what number you really want...)
Preserve Trigger
Report, edit, etc...Posted by KaboomHahahein on 2005-01-25 at 15:33:50
Just to let you know if this is the problem. 1000milliseconds=1 second.
Your post is very confusing. Don't use excess internet slangs and use spell check.
Your post is very confusing. Don't use excess internet slangs and use spell check.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-01-25 at 15:44:46
QUOTE(Screwed @ Jan 25 2005, 01:58 PM)
It doesn't exactly remove the 2 second wait between preserve triggers, it just shortens it to 1/12.2 seconds.
[right][snapback]132201[/snapback][/right]
[right][snapback]132201[/snapback][/right]
No it delays the 2 second wait by keeping the triggering process active and seemingly never ending.