Oh... nevermind. I think I just figured it out. It's a super dynamic array system that allows you to create a series.
Array field 1 being the first, will be accessed first. So if you wanted to store units inside of a trigger for example, you could create a double array this way and make the first array have a size of 3 so that 1 would be zerg units, 2 would be protoss units, and 3 would be terran units, then your second array field would be used to actually access the units themselves, whereas the first one would just be the races they belonged to.
So Variable[2][4] for example might be a Protoss Dark Templar.
I'm just messing around a bit more with some stuff in the editor to see what all I can do and ran into something weird.
Variables with arrays have 4 fields to define the size of the array. What is the intended use of the extra 3?
Just curious, Zeban
Oh... nevermind. I think I just figured it out. It's a super dynamic array system that allows you to create a series.
Array field 1 being the first, will be accessed first. So if you wanted to store units inside of a trigger for example, you could create a double array this way and make the first array have a size of 3 so that 1 would be zerg units, 2 would be protoss units, and 3 would be terran units, then your second array field would be used to actually access the units themselves, whereas the first one would just be the races they belonged to.
So Variable[2][4] for example might be a Protoss Dark Templar.
@Zeban: Go
Yep, Exactly. I <3 Arrays
Yes but how in the world do you access those? I am making a Zone Control And I have a Variable for Zones, Zone (9) (9)... I am new at this
I like to call them "Multi-dimensional" arrays.
Over9000[0-9000] .... Its over 9000 but do you know why?
SentOver9000ToAnotherDimension[0][0-9000] say hello to HFIL Mr. 9000
Take a look at my region tutorial in my sig