VAC "Bypass" answering

[Anomxus]

I see alot of questions on Fleep's videos wondering how to make their triggerbot/auto bhop undetected by VAC.

The reason you get detected by VAC using 'WriteProcessMemory' is because VAC does not want you to edit variables. Instead you could use something to simulate a mouse/keyboard click.
I personally use 'keybd_event' to simulate clicks on keyboard/mouse. But I have notices a few bugs with it. I'm pretty sure you can only simulate mouse-clicks, which sucks.

But as said don't use 'writeProcessMemory' if you are going to do anything VAC related.

 

[WiTH]

WPM is still undetected... You just have to be careful to what you're writing to.

 

[Szaka]

If you debug the app you will know whats detected and what is not. Just study taregt with olly

 

[WiTH]

If you debug the app you will know whats detected and what is not. Just study taregt with olly

It's not so easy to know what's detected, vac is a hard anti cheat to reverse. If someone is interested in more information about vac they should check gamedecepticon.

 

[Szaka]

Its called decompiling, reverse engineering, disassembling and debugging

 

[squeenie]

Its called decompiling, reverse engineering, disassembling and debugging

You say it like it's so simple

 

[brinkz]

Its called decompiling, reverse engineering, disassembling and debugging

You never know exactly what VAC detects at the moment, because VAC3 is streamed and can always have new detection routines and stuff, for the rest wav really posted much stuff on GD about VAC.
But still, WPM in the right sections is NOT detected. But yeah using things like keyb_event or SendMessage or whatever is still better to use, 1 Offset less to update and also not the risk that you write into critical sections after an Update (where you forgot to update this offset or whatsoever).