Protecting mods

Have you ever created a mod and had parts of it stolen from you by other users? Or maybe you want parts/all of it to be a secret to the public. Well, there is a way to stop anyone from gaining access. A program created by [A]Nobody, this clever but simple tool allows you to completely erase your coding from a .u file, but not affect the functional in any way. You may download it here.

This tool modifies a package file (extension — .u) in the way so noone else can see the source code even with the use of WOTGreal or other exporters. There are 3 levels of protecting: the first one is against the exporting of the mod's source code, the second and the third one protects the mod's binary against decompiling.

You can use the program in 2 ways. The first and simpliest way: just launch the program and specify the filename with extension and the program will pass your mod over all the three levels. You can use the second way if you need to choose between these 3 levels of protection. Run the program within commandline or batch file (.bat) with the parameters.

ModProtectionTool PackageFileName [options]

Parameters:

-ss — the program will remove the source codes against exporting
-fp —  the program will protect all function against decompilation
-np — the program will screw up the variables function identifiers (just if identifiers are marked with a  _   in the beginning of the name). 

Examples:

ModProtectionTool FLKeypad.u -ss -fp -np — 3 levels of protection to package FLKeypad.u

ModProtectionTool FLKeypad.u -ss— removes the source code against exporting and functions and against decompilation

ModProtectionTool FLKeypad.u -ss — removes the source code so noone else can export it anymore but don't forget that advanced users can still decompile it

We recommend to use always the source code removing (-ss) otherwise two other levels don't make sense.

© dxalpha.com, 2003—2007.