What you describe is perfectly normal for any protected map published to Battle.net. And it's part of procedure which Editor performs (or server, as I believe it actually happens server-side while publishing) in order to protect the map.
Triggers scheme file is completely lost at this point. But you can still put your modifications in Galaxy code.
Good point with TriggerString.txt, this file is relevant only to editor, thus should be erased too. Funny thing is that it can actually compromise MapScript.galaxy obfuscation (default one, at least). Because defined names there correspond to hashes editor uses to mask symbol identifiers.
I once was able to fully deobfuscate MapScript.galaxy (including restore of original names) thanks to this. The only thing that was missing were constant enums, as they have been inlined.
In addition to that there's one more component being removed while publishing as protected. It is Attributes, which stores data about lobby attributes, game varants and such. But it can be rather easly recreated by hand.
What you describe is perfectly normal for any protected map published to Battle.net. And it's part of procedure which Editor performs (or server, as I believe it actually happens server-side while publishing) in order to protect the map.
Triggers scheme file is completely lost at this point. But you can still put your modifications in Galaxy code.
Good point with TriggerString.txt, this file is relevant only to editor, thus should be erased too. Funny thing is that it can actually compromise MapScript.galaxy obfuscation (default one, at least). Because defined names there correspond to hashes editor uses to mask symbol identifiers.
I once was able to fully deobfuscate MapScript.galaxy (including restore of original names) thanks to this. The only thing that was missing were constant enums, as they have been inlined.
In addition to that there's one more component being removed while publishing as protected. It is Attributes, which stores data about lobby attributes, game varants and such. But it can be rather easly recreated by hand.
Previously known as: SomeoneTookMyNameTT