Report, edit, etc...Posted by Zeratul_101 on 2006-09-16 at 16:23:53
does anyone have a list of what trigger actions are 'slow,' as in they don't work until the trigger cycle has ended.
Report, edit, etc...Posted by PCFredZ on 2006-09-16 at 16:27:05
Actions all execute when they're hit, while Wait modifies the checking order of actions after themselves.
The Kill Unit and Kill Unit At Location actions execute immediately as well, but the units that die are not immediately removed from the map. In other words, a Killed unit disappears slower than a Removed unit.
The Kill Unit and Kill Unit At Location actions execute immediately as well, but the units that die are not immediately removed from the map. In other words, a Killed unit disappears slower than a Removed unit.
Report, edit, etc...Posted by Zeratul_101 on 2006-09-16 at 20:06:29
ya, thats what i thought(only kill was 'slow') but i've been having a problem with remove being slow. the problem trigs are:
***
player 1 commands at least one dragoon
deaths
preserve
remove dragoon
***
player 1 commands at least one dragoon
set death
preserve
remove dragoon
***
now, the second trigger starts a chain of events, to prevent this under certain circumstances, i put in the first trigger. as you can see, when the first trigger fires, the second one shouldn't. yet, they both end up firing
***
player 1 commands at least one dragoon
deaths
preserve
remove dragoon
***
player 1 commands at least one dragoon
set death
preserve
remove dragoon
***
now, the second trigger starts a chain of events, to prevent this under certain circumstances, i put in the first trigger. as you can see, when the first trigger fires, the second one shouldn't. yet, they both end up firing
Report, edit, etc...Posted by fritfrat(U) on 2006-09-16 at 20:19:25
Command doesn't update until the end of the trigger cycle. Use Brings atleast 1 dragoon to Anywhere instead.
Report, edit, etc...Posted by Zeratul_101 on 2006-09-16 at 20:24:03
alright thanks fritfrat. i'll leave this topic open for a little bit longer if anyone else knows of any other slow trigger scripts if the mods don't mind.
Report, edit, etc...Posted by Kenoli on 2006-09-16 at 21:18:15
Information about the Bring and Command conditions: here.
Report, edit, etc...Posted by MoonlighTurtle on 2006-09-17 at 22:12:21
Removing transport units doesn't happen until the end of the trigger cycle.
Report, edit, etc...Posted by Laser_Dude on 2006-09-17 at 22:27:02
Bring to anywhere isn't any different from command. I know this because I delt with it in a map. Remove unit, give unit, kill unit... are all "slow", as in they can't be detected until the next trigger run.
Report, edit, etc...Posted by MoonlighTurtle on 2006-09-17 at 23:43:14
Bring is different than command, when detecting whether or not a unit has just been removed in the current trigger cycle.
Remove unit is only "slow" when removing transport units, because then it acts like the kill unit action, which is always "slow". Give unit is not "slow".
Remove unit is only "slow" when removing transport units, because then it acts like the kill unit action, which is always "slow". Give unit is not "slow".
Report, edit, etc...Posted by TheKeyToKilling on 2006-09-21 at 11:25:44
QUOTE(Zeratul_101 @ Sep 16 2006, 07:06 PM)
ya, thats what i thought(only kill was 'slow') but i've been having a problem with remove being slow. the problem trigs are:
***
player 1 commands at least one dragoon
deaths
preserve
remove dragoon
***
player 1 commands at least one dragoon
set death
preserve
remove dragoon
***
now, the second trigger starts a chain of events, to prevent this under certain circumstances, i put in the first trigger. as you can see, when the first trigger fires, the second one shouldn't. yet, they both end up firing
[right][snapback]562019[/snapback][/right]
***
player 1 commands at least one dragoon
deaths
preserve
remove dragoon
***
player 1 commands at least one dragoon
set death
preserve
remove dragoon
***
now, the second trigger starts a chain of events, to prevent this under certain circumstances, i put in the first trigger. as you can see, when the first trigger fires, the second one shouldn't. yet, they both end up firing
[right][snapback]562019[/snapback][/right]
The first time this trigger runs during the game, the second 1 should run first... everything should work correctly... the second time player 1 commands a dragoon though, since the first time deaths were set... and since this time player 1 also commands at least one dragoon... both of the triggers should meet requirements... Player 1 commands at least one dragoon and deaths are set... therefore the second time it runs... it should be doing both triggers instead of just 1 of them.
Report, edit, etc...Posted by Zeratul_101 on 2006-09-21 at 11:29:37
nice try, but the deaths aren't related. not your fault. anyhow, the issues been solved. forgot to close it 
*topic closed*
*topic closed*