I have this trigger:

etc...

I have 5 differents teleports "in" and 8 teleports "out". Doesn't matter what IN you take, the out will be random.
This trigger is already working in my map, and i've tested it, with more humans players, and it's all cool.

My question is:
How know the 2º Trigger who is "Current Player"?

How know Starcraft who is Current Player?

The trigger is for all the force 1, where are all human players. The condition is only a switch, so i think is impossible to know who is the player in the teleport.
By this point, the trigger should move all zerglings to the teleport out, but...

The trigger only move the zerling of the player is in the Teleport IN!!!! Works fine!!

I want to know why this is happening!

Why not do it this way


"Current Player" refers to the player who owns the trigger.
When you assign a trigger to multiple players, or a force with multiple players on it, you actually get multiple copies of that trigger - one owned by each of the players.

So, in your triggers, when "Player 1's" Zergling enters the location "Player 1's" Zergling gets moved. Etc.

No Kenoli. Doing your way, I have to make 8x5=40 triggers..

My trigger works fine, i've already told.

But i want to know how it works.

For identify current player use the switch? I think the trigger can look for who set the switch... or something else..

Oh. I forgot you were talking about having multiple entry and exit locations.

The reason it picks the right player is because of the way the triggers are arranged. After one of the players sets the switch, the same player immediately uses it.

Is there an actual problem with the map, or were you just wondering how current player works for future reference?

Current Player = Who ever the trigger is set to be for.

EX:

Setting a trigger to Force 1 effects every player in force 1. Setting to All Players effects every Player.
(NOTE: The player will have to meet all of the conditions of the trigger for it to fire for that Player.)

Kenoli said it. In this case, "current player" is remembered within one execution run of the triggers.

To everyone else: This is not a problem with his map. He has a set a triggers that work, but he thought that they shouldn't.

CeR, please have a look at the post, where I describe exactly how triggers work: http://www.staredit.net/50794/
Then try to replay in mind the triggers behaviour with that exacly algorithm and you understand what is happening.

EDIT:
Trigger can't look for who set the switch and anything like that. No magic, just an exact algorithm I've described. That is all. Switches (btw as far as locations) are kind of global variables in oppose to death counters, score, kills and etc. which are local to players.

DT_Battlekruser, you understand it good.

My question is about this trigger:
Is the same trigger for all the players on force 1 (7 humans players). The conditions are only switches, and Wormer said this:

SO, I dont know why this system works fine!! I have tried a lot! With 2 players joining a teleport IN position at the same time. Both get different EXT position..

Two questions:
1. Does these actions "Message, Center view, minimap ping, etc.." include the clear Teleport Activated switch action?
2. Have you looked at the post?

1.Yes
2.Yes, but is in english and it very hard for me reading tecnic things in english (i'm spanish) so i dont understand a shit.. >_<

Post has been edited 1 time(s), last time on Apr 27 2008, 11:40 pm by Brontobyte. Reason: Added :bleh: :D

Translators are usually quite off the actual translation, especially when talking about technical things like this, but maybe it will help..

It helps me. It's not always perfect, but I can understand the gist of what a sentence says just by translating it.

You should understand this explanation better. It's basically what Kenoli, DTBK and Wormer already said, but maybe it helps to use other (simple) words.

Especially when the original English text uses "your" when it should use "you're". COUGH.



The reason the triggers work is because of the odd way in which Current Player functions. In a sense, it does "remember" the previous condition. Your triggers will be executed from first to last for each player, and the floating reference to Current Player will begin as null and only be changed if a condition involving Current Player evaluates to true. Current Player will remain pointing to the executing player unless another condition evaluates to false.

Therefore, your map will be reading your triggers like this (Assume player 1 has a Zergling at teleport, and player 2 does not):
---Execute Triggers for Player 1---
-Condition evaluates to TRUE, Current Player now refers to Player 1
-Action in the next trigger moves all Zergling for Current Player (Player 1)

---Execute Triggers for Player 2---
-Condition evaluates to FALSE, Current Player is now null
-Action in the next trigger does nothing, since it refers to no player.


Remember, a trigger given to a force acts identically to a trigger given to each player of a force, with the small side effect that force triggers are always compiled to the bottom of the trigger list.

No, the trigger does nothing because its conditions are not met. If the condition were met you would automatically have a current player.
The 'null-theory' may only apply when there's no trigger running at all.

And no, Force triggers are split up, but they are inserted in sorted position - the position you see them when you mark every player/force/all players in scmdraft trigger overview.

This trigger has its conditions met whether there was a Zergling on the beacon or not:

Force 1 (humans)
Conditions:
"Teleport Activated" is Set
Random option is A
Actions
Move Zergling from current player from everywhere to "Out 1"
Message, Center view, minimap ping, etc..
Preserve

Unless of course the switch is being set between individual trigger runs per player, which isn't specified in the original problem.

The only way that switch can be set is if a Zergling is in one of the locations.