SUPER HAXZORZ ( this is a serious question )

[J0nathan27]

hi i have been reading c++ primers plus 6th edition, now i just finished reading the whole book and i also know a good amount of windows api, so now to my question . Could i make some basic hacks with this knowledge

[atom0s]

In short, yes. Your best bet is to start with trainers, simple memory edits and so on. Don't worry about things like DLL injection, hooks, etc. yet until you get a better feel for things.

[J0nathan27]

okkk ome thing that i do not understand is how bypasses wirk

---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------

In short, yes. Your best bet is to start with trainers, simple memory edits and so on. Don't worry about things like DLL injection, hooks, etc. yet until you get a better feel for things.

okkk one thing that i do not understand is how bypasses work, like if i memory edit something and its like multiplayer and it has a good anti cheat how would i like ya

[atom0s]

Understanding an anti-cheat is a bit more out of your range for just starting.
You will need to debug and understand what the anti-cheat is doing to prevent it from detecting your edits / tools.

Each anti-cheat has its own methods and similar methods to others.

It can be as basic as simple things like:
- Window name detection.
- Process name detection.
- Window layout / control position and property detection. (Such as detecting Cheat Engine based on its layout.)

It can then lead into more complex things like:
- Process handle detection.
- Debugger detection.
- Memory change detection. (Can be from protection change detection, Crc checksums on memory areas, etc.)
- Breakpoint detection. (Software and hardware.)
- Jump / detour detection by comparing function stubs etc.
- IAT / EAT change detections to locate IAT hooks and so on.

It's no a simple task to jump in and bypass an anti-cheat right away. Without prior knowledge of what you are doing or what the anti-cheat does, it takes a bit of work to debug and find what you need to bypass.

[J0nathan27]

Understanding an anti-cheat is a bit more out of your range for just starting.
You will need to debug and understand what the anti-cheat is doing to prevent it from detecting your edits / tools.

Each anti-cheat has its own methods and similar methods to others.

It can be as basic as simple things like:
- Window name detection.
- Process name detection.
- Window layout / control position and property detection. (Such as detecting Cheat Engine based on its layout.)

It can then lead into more complex things like:
- Process handle detection.
- Debugger detection.
- Memory change detection. (Can be from protection change detection, Crc checksums on memory areas, etc.)
- Breakpoint detection. (Software and hardware.)
- Jump / detour detection by comparing function stubs etc.
- IAT / EAT change detections to locate IAT hooks and so on.

It's no a simple task to jump in and bypass an anti-cheat right away. Without prior knowledge of what you are doing or what the anti-cheat does, it takes a bit of work to debug and find what you need to bypass.

thanks dude for all of your help