How do you make your cheats VAC proof?

[memerstar]

Currently making bhop and wall hack cheats for CSGO, I don't know to make them VAC proof. Anyway to do them?

[Hunter]

/Moved to the correct section.

[DarknzNet]

If you make hack yourself dont release it to public and it will most likely be ud for long time. Unless you c+p a source code and only change offsets/some variables it will be detected.

[gigagiga]

update structures time after time, check hex and compare if there is much the same as before

[derkrasseboy]

bhop and wall hacks are easy to do, so you can make it the most complicated way it could possibly be and youll be safe haha

[Lols12342]

Add junk code. People say it doenst work but it does.

[antep2727]

Add junk code. People say it doenst work but it does.

only works if optimization is disabled in your compiler settings

[ImWhacky]

Don't copy pasta source codes, change variable names, change structs somewhat often, don't name you cheat "CSGO CHEAT" because i think vac checks that stuff (I'm probably wrong), add junk code (don't have optimization enabled), don't make the cheat public. I've been following these and my private cheats have been ud since I made them.

[4773n0x]

Just code your own stuff and don't share it to the public. That's all you need.

[affe2626]

Don't copy pasta source codes, change variable names, change structs somewhat often, don't name you cheat "CSGO CHEAT" because i think vac checks that stuff (I'm probably wrong), add junk code (don't have optimization enabled), don't make the cheat public. I've been following these and my private cheats have been ud since I made them.

Well my cheat is named CSGO Cheat so ur wrong lol

[ImWhacky]

Well my cheat is named CSGO Cheat so ur wrong lol

mine was named "L33T M4D HAX" before i was told vac checked it lmao

[antep2727]

Don't copy pasta source codes, change variable names, change structs somewhat often, don't name you cheat "CSGO CHEAT" because i think vac checks that stuff (I'm probably wrong), add junk code (don't have optimization enabled), don't make the cheat public. I've been following these and my private cheats have been ud since I made them.

variable names are ignored by the compiler. So no need to change them, take the most comfortable for you.

[WasserEsser]

Don't copy pasta source codes, change variable names, change structs somewhat often, don't name you cheat "CSGO CHEAT" because i think vac checks that stuff (I'm probably wrong), add junk code (don't have optimization enabled), don't make the cheat public. I've been following these and my private cheats have been ud since I made them.

mine was named "L33T M4D HAX" before i was told vac checked it lmao

VAC doesn't do anything against window titles. Different variable / function names don't have any impact on the compiled binary.