- Unit Group is a list with units. Sadly we can only add new units to its end, so you would need to code other operations like adding at position 2 yourself.
Units have custom value 0 to 63 to store real values within them. Custom values are only accessible via triggers.
Dead units are removed out of this list, when their death time (unit data, how long a unit is kept in memory after death) runs out.
- Arrays have a static size. So, you would need to define it with the max size you require. They can only store one data type, but you can just add multiple arrays.
- Global Data Table can store values with a key. So, you would use a string key like "a2-2" to store 3. Every key needs to be unique, else you overwrite entries.Here are some limitations and knowledge about the data table.
- Then there is something with user data, but I've never used it. Maybe someone else can describe them.
So...: What do you want to save? How much do you need to save at max?
En7ropi Regular ShmoeHey there,
I am trying to generate some type of table of variable size (each row signifies a unit on the field- let's say 3 for this example). Periodically throughout the game, I want to update, reference, and (optionally) resize the table (in case of unit death, for instance). I'm not sure if a table is what it's called in the editor- I found variables, which I could form into arrays, but it seemed very clunky to manipulate and use the fields in them.
Any recommendations or tips on use? I was hoping to find something like "cooltable(2,4) == 3", which would set the 2nd row, 4th column field to a value of 3, for instance.