I'm looking for a code obfuscator/scrambler/encrypter/encoder that supports AutoHotkey_L scripts. I've spent a bunch of time searching for one with no success, since the few readily available programs were either outdated or broken.
I am NOT trying to make my code more "secure" or "protect" it against ""theft"" whatsoever. I won't even compile it nor make it harder to reverse.
I'm just looking for a quick way to bypass basic automated file hash checks and RAM signature scanning methods commonly employed by anti-cheat solutions, without having to manually scramble each script.
Three "dirty" manual obfuscation methods I'm currently using consist in removing indentation (compiling a script does it), adding a useless comment after every line (regex), and replacing 1 space with 2 spaces in the entire script (regex again), but they're not exactly what you would call "optimal".
If anyone is aware of the existence of some maintained obfuscator tool, please let me know. What I'm especially looking forward to is some automatic way to instantly rename every variable in a script to something else. Bonus points if it makes use of randomness.
Any working code obfuscator for AHK_L?
Any working code obfuscator for AHK_L?
YOU'RE NOT ALEXANDER
Re: Any working code obfuscator for AHK_L?
Do your dirty manual obfuscation methods actually work?
I doubt code obfuscation would work myself. If I were designing an anti-cheat engine I wouldn't look in the code of a .ahk file, but Autohotkey.exe itself... I would assume it does that by mapping the hash of the AHK application to some list. Other possibility would be it blocking input from any process other than the OS.
If you need to change Autohotkey.exe you can download the source-code and iirc you can compile it with a different hash? Cant remember how though...
Another option is to use something like API Monitor to find out what the anti-cheat engine is doing and, well, block it.
I doubt code obfuscation would work myself. If I were designing an anti-cheat engine I wouldn't look in the code of a .ahk file, but Autohotkey.exe itself... I would assume it does that by mapping the hash of the AHK application to some list. Other possibility would be it blocking input from any process other than the OS.
If you need to change Autohotkey.exe you can download the source-code and iirc you can compile it with a different hash? Cant remember how though...
Another option is to use something like API Monitor to find out what the anti-cheat engine is doing and, well, block it.