Extprotect or HeavyLocker for 1.15

There seems to be a lot of conflicting and confusing posts around referring to these two protection programs and am hoping somebody knowledgeable on the subject could answer a couple of questions?

1. Do these programs work with 1.15 maps?

2. Which one is better at protecting your map?

3. Does Extprotect reduce map size if you choose not to use the password recovery feature? If so, how does it compare to the reduction HeavyLocker yields?

1. ExtProtect definitely works
HL will not work very well in its current release (if you don't know exactly what options you can use and which options are buggy - there are pretty many options)

2. They're equal, they both apply the same changes to your map (only that the ExtProtect script obfuscation seems a bit more stable than the current HL obfuscation).

3. ExtProtect isn't made to optimize the size of your map. But it's true that it will be smaller if you don't use a password, because then no internal backup of the deleted files will be stored.
Real optimizations to the map size will only be done by Heavy Locker (which makes HL superior to all other protectors)

Although the name suggests the opposite I don't regard Heavy Locker as a Map Protector in the first place. The main application of HeavyLocker is (in my opinion) MPQ optimization (i.e. recompression with optimized settings).

Anybody know which functions in HeavyLocker are bugged and should not be used?

You better don't use script obfuscation.

And most of the file optimizations (txt, slk) might be problematic.

Everything else should work (of course only if your map has a complete listfile, otherwise the unknown files won't be carried over)

Would any of these apps have problems protecting maps using WE Unlimited since these maps have enhanced triggers in the archive?

I think they both have problems with the script obfuscation, because they would corrupt references to functions called through ExecuteFunc.

For HeavyLocker you can turn off obfuscation so you can try it with HL, but I think ExtProtect wouldn't be a good idea to use with weu maps.

If you're using the latest version of extprotect(available at the link in my sig) and the problem persists, please send the map that demonstrates the problem to the email address at the link in my sig.