Cheat Engine

[RaDeX_Dark]

http://forum.cheatengine.org/viewtopic.php?t=595142

Honestly, in my opinion, if you want to create a "super secret game hack" don't release it to the public, or don't be lazy and use a backend like cheat-engine.

LUA bytecode is pretty easy to decompile. Hell there are multiple opensource decompilers out there, even themida and the like are relatively straight-forward to circumvent if you know what you are doing and are determined. Hell if all else fails just hook WriteProcessMemory and the like hahahah

I think the decode/encode functions should rather be called compress/decompress, and add in a LZMA layer before the Base85

I'm still trying to work my way around lazarus (its an incredibly messy IDE), but I've been adding compression functions to things like the data dissector and I have had massive space savings when leaving the structures intact. Take a 5MB structure down to ~110kb.

[mgr.inz.Player]

For data dissector I also made simple RLE compression. Even such simple compression can make a huge difference.


My cheatengine GitHub fork has such modification.

[RaDeX_Dark]

[mgr.inz.Player]

Great, but, I prefer human readable compression. For example, this has 256 pointers (64bit) and it is saved like this:

[Dark Byte]

of course you can use a lua decompiler to figure it out, but at least this stops the dumb people that only scan for a string in your script and then copy/paste the memory

and you can always wrap encodeFunction/decodeFunction in your own encryption engine if you like

also, try to decompile the script i posted in that topic, it's not something you do in one step

as for compression, if you really care about a MB more or less, turn on compression in the folder you save your cheat tables
but i'll add mgr. inz. player's compression method, assuming it won't break weird situations (e. g 50 times the same offset with the same type should be valid and reconstructable) havn't had a chance to test it yet