Does this loop work?

[Craphter]

So I know loops have been around for quite a while, but I never really understood them. Today I decided it's about time, so I made my first loop.
I want to set every player (there are 10 players) current lumber and gold to 0

• For each (Integer A) from 1 to 10, do (Player - Set (Player(((Player number of Player 1 (Red)) + 1))) Current gold to 0)

Does it work?


And in a completely unrelated topic, what the f**k is MUI and MPI? I read these initials everywhere, I tried searching for it, it seems everybody was born knowing what they stands for.

 

[wyrmlord]

So I know loops have been around for quite a while, but I never really understood them. Today I decided it's about time, so I made my first loop.
I want to set every player (there are 10 players) current lumber and gold to 0

• For each (Integer A) from 1 to 10, do (Player - Set (Player(((Player number of Player 1 (Red)) + 1))) Current gold to 0)

Does it work?

Not exactly. That will set the gold for player2 to 0, 10 times. Instead, you want the loop to look something like this:

For each (integer a) from 1 to 10 do:
Player - Set Player(Integer A) current gold to 0

And in a completely unrelated topic, what the f**k is MUI and MPI? I read these initials everywhere, I tried searching for it, it seems everybody was born knowing what they stands for.

If a trigger is MUI, it means that trigger will work no matter how many units/player/etc are using it at once. Ideally, all necessary triggers in a map would be MUI if they need to be (such as triggered spells).

MPI means that the trigger is able to be used by every player at the same time, but not multiple times at once by the same player.

 

[Craphter]

Thank you very much wyrmlord.
One last question, do MUI and MPI stand for anything?
+rep

 

[PurgeandFire]

Multi-unit instanceability and Multi-player instanceability.

MUI - Able to be cast by more than one unit at the same time and stay fully functional.

MPI - Able to be cast by more than one player at the same time and stay fully functional.

 

[Craphter]

Thanks

 

[Dr Super Good]

Loops in WC3 work like this.

loop
exitwhen [boolean]
endloop

Where [boolean] is a variable or statement which generates a boolean value (usually a condition).

The code inbetween loop and endloop will be repeated infinatly until an exitwhen statement is given a true boolean value or a thread crash occurs. Loops may use more than 1 exitwhen statement to break out from many points within the looping code.

Some uses people often forget about.

exitwhen false //completly redundant waste of time line, never use
exitwhen true //will always terminate the loop (breaks out of loop)

A thread crash may occur on some invalid parameters (division by 0 or passing stupid values to natives) or when the op limit is exceeded (too many instructions are executed without some pause).

The crappy for loop actions that GUI use are constructed from the above structure. Idealy you want to difine your own looping structure as it allows for more flexibility with your code flow and can increase efficency.

 

[Craphter]

Thank you very much Dr Super Good.
It's more or less a like a for in programming, but I can't really think of much uses for it...

 

[Dr Super Good]

You can use it for some kinds of indirect searches for values. Additionally, sorting algerthims can benifit from this (for a score board for example).

I agree however that a lot of the time it will be used as a slightly less neat for loop.