Counter-Strike 2 players are being hit with VAC bans for setting their DPI too high, with the AI overwatch detecting the quick jittery movements as hacks.
Counter-Strike 2 has finally gone through the first month of its full release, with a whole tournament being played between, however, bugs have inundated the game since release.
From the more innocent bugs such as the “Michael Jackson peek”, to the more serious problems of peekers’ advantage which has had a lot of players and pros alike complain.
However, a new bug has been discovered where players have been receiving VAC bans on Steam for having DPI settings that were too high for the game’s liking.
In extreme cases, it only takes one minute to trigger this bug, I tested this extreme case, that is, during the warm-up phase, the mouse dpi is turned to the maximum, even in casual mode, after you hit a teammate, it will trigger AI overwatch and get a game ban pic.twitter.com/pqQBad12AE
— Jigglypuff (@Jigglypuff64942) October 22, 2023
According to players who were unexpectedly hit with the bug, and those who tested it out, if you were to change your mouse’s DPI to its max mid-game, which is around 16,000 to 25,600 depending on the mouse, and start spinning around frantically, you can get a VAC ban.
Subscribe to our newsletter for the latest updates on Esports, Gaming and more.
The ban can happen regardless without anyone reporting you. Rather, as players speculate, CS2’s new AI overwatch, which is Valve’s proprietary software to determine if a player is cheating, is seemingly falsely banning what it perceives as aim hacks.
And players have been documenting this bug. Various users across Twitter, Reddit, and even Chinese players on Bilibili have been demonstrating how replicable the bug is by recording themselves getting banned on new accounts.
It may seem ridiculous for a player to do this in the first place, however, increasing your DPI and spinning around madly is a plain old fun thing to do while in a casual game for players, which was exactly how one user on Reddit discovered the bug when they were hit with a VAC ban while doing it.
Valve has yet to respond to the bugs, however, Valve has been updating CS2 regularly since release, so a quick patch to the bug is most likely coming in the next week.