protect a 1.17 map cause fatal error

I used to develop an map under 1.15WE+WEU1.15, it works well with extprotect or w3mmsater.
But when I upgrade to 1.17WE+WEU1.17, the unprotected map can work, but the protected map (either extprotect or w3mmaster) cause a fatal error at the time I try to select the map. What is the problem and how to resolve? Pls help me.

I use normal editor with EXT protect and it works fine for me. So all i can say is it works for me in this situation, sorry i cant help otherwise.

Heavy Locker and ext protect tend to have trouble with 1.17 maps that use certain triggers. The easiest, most failsafe way fo protecting a map is to create a blank notepad file and use it to overwrite the GUI triggers in your map. THere's a tutorial/post about that kind of protection somewhere in these forums... I can't remember the exact path of the .wtg file.

Alternatively, you could use vexorian's string optimizer program. It also handles protection. It's available in the editing tools forum.

thanks for your reply~~~~, do u mean I have to use winmpq to do manual protect? :(

You import the text file like you would import a new model. You'll have to find out what the exact path for the file is, though.

If you use winmpq, you might as well just delete the .wtg file instead of replacing it...

Note that this kind of protection isn't as secure as HL or Extprotect that use obfuscation and other techniques to make even the raw JASS illegible.