How to implement some sort of Vac Evasion?

[Skits]

Hi MPGH, Long time lurker, Over the past month or so I have been learning C++ and coding a couple of hacks for source and now GO.

However I'm wondering, what are some ways to avoid VAC Detection? I mean code wise not "keep it private" shit like that.

Are there any other ways? Its a very hard topic to research on.

Thanks :P

[Sandwich]

They're many resources on the CSGO forums of MPGH on this topic. I would recommend looking in the CSGO tutorial section.

[grunjrbr]

Look up the original thread for Merccy's polyhack. it's been undetected (publicly) for more than a month now.

he made it so his hack modifies itself every time you load it.

[ClimbingTheSkinLadder]

Yeah basically what grunjrbr, just look at the code for other hacks that stayed undetected for a longer period of time.

[moot_]

I'm not 100% sure on how VAC works, but maybe you could randomly generate a load of junk data on program launch.

[Merccy2]

There is literaly nothing else then keep your code private.

Some people will probably say something like driver cheats but those will get detected when they are public, just ad easily as normal cheats do.

I have a topic named The truth about VAC detection read that.

[Skits]

There is literaly nothing else then keep your code private.

Some people will probably say something like driver cheats but those will get detected when they are public, just ad easily as normal cheats do.

I have a topic named The truth about VAC detection read that.

I actually read that a couple days ago, my main question being, when somebody on MPGH releases a hack and it becomes detected, what do they have to change in order for it to become undetected(Aside from when offsets get changed). Do they just change the general code? or the way it reads the memory?

Thanks in advance.

[Merccy2]

I actually read that a couple days ago, my main question being, when somebody on MPGH releases a hack and it becomes detected, what do they have to change in order for it to become undetected(Aside from when offsets get changed). Do they just change the general code? or the way it reads the memory?

Thanks in advance.

The code //2short