ExtProtect v0.1.0.0 Beta Released

Well, I realy like your tool, I dont think you should take it down in any way till Blizzard asks you to.

But ehh, I made a map in WE, protected it and tried to run it in WC3, but it makes WC crash even before it loads the preview screen, I can load the orginal one. If you like to, i'll send you my map+the protected one.

Send the map to my extprotect address (its at the link in my sig) and I'll look into it.

can u unlock the maps?

it seems weird i used your protector and... it put my map as a Reign Of Cjaos map not a The Frozen Throne map, it was weird... 0.o

If you protected it with a password, you can unprotect it by loading the protected version into the program and typing the password again. If you didn't store a backup or you forgot the password, there is nothing I can do.

If you don't type a file extension, it automatically selects w3m for you. If you're protecting a w3x map, either rename the protected file afterwards or type the extension in as part of the file name when you select the map

Though I have been using Ext protect with normal WE created maps without prob since ever, it doesn't work with maps edited with WE Unlimited. Can you make it compatible with WEU? Also, can you add campaign file protection like in heavy locker?

Anyways, I am still using ur program, and it is the best out there.

I can't fix a bug without a map that demonstrates the bug, and so far nobody has been willing to send me a WEU map that doesn't work. Right now I'm working on fixing some bugs demonstrated by another map somebody sent me, so it'd be good for somebody to send me such a map so I can make both fixes in a single patch.

I think people are afraid to send their original work. I'll make some maps with WEU with the problems I am facing. Should I post them here?

Ok, I am pmming you the link to the files. One is non protected WEU map with custom features I use in it. Other is the protected version by ExtProtect 1.1.0b. It doesn't open in WE, but it doesn't open in-game too.
I think you'll have to test WEU maps by downloading them yourself.

Extarius are you still working on Extprotect?
And Desmasic and Dargath plz use the "Edit" function and don't doublepost!

I'm working on it in that I'm still fixing bugs that make it unusable, but I am not adding new features or options etc. I do my best to drop what I'm doing and fix bugs as soon as people send me maps that have problems with ExtProtect.
Right now I'm working on making it work with WEU, which is a HUGE undertaking because I'm going to have to entirely redo the obfuscation, but it is a big bug and needs fixing.

I guess you're talking about problems with ExecuteFunc , or are there any other serious problems I missed?

ExecuteFunc is the big one, but there are also some trigger types that use quoted variable names (the ones dealing with variables changing)

Right now, my obfuscation is rather hackishly implemented, and I'm going to try to turn it into something more elegant. The problem is that I know what I need to do but not exactly how to do it, so I'm ordering some books on proper language parsing and I'll be learning it as I go. That means it might take quite some time to fix =-/

You people speak in languages i never knew existed!

So good being back. :-)

Well, let us see if the map protector works or not......

[testing]
Testing...
Testing...
Testing...
Still testing...
[/testing]

It works! I'll be damned.

However, i do have one concern with this program. It might have been answered, but i will ask anyway:

Where is the password stored? Is it stored in the map archive, or on the user's computer?
If it is stored on the map archive, what is to prevent someone from writing a program to search the archive for the password?

Just a few concerns about it. Nothing special.

The password is the encryption key for encrypting the backup data, which is then stored in the archive.
The password you enter when opening the protected map is then used as key to decrypt that data - if a invalid password is used, it will output a corrupted archive and therefore not work.
It's almost unbreakable