Led it

Hello i'm a very experienced coder and reverse engineer and today i'm sharing my suggestions to the VAC4 module!

As many of you know, the current VAC version is 3. VAC3 is very old and easily bypassed since it uses signature detection. Anyone can go online on cheat forums and download a source code and move the functions and variables around and they've bypassed VAC3!

Here are my suggestions to how we can stop these filthy cheaters from ruining our games!

Blocking off DLL injection is the key to success. Many cheaters are using manual map injected cheats. P2C cheats are usually doing this cause of the manual map injection process doesn't need the .dll file anywhere on the disk, it will just read the byte array and inject it straight into csgo.exe, undetected.

Blocking Writing/Reading Process Memory to csgo.exe, this is also a major thing in csgo cheating since glow cheats just write to the csgo glow struct and boom, enemies are glowing.

Instantly banning anyone hooking the vtables of CSGO, this is just blatantly easy for Valve to do and it's only used for cheating, also banning anyone bypassing VirtualProtect.

VAC Kicking anyone using radpi or anything related to it, it's used for aimbots and only aimbots. Come on Valve!

Valve should also make a kernel driver for their anticheat so that no one can mess with VAC!

Ban the cheaters ip addresses, mac addresses, cpu ids and bios strings!