UnitDex - Unit Indexer - reforged

[kokon]

Im trying to set up Unit Dex in Reforged.

[System] UnitDex - Unit Indexer

System Code library UnitDex uses optional WorldBounds, optional GroupUtils /*************************************************************** * * v1.2.2, by TriggerHappy * ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ * UnitDex assigns every unit an unique...

www.hiveworkshop.com

But I think this line does not work:
//! external ObjectMerger w3a Adef uDex anam "Detect Leave" ansf "(UnitDex)" aart "" acat "" arac 0

can you help me?

 

[Uncle]

Im trying to set up Unit Dex in Reforged.

[System] UnitDex - Unit Indexer

System Code library UnitDex uses optional WorldBounds, optional GroupUtils /*************************************************************** * * v1.2.2, by TriggerHappy * ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ * UnitDex assigns every unit an unique...

www.hiveworkshop.com

But I think this line does not work:
//! external ObjectMerger w3a Adef uDex anam "Detect Leave" ansf "(UnitDex)" aart "" acat "" arac 0

can you help me?

8. Notes

• ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
• - This system is compatable with GUI because it utilizes UnitUserData (custom values for units).
• - The object merger line should be commented out after saving and restarting.

Just delete that line of code, it's not doing anything important.

 

[Pyrogasm]

Since Uncle didn't say: ObjectMerger is an old JNGP tool that used to be integrated into that editor. ObjectMerger creates new objects (units, upgrades, buffs, etc.) with lines of code instead of having to make the ability yourself in the OE; it is capable of setting any fields in the output object to any value they could reasonably take.

JNGP is now deprecated and that ObjectMerger functionality was not ported over to the post-Reforged World Editor. It's possible to get ObjectMerger lines to run still (search a bit here and you'll find the threads, I've replied to them) but generally it's not needed. That line was only ever intended to run once to make the ability. You can also recreate what it would do by hand if you want, just by reading the OM syntax from left to right:

//! external ObjectMerger w3a Adef uDex anam "Detect Leave" ansf "(UnitDex)" aart "" acat "" arac 0

• White: main OM invoking line
• Red: w3a means it's an ability, Adef is the rawcode of the ability this will be based on, and uDex is the rawcode for the new ability this will create
• Green: the field anam is given the value "Detect Leave"; this is the name of the ability, and you can see what anam corresponds to by pressing ctrl+d in the object editor window for the ability to show the raw data fields (they all have a 4-character name under the hood)
• Blue: the field ansf is given the value "(UnitDex)"
• Purple: the aart field is given the value ""
• Yellow: the acat field is given the value ""
• Orange the arac field is given the value 0
• all other fields remain idental to the ability this OM was based on (Adef, which is human defend)