As the title says. Is the "Any Player" option MPI, or will I need to use Player 1, Player 2, Player (...) instead?
Additional Info: The Any Player option is an event/condition, not an action.
MPI means that the trigger can be ran multiple times at the same instance by many players, meaning that if two players trigger the event at once, the trigger won't screw up.
If you know about Picked or Triggering Player, what exactly is your problem? Describe exactly, what you want to do; an event cannot be described as MPI or not, it depends, what you actually do with it.
I remember something with caleed MUI meaning Multi-Instancable back in Wc3 times. Now i dont even care about it.
Also it was the case if you used "Wait x" now you store player as p and your 100% sure it will work. All variables are locals now.
But you get it wrong here. You still should store Things like "Triggering Player" "Last created unit" etc if you use waits. Probably similar precautions should be taken when you run action/function in new threads. On other hand forget about leaks unless threes is GUI option to destroy something you don't
Half true. Local variables are local, there are also global variables which you can place in the same location as your triggers, folders and action/condition/function definitions
On topic, I don't see how a trigger could mess up if multiple people triggered it at the same time (the chance of that being ridiculously small as well, and unless you use a wait action, the triggers will run on after the other)
The only way you can ahve them interfere with each other is by using and modifying global variables AND using wait actions at the same time, which is easily solved by using local variables.
As the title says. Is the "Any Player" option MPI, or will I need to use Player 1, Player 2, Player (...) instead?
Additional Info: The Any Player option is an event/condition, not an action.
MPI means that the trigger can be ran multiple times at the same instance by many players, meaning that if two players trigger the event at once, the trigger won't screw up.
Shameful bump. Really need an answer.
What's MPI?
Picked player resolves the matter...
It's an event...
If you know about Picked or Triggering Player, what exactly is your problem? Describe exactly, what you want to do; an event cannot be described as MPI or not, it depends, what you actually do with it.
WTF is "MPI"
your question makes no sense....
Warcraft 3 Triggering term. It means that many players can trigger the same action without it screwing up.
My question is, can I use the "Any Player" option in my events rather than having to input "Player 1, 2, 3, etc..."?
Yes, for most events you can.
I remember something with caleed MUI meaning Multi-Instancable back in Wc3 times. Now i dont even care about it.
Also it was the case if you used "Wait x" now you store player as p and your 100% sure it will work. All variables are locals now.
But you get it wrong here. You still should store Things like "Triggering Player" "Last created unit" etc if you use waits. Probably similar precautions should be taken when you run action/function in new threads. On other hand forget about leaks unless threes is GUI option to destroy something you don't
@Nerfpl: Go
Half true. Local variables are local, there are also global variables which you can place in the same location as your triggers, folders and action/condition/function definitions
On topic, I don't see how a trigger could mess up if multiple people triggered it at the same time (the chance of that being ridiculously small as well, and unless you use a wait action, the triggers will run on after the other)
The only way you can ahve them interfere with each other is by using and modifying global variables AND using wait actions at the same time, which is easily solved by using local variables.
I personally use Any Player, i just use 'Triggering Player' to get the player who triggered it.