16:29, 28th Jun 2011
Maker: Approved. Can be of great use in creating MUI spells and systems.

 

Does this mean that this trigger can count units for you and give the unit a special code?

 

If you mean counting how many units are in the map at once, no this is not what it's used for.

The custom value of the unit is a mere integer used in array lookups to make indexing more automated (user-friendly).

• Set MyData[(Custom value of (Triggering unit))] = 1000

^The above example effectively allows you assign "1000" to the unit as a pseudo-attribute. Normally in this case, data attachment would involve hashtables.

 

This really deserves a DC
A UnitIndexer is ok, but a UnitIndexer for GUIers?? That is above and beyond
The only problem is that some GUIers use custom values for other stuff
If they do, it's their loss xD
Good Job dude sir Bribe 5/5 ^^

 

LOL what is this?! You know that GUIers doesn't use unit indexers for some what unknown reason.

The filter should filter out units with locust btw.

 

It intentionally enumerates units with locust, because dummy units like projectiles can benefit from indexes.

However, I should make it clearer what users can add to make it filter out unwanted units.

Jesus4Lyf used a very similar approach in his "GUI AIDS" so I cannot take credit for the idea. This is simply a different implementation and has some pros and cons against his:

	Jesus4Lyf - Uses a timer throughout the game to check if units should be removed - As a consequence, only removes up to 32 dead instances per second, making it (in a stretch of the imagination) possible that the digit 8190 can be exceeded (more a logical problem than a practical one) - Ends up being more efficient when units are created - Pretty easy to implement (3 sets of cnp)	Bribe - Checks for removed units only when a new unit is added to the map - Does a quick iteration over all indexed units each time a unit is added - Ends up being more efficient over the course of the game, using fewer handles - Easier to implement (two cnp instead of 3)

 

But the timer option in AIDS is optional from my experience. Else it uses the classic "undefend" ability to detect leave/removed instances.

Yeah you're probably right about the dummies now when I think about it, GUIers will gain alot by this.

Does the userdata always return 0 when a unit is removed/decayed? Cool.

 

His GUI version of AIDS only uses a timer, it doesn't have an option for the undefend bug.

GetUnitUserData returns 0 for null/removed/decayed units. The wc3 system does some internal deallocation when units pass from scope - an event Blizzard forgot couldn't be bothered with to give us access to.

 

I'm really, really confused by this. But from what I gather, this replaces hashtables right? So you could put the custom value of whatever unit in a spell, and it will make it MUI, so long as you don't have 8190 units on the field, right? If that's what it does only problem I see with it is that is uses custom values. A lot of system use custom values

 

Those other systems shouldn't be using

SetUnitUserData

, but should rather just be assuming that a unit indexer is in the map and make use of

GetUnitUserData

= )

 

Update to 1.0.0.1 - added an optional filter and an optional initializer.

Before, it was unclear how to filter units.
Now, you can filter units from the UnitIndexFilter function in the custom script.

Before, if you needed to get the custom value of a unit during map initialization, it may have returned zero.
Now, you can run any of those triggers from the designated spot in the Unit Indexer trigger (where it says "run initialization triggers after this line").

With these changes, this system is now perfect unless the user calls SetUnitUserData (sets the custom value of the unit) themselves. However, users should not be doing that if they want to use this system (only calling GetUnitUserData).

Finally, no map that exceeds 8190 units can be taken seriously. The array limit in that case is out of the question.

 

i still do not understand what does a indexer do? Could someone explain this a little more if you have the time?

 

It gives each unit a unique id that can be used as an array index.


So rather than (hashtable)

SaveInteger(table,GetHandleId(unit),0,value)

you can do (array)

set a[GetUnitUserData(unit)]=value

 

Updated description with a short text on why unit indexing is important.

 

hi i'm new to mapping and am having trouble on how to use this system in my map.

i followed the steps and added the system to my map.

i didn't edit anything, i.e, Unit Indexer trig and the jass script located on map name.

i tried setting custom integer variable to triggering units custom variable to my spell

and when i try to multi cast the spell with 2 different units with 2 different custom values, it doesn't work. The last casted spell overwrites the first one.

could someone help me fix this?

i have attached the map to this post.

thanks =)

 

Make sure you properly affix the map . . . Because it isn't showing up. Once you attach the file you have to also click the little attachment button to put in the attachment in the post somewhere.

 

yeh just fixed it, i attached the wrong map b4 so i edited it lol

 

You have waits in your spell. Even with a unit indexer, waits will overwrite the data previously stored. To avoid this, DON'T USE WAITS. Look up some tutorials on making spells MUI. Just in case you don't, heres a simple breakdown. Don't ever use waits in spells unless you use local variables. Any spell that isn't instant needs a unit indexer (this very thing , hashtables, or recycling. Next time you post something about triggers it should probably be under the "triggers and scripts" part of the help section.

 

Updated to 1.0.1.0, this version now recycles every 15 new units as an optimization. The demo map has been updated to be more dynamic - you can type commands to create new units, display their indices and click on them to remove them from the game. This is to better show off the index recycling as the old demo I had won't work with the new "recycle every 15 new units" setup.