Hex's Anti-Cheat & CFG Source Code
You're probably too retarded to understand how it works.
Anyone intelligent enough would not release anything 'good' to feed skids.
Just don't touch << too much >> the .text region and you're fine, ******.
What the fuck are you even saying, you can hook DirectX safely, retard.
Conclusion? Stop misinformating people. You make yourself look stupid.
Also,
you're going to need the source code of the binary in order to paste your hack in.
Anyone intelligent enough would not release anything 'good' to feed skids.
Just don't touch << too much >> the .text region and you're fine, ******.
What the fuck are you even saying, you can hook DirectX safely, retard.
Conclusion? Stop misinformating people. You make yourself look stupid.
Also,
you're going to need the source code of the binary in order to paste your hack in.
No. You can use a code cave.
EDIT: Just push the name of the file and call LoadLibraryA.
Loading the hack.

View of loaded modules.

You have to put all your hacking stuff in DllMain, which is the entry point called after LoadLibraryA, I think. I don't know how you guys will get the Lua state from there, lol good luck. Anyways, the point being, you insert that somewhere into a module loaded by Garry's Mod, jump to it, and jump back after loading your module.
EDIT: Just push the name of the file and call LoadLibraryA.
Loading the hack.

View of loaded modules.

You have to put all your hacking stuff in DllMain, which is the entry point called after LoadLibraryA, I think. I don't know how you guys will get the Lua state from there, lol good luck. Anyways, the point being, you insert that somewhere into a module loaded by Garry's Mod, jump to it, and jump back after loading your module.
I believe tdsx is correct, although code cave is just a place to store run-time-generated code it's better then using dlls to inject and considering it is a self-modifying code so it would be scrambled or randomized. (Correct me if I missed something)
And TroubleMakers, there is no need to insult or flame at other people if they don't know something or the fact that it might be incorrect, that's just being plain rude and it's not appreciated. Maybe you could just tell them how they are incorrect a nicer way, that would be appreciated.
And TroubleMakers, there is no need to insult or flame at other people if they don't know something or the fact that it might be incorrect, that's just being plain rude and it's not appreciated. Maybe you could just tell them how they are incorrect a nicer way, that would be appreciated.
Jesus christ, this is giving me a headache so let me clear it up.
1. Modifying "client.dll" WILL NOT get you VAC banned. (In GMod.)
2. DirectX hooking CAN get you VAC banned IF it's done incorrectly, but it's very difficult to fuck up.
3. JMP hooking CAN get you VAC banned IF it's done incorrectly.
4. Externally drawing menus WILL not protect you from screenshots, render.Capture will draw the entire window.
5. Seed detection + Aimbot detection can be bypassed in HeX's AC.
6. Seed = "Verifying CUserCmd" there isn't really any other way to check it (that I know of.) directly from GLua.
7. Fakelag detection is a fucking stupid method of detecting a cheat, it's just a loss of packets, therefore, anyone losing packets will get caught (HeX wouldn't do this in the first place.)
8. Touching the .text section AT ALL can, and most likely WILL get you VAC banned, only .data and .rdata are safe to modify.
9. (This is directed toward Meep, who thinks they know so much about everything.)
Meep thinks this is not render.DrawWireframeBox, I can tell you, it is, I fucking made the cheat, I know what's in it.
1. Modifying "client.dll" WILL NOT get you VAC banned. (In GMod.)
2. DirectX hooking CAN get you VAC banned IF it's done incorrectly, but it's very difficult to fuck up.
3. JMP hooking CAN get you VAC banned IF it's done incorrectly.
4. Externally drawing menus WILL not protect you from screenshots, render.Capture will draw the entire window.
5. Seed detection + Aimbot detection can be bypassed in HeX's AC.
6. Seed = "Verifying CUserCmd" there isn't really any other way to check it (that I know of.) directly from GLua.
7. Fakelag detection is a fucking stupid method of detecting a cheat, it's just a loss of packets, therefore, anyone losing packets will get caught (HeX wouldn't do this in the first place.)
8. Touching the .text section AT ALL can, and most likely WILL get you VAC banned, only .data and .rdata are safe to modify.
9. (This is directed toward Meep, who thinks they know so much about everything.)
Meep thinks this is not render.DrawWireframeBox, I can tell you, it is, I fucking made the cheat, I know what's in it.
Ah, it looked like my old hack so I assumed it was mine. Mine used surface.* functions and no render.* functions. Judging by the name of the video I thought it was you showing off how "awesome" you are by getting my leaked hack and using it. Not my fault you are a ****** who only c+ps and calls everyone else a c+per.
Similar Threads
Combat Arms Hack Coding / Programming / Source CodeAnti-Kick & God-Mode - MORE! [ Source Code ]
15 Adventure Quest Worlds (AQW) Tutorials, Source Code & CodingAQW cheating 101[History, technical explanations, source code examples]
72 Combat Arms BR Hack Coding/Source CodeAnti-Kick & God-Mode - MORE! [ Source Code ]
55 Need for Speed World Helpwhat is the source code to bypass the anti hack
2 WarRock Philippines HacksAnti-AFK Ingame and Fast Lockon Source CodeWR 11
