Final Hurdles - drawing menus - detection
Final Hurdles - drawing menus - detection
Hey guys, ive spent the last two weeks pouring over c++ and have accomplished the following:
Injection of DLL
Actually attaching the dll
writing to and reading from memory - basic things in games like changed ammo, no recoil,
What I want to do know is start writing things for wallhacks and then latter aimbots.
QUESTIONS:
What do I need in order to code an overlay for a game when the hack in internal.
How does one go about making their hacks undetectable. I feel like hacking has been around so long that every method must have been covered (I know thats not true but some pointers would help).
Thanks in advance for any help given.
Injection of DLL
Actually attaching the dll
writing to and reading from memory - basic things in games like changed ammo, no recoil,
What I want to do know is start writing things for wallhacks and then latter aimbots.
QUESTIONS:
What do I need in order to code an overlay for a game when the hack in internal.
How does one go about making their hacks undetectable. I feel like hacking has been around so long that every method must have been covered (I know thats not true but some pointers would help).
Thanks in advance for any help given.
You could mess around with hooking, there are diffrent kinds of hooking.
For ex: IAT (?), VMT, Detouring and so forth.
You have to ask yourself, how and where does it detect a function, item or hook.
Then you can answer the question yourself.
Ofcourse, it's diffrent for each game.
Making a bypass would be far surpirior to any hooking changes.
I don't understand the first question.
Hope it helps!
For ex: IAT (?), VMT, Detouring and so forth.
You have to ask yourself, how and where does it detect a function, item or hook.
Then you can answer the question yourself.
Ofcourse, it's diffrent for each game.
Making a bypass would be far surpirior to any hooking changes.
I don't understand the first question.
Hope it helps!
