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.
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.