yes nobody names his variables like that, map editor has an option to obfuscate the script by renaming variables into that. the fact that it is a locked map makes you a hacker lol. i really don't care about that and i don't really consider it a bad thing but stay with the truth.
The names are likely generated by hashing the variable name.
Frankly the obfuscation function is kind of bad. It does not support non-GUI at all and has caused many people headaches when an error free map throws errors during publishing.
In Warcraft III Vexorian's Optimizer did a far better job. Better still it was pure script only so it did not matter if you used GUI or JASS as it still worked.
It is worse then that. All the obsfucation does is take the 4 (now 8 because its 64 bit) byte ID of the element (function, variable, parameter, whatever) from the Triggers.xml file and substitutes it. It is borderline worthless. This is why it doesn't support non GUI, non GUI (custom script of any kind) creates a single ID entry for the custom script block, all the contained script has no corresponding entries into the Triggers.xml file, and thus isn't macroed/substituted.
I think it also appends the 4 byte library/document ID to it, to prevent collisions.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
<code>gt_E697A0E6958C_Init();
bool[9] gv_e697A0E6958CE78AB6E68081;
bool[9] gv50E5808DE78AB6E68081;
bool[9] gv100E5808DE78AB6E68081;
gt_D090D0B2D182D0BED0BFD180D0BED0B8D0B7D0B2D0BED0B4D181D182D0B2D0BE_Init();
gt_D097D0B5D180D0B3D0B8D092D0BED181D0BAD180D0B5D188D0B5D0BDD0B8D0B5_Init();
</code>
it's obfuscated script from the map you are trying to hack.
@FunkyUserName: Go
not obfuscated,just lock map
I'll trying to read
"e697A0E6958CE78AB6E68081"
this is variable name,why do you think I want hack,i just read and learn,this helps me to become a master
yes nobody names his variables like that, map editor has an option to obfuscate the script by renaming variables into that. the fact that it is a locked map makes you a hacker lol. i really don't care about that and i don't really consider it a bad thing but stay with the truth.
The names are likely generated by hashing the variable name.
Frankly the obfuscation function is kind of bad. It does not support non-GUI at all and has caused many people headaches when an error free map throws errors during publishing.
In Warcraft III Vexorian's Optimizer did a far better job. Better still it was pure script only so it did not matter if you used GUI or JASS as it still worked.
It is worse then that. All the obsfucation does is take the 4 (now 8 because its 64 bit) byte ID of the element (function, variable, parameter, whatever) from the Triggers.xml file and substitutes it. It is borderline worthless. This is why it doesn't support non GUI, non GUI (custom script of any kind) creates a single ID entry for the custom script block, all the contained script has no corresponding entries into the Triggers.xml file, and thus isn't macroed/substituted.
I think it also appends the 4 byte library/document ID to it, to prevent collisions.