OutdatedMerccy's PolyLoader 2.1

A hack file is just a simple zip with the following files:
-command.txt
-inout.txt
-msg.txt
and a src directory.

So how do I make a hack file?
Step 1, modify your source code.
The PolyLoader uses a few tags to understand your file:

[swap_lines][/swap_lines] - Swap the lines between the 2 tags, useful for randomizing a structure.
[junk_enable /] - Enables auto junk code addition, the PolyLoader will add junk code after every ;
You can give it 1 or 2 parameters
[junk_enable 5 /] - Will add 5 lines of junk code after every ;
[junk_enable 5 10 /] - Will add 5 to 10 lines of junk code after every;
[junk_disable /] - Disables auto junk code addition.
[junk_enable_declares /] - The auto junk code generator will now only make declares (useful for in header files).

[add_junk /] - Adds a block of junk code at this position, it does NOT take junk_enable_declares into account.

[swap_blocks][/swap_blocks] - Works like swap_lines but instead it swaps blocks of code.
[block][/block] - Define a block
[enc_string_enable /] - Scrambles all strings, when you are using this make sure you have Decrypt.h included (the loader will generate a randomized Decrypt.h file).
[enc_string_disable /] - Disables the auto string scrambler.

command.txt
In command.txt you have to fill in the command line compiler options, here you have to link all the libraries etc... this one should work for practically any hack.
inout.txt
First line you put the filename the compiler generates (see the /OUT: parameter)
Second line the new name.
msg.txt
A message that will pops up when the user loads up the hack.

If you have any question regarding implementing this system sent me a pm .