Protection methods

[Eradicator]

Does anyone have a list of all (majority) of the various protection methods available, aside from JASS methods?

Thanks.

[L0K3]

Vex's Optimizer
Widgetizer
HeavyLocker

Damaging the MPQ headers:
"The first four bytes of the map hold the filetype-identifier (usually "HM3W"). We'll leave that and the next 508 blocks alone. The next four (4th, 5th, 6th and 7th) bytes always hold hex: {0×00 00 00 00}. The following 508 bytes hold the map name, some data with unknown purpose, some more nullbytes and then finally, after byte 512 the MPQ file begins with "MPQ " and hex {0×20 00 00 00} Which is actually another (but smaller) header, and we can damage it:
Leave the string "MPQ " alone, and change hex {0×20 00 00 00} after it to hex {0×33 49 43 45} (We are at byte 516 now) and MPQ extractors will fail to open the map. Warcraft does not look at this information, so your map will be still playable. This method effectively crashes most deprotector scripts and programs, but any knowledgeable user can reverse the effect within seconds so it'll only help against beginners."

The 3 programs up top are probably the easiest way of protecting a map.

[Eradicator]

I'm aware of the programs, but what do they actually do?

Vexorian's obfuscates war3map.j, and deletes editor-only files. I'm not sure what the other two cover. I found this, but which of those actually cause the map to fail to open in the editor?

[Risen]

Widgetiser makes the deprotection process 3x longer but nothing serious, I would use it anyways, since it decreases map load time.

The best protection method is the internal clockwork of your map. (Stolen from Aero)

There are plenty of Jass exploits that can prevent an inexperienced user from touching your map.