ExtProtect v0.1.0.0 Beta Released

As PitzerMike said, the password is never stored anywhere. The program uses it to encrypt the backup and then throws it away. When you try to unprotect, if you give a wrong password the backup will not decrypt correctly and that is how the program knows you gave a wrong password. It is practically impossible to get the password out of the backup.

New Version of ExtProtect Out! - v0.1.2.0

(Link in my Signature as always)

Most problems with WEU are fixed. I will have to wait until my books get in before I can fix the rest, and that could be a few weeks. Most WEU maps should work properly now, as long as WEU doesn't do any fancy ExecuteFunc stuff (like making functions A_1 to A_9 and then doing ExecFunc("A_"+I2S(var)) or something like that)

If a string consists entirely of a variable name (with no extra letters or spaces etc), and the variable name is 6 or more letters, it will be replaced.

That's excellent.

Other map protectors that i have seen store the password on the map archive, therefore, somone just writes a script to search the map archive for the password, and then they can edit it freely.

Good thinking with the encrypting process.

Very good Extrarius.
Only one simple thing you should take into account. Almost everywhere, where WEU uses ExecuteFunc the user will pass in the function name in the form of TriggerName2Function("XXX")
This is for the GUI people to be able to access the actions part of a trigger. It Will be internally converted to Trig_XXX_Actions
So whenever you see any use of TriggerName2Function you should make sure that you won't mess anything up there.
Sorry I didn't mention that before, it just came into my mind right now.

EDIT: The place where you'll find the TriggerName2Function functions will never be within ExecuteFunc (In these cases it will always use string variables), but this shouldn't be the problem because you can simply search for all occurances of TriggerName2Function

PitzerMike: That is exactly the kind of thing I can't do in my current obfuscation function because it doesn't actually parse the whole script. It just looks for variable declarations (which always come after a type name) and replaces those and uses of the variables.

Once I get my books, I'll work on a real parser that can take everything into account, and it will do pattern matching etc to make sure all things passed to a function that takes a variable-as-string still work. That will require a great deal of time to implement though, so everybody will have to be patient.

Ok, well I ordered the book I needed from an Amazon Merchant (clearly labeled 'Condition: New') and it got in and its in _REALLY_ crappy condition(practically unreadable) so that will probably push the release back quite a bit since I have to get my money back and then order another one =-(