Report, edit, etc...Posted by JaFF on 2006-08-08 at 04:11:09
I need to be sure, so if you don't know or not sure, don't answer this question:
After running 1 (any) trigger, all the other triggers ( for all players) get scanned ?
After running 1 (any) trigger, all the other triggers ( for all players) get scanned ?
Report, edit, etc...Posted by JoJo. on 2006-08-08 at 04:19:02
QUOTE(Jammed @ Aug 8 2006, 01:10 AM)
I need to be sure, so if you don't know or not sure, don't answer this question:
After running 1 (any) trigger, all the other triggers ( for all players) get scanned ?
[right][snapback]542083[/snapback][/right]
After running 1 (any) trigger, all the other triggers ( for all players) get scanned ?
[right][snapback]542083[/snapback][/right]
Don't be mad for me asking but what do you mean by scanned?
Report, edit, etc...Posted by Killer_Kow(MM) on 2006-08-08 at 07:33:46
I think he means checked. However, I don't know the answer, so I'll go now.
Report, edit, etc...Posted by PCFredZ on 2006-08-08 at 08:51:38
QUOTE(Killer_Kow(MM) @ Aug 8 2006, 07:33 AM)
I think he means checked. However, I don't know the answer, so I'll go now.
[right][snapback]542118[/snapback][/right]
[right][snapback]542118[/snapback][/right]
Yeah, just search one of the million posts Bolt Head posted...
Ok, I found it. It's got stuff about Hyper Triggers attached, free bonus.
Go nuts.
EDIT: reading that post I've realized that Bolt rambled a lot about Hypers and not much about trigger execution. Let me just sum it up for you:
QUOTE
order of trigger creation determines trigger execution order
Report, edit, etc...Posted by Shocko on 2006-08-08 at 10:02:59
all i know is that triggers work
Top -----> Bottom
p1 -----> p8
if thats any help then yay
, if not then boo hiss hiss boo 
Top -----> Bottom
p1 -----> p8
if thats any help then yay
, if not then boo hiss hiss boo Report, edit, etc...Posted by fritfrat(U) on 2006-08-08 at 10:06:50
http://www.staredit.net/index.php?tutorial=232
It runs player 1's triggers, top to bottom.
Then player 2's triggers, top to bottom.
etc.
DOUBLE EDIT: Removed a paragraph full of wrong information. That tutorial lies
The tutorial by blizzard I linked to above also states that player 1's triggers going first actually becomes an issue because if two people bring a unit to a location at exactly the same time and whoever it brings it first gets something, the higher numbered player would get it, since their triggers go first. Of course, hyper triggers would basically fix this problem, but it's just an example of how the trigger order works.
EDIT: Forgot to mention wait blocks. These pertain to single players, so even if player 1 is executing a wait block, it will still go on to player 2-8's triggers. You'll get the hang of how those work after working with them, though.
It runs player 1's triggers, top to bottom.
Then player 2's triggers, top to bottom.
etc.
DOUBLE EDIT: Removed a paragraph full of wrong information. That tutorial lies
The tutorial by blizzard I linked to above also states that player 1's triggers going first actually becomes an issue because if two people bring a unit to a location at exactly the same time and whoever it brings it first gets something, the higher numbered player would get it, since their triggers go first. Of course, hyper triggers would basically fix this problem, but it's just an example of how the trigger order works.
EDIT: Forgot to mention wait blocks. These pertain to single players, so even if player 1 is executing a wait block, it will still go on to player 2-8's triggers. You'll get the hang of how those work after working with them, though.
Report, edit, etc...Posted by Shocko on 2006-08-08 at 10:13:56
QUOTE(fritfrat(U) @ Aug 8 2006, 06:06 AM)
EDIT: Forgot to mention wait blocks. These pertain to single players, so even if player 1 is executing a wait block, it will still go on to player 2-8's triggers. You'll get the hang of how those work after working with them, though.
[right][snapback]542212[/snapback][/right]
[right][snapback]542212[/snapback][/right]
pertain ?
Report, edit, etc...Posted by fritfrat(U) on 2006-08-08 at 10:14:55
Report, edit, etc...Posted by Shocko on 2006-08-08 at 10:17:13
lol at first i thought u ment certain but thinking about it the c is on the other side of the keyboard lol thanks u learn something new everyday
Report, edit, etc...Posted by PCFredZ on 2006-08-08 at 10:44:39
QUOTE(Shocko @ Aug 8 2006, 10:02 AM)
all i know is that triggers work
Top -----> Bottom
p1 -----> p8
if thats any help then yay , if not then boo hiss hiss boo
[right][snapback]542206[/snapback][/right]
Top -----> Bottom
p1 -----> p8
if thats any help then yay
, if not then boo hiss hiss boo [right][snapback]542206[/snapback][/right]
QUOTE(fritfrat(U) @ Aug 8 2006, 10:06 AM)
http://www.staredit.net/index.php?tutorial=232
It runs player 1's triggers, top to bottom.
Then player 2's triggers, top to bottom.
etc.
All Players and stuff like for Forces is NOT the same as having the triggers checked for every player. All Players and Force triggers run AFTER the triggers that are assigned to each player. This is in the tutorial above.
The tutorial by blizzard I linked to above also states that player 1's triggers going first actually becomes an issue because if two people bring a unit to a location at exactly the same time and whoever it brings it first gets something, the higher numbered player would get it, since their triggers go first. Of course, hyper triggers would basically fix this problem, but it's just an example of how the trigger order works.
EDIT: Forgot to mention wait blocks. These pertain to single players, so even if player 1 is executing a wait block, it will still go on to player 2-8's triggers. You'll get the hang of how those work after working with them, though.
[right][snapback]542212[/snapback][/right]
It runs player 1's triggers, top to bottom.
Then player 2's triggers, top to bottom.
etc.
All Players and stuff like for Forces is NOT the same as having the triggers checked for every player. All Players and Force triggers run AFTER the triggers that are assigned to each player. This is in the tutorial above.
The tutorial by blizzard I linked to above also states that player 1's triggers going first actually becomes an issue because if two people bring a unit to a location at exactly the same time and whoever it brings it first gets something, the higher numbered player would get it, since their triggers go first. Of course, hyper triggers would basically fix this problem, but it's just an example of how the trigger order works.
EDIT: Forgot to mention wait blocks. These pertain to single players, so even if player 1 is executing a wait block, it will still go on to player 2-8's triggers. You'll get the hang of how those work after working with them, though.
[right][snapback]542212[/snapback][/right]
All wrong, Blizzard's FAQ lies.
EDIT:
Proof.
Report, edit, etc...Posted by fritfrat(U) on 2006-08-08 at 10:50:25
If it's wrong, you should remove that tutorial from the database.
I had actually always thought that the group triggers were incorporated into the player's trigger orders, but I went off that tut and made my last post, thinking "hey, blizzard can't be wrong." Shame on me for thinking that, especially after playing D2 for so long
Edited my last post, removing all the wrong information.
I had actually always thought that the group triggers were incorporated into the player's trigger orders, but I went off that tut and made my last post, thinking "hey, blizzard can't be wrong." Shame on me for thinking that, especially after playing D2 for so long
Edited my last post, removing all the wrong information.
Report, edit, etc...Posted by Shocko on 2006-08-08 at 12:41:11
i just said wat i was told i dont use sen tutorials they generally teach u to hate the sen tutorials more then the trigger
Report, edit, etc...Posted by JaFF on 2006-08-08 at 14:34:15
Thanks for the help. You guys saved me from using up 5 more locations... in other words, you didn't save my ass in a critical situation But still thanks
But still thanks