VAC & external

Over the years have developed very effective but “keep it simple” legit aim assist for CSGO.

It’s external and uses many winapi hooks checked by VAC
– CreateToolhelp32Snapshot
– Process32Next
– Module32Next
– OpenProcess
– ReadProcessMemory
– WriteProcessMemory

I know VAC is not caring about private externals coded from scratch and im undetected for about 2 years but i would like to get more advanced. Doing things different than mainstream seems to be a good starting point to stay more undetected.

What would be the way to go if i would like to VAC proove my external and learn new fancy stuff?

Driver development, reading network traffic..

Wouldn’t reading UDP traffic from network be undetected. One could read playerdata and use mousebased aim on that data. Like in Netshark GO back in 1.6.

I have been reading that VAC has access on driver level since it banned pay hack based on a driver. So making a driver that reads/writes memory would be as detetable as winapi calls, right? I dont know if it makes sense to put the effort in driver development and signing.

What you mean “protect your Process”? Isnt that even more obvious?

sure i mean api calls.

As im the only one using this hack and im like changing something to improve it once a week it would be unfortunate if it gets detected. But i have the feeling that at one point VAC is banning all externals with a big wave. Would be easy as far as i understand. I mean why the hell would any process read playerdata all the time. Its only a matter of time imho.