Ok, I know that player1 runs triggers before p2 does or something. But I need a full list of players and player groups(including players inside) in order they run triggers. Also some explanations wouldn't hurt.
All of p1's triggers run, all of p2's, all of p3's, and so on until all of p8's triggers have run. There's no such thing as Force and All Players. It's merely a grouping thing in the editors, the triggers there are the same as if they had been applied to the players in the force, and they run for the specific player when the specific player's triggers are being run.
So basically the list is:
P1
P2
P3
P4
P5
P6
P7
P8
That is the order in which triggers run. Also, they are the only players that can run triggers.
everything below is what i've learned from what others have said, not personal testing so there may be some small nuisances that are incorrect
you already know basic trigger order, so i'll explain player groups.
player groups do not run triggers - because, practically speaking, they don't have any. the triggers they have are actually in each individual players trigger list(albeit invisible) and the forces is merely an easier(but flawed) way of organizing trigs.
lets say i've created these triggers in this order:
***
Player 1
always
create 1 marine
***
Force 1(player 1 is included) * - name of trig
current player commands at least one marine
remove marine for current player
***
player 1 ** - name of trig
current player commands at least one marine
defeat
***
now, people generally think the trigger order is like this and that you'll end up with a defeat:
***
Player 1
always
create 1 marine
***
player 1 **
current player commands at least one marine
defeat
***
Force 1(player 1 is included) *
current player commands at least one marine
remove marine for current player
***
this is wrong, the proper trigger order is the first set of trigs. even though force 1 comes after player 1 - it doesn't matter because like i said, force 1 doesn't acutally have any trigs - because trigger * was created earlier, it already has a spot reserved for it, ahead of **.
this is a basic explanation, i'll provide a more elaborate one if you need it.
I see, this is bad, really bad. So to make sure that tiggers run in certain order is to check p1, p2, p3, p4, p5, p6, p7, p8 instead of all players? Damn, It will take quite some time to reorder the triggers.
lol, yep, trigger groups are just plain bad
They aren't exactly bad, it's just hard to know the order they are in when you have some triggers for specific players, and some applied to forces and all players, because they are grouped in the editor separately. You would really only run into problems when you are dependent on trigger order, and triggers for specific players are related to the triggers in the forces groupings.
That's why I try to either trigger everything applied to forces, or checked for each player.
Also, using SCMD2, it should be easy to change forces, to specific players such as replacing:
Trigger("Force1"){
with:
Trigger("Player 1","Player 2"){
using notepad.
true, true, usually the only time i use trigger groups is for non-trigger order reliant and non-preserved triggers(such as spawning). just because its so tedious(as in invisible) and because of my rather archaic trigger making process, i don't find it 'safe' to use trigger groups.
remember, not all of us have the luxury of using TrigEdit
Here is a link to a topic that has other links in it. It will lead you to the truth.
I'm amazed how people can actually argue about such things. We should have a big tuttorial that states facts like this, correct ones of course. Otherwise everyone thinks his own way and that leads to bugs in our maps.
My conclusions:
- Triggers are executed from top to down as they are listed in editor.
- Triggers are executed for players from p1 to p8.
- Group triggers are actually in the player triger list, but hidden.
- As group triggers are in player's lists they are executed according to time when they were created.
Is that right?
QUOTE
I'm amazed how people can actually argue about such things. We should have a big tuttorial that states facts like this, correct ones of course. Otherwise everyone thinks his own way and that leads to bugs in our maps. pinch.gif
Well, everyone that knows how it works, pretty much most of the replies here, are just saying the same thing but in different ways. I find it a little hard to explain the group triggers in a clear way, without having to actually give a lengthy example of triggers. However, I like how Bolt_Head said it here:
http://www.staredit.net/index.php?showtopi...&st=0&p=301761&I think it is a problem that we have a tutorial by blizzard that states exactly the opposite.. we need to remove that tutorial or state in it that what blizzard is saying is wrong.
Using scmdraft2's classic trigedit and selecting both Player 1, All Players, and the force player 1 is in would be able to show the entire trigger order for that player. Trigedit, obviously, also shows them all in straight up order, so you can just look through the text for all of P1's including groups, all of p2's, etc.
Assigning triggers to a force or all players is pretty pointless. You get exactly zero benefits.
QUOTE(Kenoli @ Sep 4 2006, 01:59 PM)
Assigning triggers to a force or all players is pretty pointless. You get exactly zero benefits.
[right][snapback]555490[/snapback][/right]
And how about this: you don't need to copy it to each of the players in that force.
so wait... if you give hypers to the all players category... will the hypers effect all the triggers?
QUOTE
And how about this: you don't need to copy it to each of the players in that force.
You don't need to copy even if you aren't using forces.
QUOTE
so wait... if you give hypers to the all players category... will the hypers effect all the triggers?
Hyper triggers affect all the triggers even if they are just owned by one player
i thought triggers activate according to when the trigger was created, the trigger order, you can look up the trigger order in uberation or scmdraft.
basicly forces and players do not determine the trigger order, it is when the trigger was created that matters or the trigger order it activates from first trigger to last trigger in the order the triggers was created.
Nope, sorry sky. If they were all under the same player it would fire in that order, but it runs it skipping all triggers for p2-p8, then again skipping all for p1+p3-p8.. and so on.
I often use force triggers (especially when there is only one computer in a force) for organizational purposes, but anything that would matter with trigger order should probably be under the individual players for the sake of lowering confusion.
Here's the exact order:
Player 1
Player 2
Player 3
Player 4
Player 5
Player 6
Player 7
Player 8
All Players
Force 1
Force 2
Force 3
Force 4
and of course, top to bottom in each list
No, read the above posts, and the other topics that have been linked to.
What about the trigger conditions and actions from uberation?
QUOTE(SuperPika2K7)
What about the trigger conditions and actions from uberation?
What about them?
Can LegacyWeapon list them?
QUOTE(DEAD @ Sep 3 2006, 06:59 AM)
My conclusions:
- As group triggers are in player's lists they are executed according to time when they were created.
Is that right?
That assumes you've never used "Move Up or Move Down". The only way to be totally sure is to use SCMDraft 2's text trigger editor. That will tell you the trigger's placement for sure.
QUOTE(SuperPika2K7)
Can LegacyWeapon list them?
There is nothing different about them. They are normal triggers.