Just store the address when you originally find it.
Alright so I can scan for an address and utilize it just fine. The issue is, after catching the address and modifying it's bytes my trainer can't scan for it's address to disable it. This is because the bytes at the given address are now shifted. Of course I can fix this by creating another scan for the modified bytes, though there's just so many hacks on my trainer it would take me a few hours to get everything working the way I'd like. I'd like to ask for any ideas on how I could catch the address to enable and disable.
IE;
Code:DWORD NewAddy() { code here return Addy; }Code:void EnableHack() { write bytes(NewAddy()) }After enabling the hack it's impossible to catch the address again.Code:void DisableHack() { write bytes(NewAddy()) }
Just store the address when you originally find it.
You should have an initializing routine which finds the addresses of the signatures when your trainer loads and stores them for later use. Then you can unpatch/repatch at will.
Trivial example:
Code:void *pHackAddress1 = NULL; void init(void) { pHackAddress1 = (void*)SignatureScan(...); }
You can win the rat race,Originally Posted by Jeremy S. Anderson
But you're still nothing but a fucking RAT.
++Latest Projects++
[Open Source] Injection Library
Simple PE Cipher
FilthyHooker - Simple Hooking Class
CLR Injector - Inject .NET dlls with ease
Simple Injection - An in-depth look
MPGH's .NET SDK
eJect - Simple Injector
Basic PE Explorer (BETA)