CSGO Sticky thread

Valve patched this last night.


Why it took them this long, I don't know, but many exploits using this command are now null.

There are people who called this out in the past that have been schat on by some popular people within the CS community.

Some people who thought they were good at this game due to these 'legit' cheats, well, you are about to be very bad at this game.
 
Allegedly, Valve activated VACnet. Many internal cheats are being caught. It is also said that external cheats are caught. Some streamers who say they don't cheat are also VAC-banned. Forums are abuzz with players claiming to be legit who are alleged to be cheating by VAC.

All this happening with `exec_async` disabled. Hmmm.

Good.

I have no idea whether these are perma or temp bans.
 
Fulcrum29 said:
Allegedly, Valve activated VACnet. Many internal cheats are being caught. It is also said that external cheats are caught. Some streamers who say they don't cheat are also VAC-banned. Forums are abuzz with players claiming to be legit who are alleged to be cheating by VAC.

All this happening with `exec_async` disabled. Hmmm.

Good.

I have no idea whether these are perma or temp bans.
Click to expand...
What does `exec_async` disabled do actually?
 
TribbleZA said:
What does `exec_async` disabled do actually?
Click to expand...

Valve's ban wave is seperate to disabling exec_async, but it is inclusive in steps they have taken to mitigate cheating on VAC protected servers.

exec_async is a normal command, but it is used to execute inputs over an period, and isn't a single execution. What some players did was to create a bhop, spray control, anything they desired, script and made it run in a loop. It is a command that was being exploited. This command has been enabled since the beginning.

All I know is, Valve is testing how well their AI is trained.

They still can't block external cheats, but they are looking at in-game player behaviour.
 
https://twitter.com/x/status/1966962511565255073

Cheat community is crying that a silent update to CS2's VAC anti-cheat has annihilated almost all known cheats, including some wallhacks and trigger bots that work through DMA cards. I'm taking this information from their forums and Telegram channels. Obviously, I'm not sharing anything from them, but feel free to look for them yourself.

There's also a reddit thread about it, feel free to share anything you know there.

Apparently, this wave also nuked case farming bots!
Click to expand...

cbf4761956b14482e9b6cbf125530345.gif
 
https://www.reddit.com/r/cs2/comments/1ng6opf/1309_major_vac_live_updates_leaving_cheaters

13-09 Major VAC Live updates leaving cheaters crying​

Following a major update to VAC (live) detections, pretty much ALL big CS2 cheat providers are now detected. A beautiful thing is happening.

Across almost ALL (internal) cheat providers, people are crying. Amongst cheater communities people are reporting VAC Live's. Not just for 'rage' cheats but even when they simply inject or 'try to closet cheat'.

I will not be naming all the different providers, but anyone who searches for it can find this. Friends have been reporting VAC Live's in matches and people are sharing print screens from inside cheater communities where (said) staff is advising to not even load up cheats right now.

It seems Valve is cooking, delivering, and can count to 3.0 with VACNet actually doing something right now.

Have you all been experiencing more VAC live's cancellations ? Seen anything happen ?

The 'silent update' is reportedly pushed last night in the evening of 12->13-09. In the days before this, some providers were already on 'lock down' due to VAC waves hitting their userbase's.

Beautiful. Excited to see what is next and how this will evolve.
Click to expand...

I don't pity your loss.
 
For those who say that VACnet is catching DMA cards are talking crap. Valve doesn't have a kernel-level anti-cheat and thus won't know what a DMA card, Kmbox, or a Macku is. It isn't even limited to those. You can build your own with the right electronics. Cheats that are run on these are external cheats and are run on a secondary PC (or streaming PC). I am not going into depth on this, as I have touched on it in another thread. Fuser boxes and some KVM-type switches are used to overlay the two PCs, in layman's terms. These cheats are powered with vision-assist, trained recognition models. So, yeah, a GPU with good enough TOPS is required to run these models. Some GPUs are too slow to use localised vision assistance.

It isn't the hardware that is detected. VACnet compiles comprehensive metrics about you in-game. The parameters are unknown.

I am not sure how big this VAC wave is, but it might be the biggest to date. At this point in time, it is not possible to see the bans. Valve has limited API access and usage. The only numbers available are those reported by sites on which individuals are checked and tracked. Then there are those who are complaining.

Events like this occur in CS history, and each time they have only slightly inconvenienced cheaters. Unless they get their account banned with a large stash. Cheating communities have pretended in the past, too. Time will tell.

For Valve to roll out such a wave during a Valve Tier 1 event is unusual. False bans are a thing.
 
From reading elsewhere. There are no known permabans. The purge seems limited to VAC Live; in essence, all that is happening is match abandonments with timeouts. Eh, so, cooldowns.

Also, I had a look at some known cheats, internal and external, and they aren't expressing the issues as expressed by others. This is strange... However, Valve did tweak something.

I think Valve has doubled down on any and all input scripting. Valve disabled their own `exec_async` command, and it seems that any auto key (including mice) scripts are actively being suppressed. Yes, some keyboards even natively support these scripting inputs. Those who run these scripts, well, you are going to trigger a cooldown.

What did Valve tweak in addition, well, looking at what is public on cheating communities. The cheats that had been disabled are enabled again. Some cheat devs suggest not to rage, but to limit to legit or semi-rage cheats. A big thing being that when you are aiming at your target through a wall too long, a cooldown is also triggered.

It is suggested that smooth aimers should limit their max FPS to 120. Lol. Thus, it seems that aimbotting on large FOVs is also triggering cooldowns.

There is a lot more to dive into, but those who are using 'legit' cheats aren't in trouble, nor are those who use semi-rage.

In actuality, this isn't a big deal. Cheating continues... All noise, no real results.

😢
 
Looking at this sample:

Yeahno.png

Steam bans do not mean it is related to CS bans. As can be seen, VAC is steady as she goes. Whatever happened, in my opinion, the impact is minimal.
 
https://twitter.com/x/status/1966967661075603795

Let’s clear up what actually happened with VACLive.
No, Valve didn’t “wipe all cheats off the planet.”
No, this isn’t the end of cheating as we know it.
Relax.

VACNet ≠ VAC.
No signature bans, no injection flags.
What changed is behavior detection. The heuristic layer got sharper.

What does this mean?
If you’re still using semi-rage or “aggresive” tools, you’re more exposed than ever.
It’s pushing people deeper into closet-cheating territory. (ESP, radar, info-only tools.)

What didn’t change?
Humanized tools (VACNet is not that sharp yet) and… VISUALS.
VACNet can’t see that. That’s VAC’s job, and VAC hasn’t moved in years.

Is this progress?
Yeah.
After years of rot, they finally made a move.

Don’t fall for the “cheats are dead” headlines.
They’re not.
But today, at least, they got hurt.
Click to expand...

https://twitter.com/x/status/1967123312330309965

Important update:

Farming bots are already back online reconfigured to the new VACnet detection logic.

Uptime resumed in hours. So much for the “cheats are dead” narrative.

Also, wild idea: if you still think VACnet flags DMA cards or detects cheat code directly, maybe sit the next one out.
VACNet ≠ VAC. Say it with me: VACnet ≠ VAC.

The problem? Too many voices with big audiences still don’t get this.

There’s a difference between banning a cheat and flagging shared behavioral patterns across common cheat functionalities.

What happened was an update to the behavioral detection layer, probably some tweaks in the heuristics used to flag semi-rage and over-tuned automation.

Some bots and cfgs got clapped. Then they adapted.

You know how this game works, it’s cat and mouse. Always has been.

If your understanding of anti-cheat systems can’t distinguish between VAC and VACnet, or between client-side detection and server-side pattern recognition, might be a good time to observe in silence.

This is not about defending cheaters, it’s about calling bullshit when I see it.

Because if you fight cheating with misinformation, you’re just helping the problem.

Thanks for reading.
Click to expand...

I am more surprised by these voices with big audiences being silent on Valve disabling 'exec_async'. Then again, I know why.
 
Possibly the world's best CS2 player at this point in time.


Any discussion about nocries is being moderated to the extreme. Some within the community say he is legit. I mean, he's still on FACEIT and it has the 'best' competitive anti-cheat.

Also, the 'exec_async' restriction is, uhm, lol.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X