Valve officially declared Razer’s new keyboard feature, SnapTap, as cheating. The Gone Forever Cologne event wrapped up Monday night, and Valve released an update clearly defining its stance on null binds, including Razer’s SnapTap feature.
Razer recently announced an update for the Huntsman V3 Pro keyboard called SnapTap. SnapTap prioritizes the latest input between two selected keys without requiring the user to release the previous one. In a game like CS2, this feature provides near-perfect counter-strafing by essentially eliminating any errors when moving left or right. In CS, players maintain accuracy only when standing still, but during a brief moment while changing directions, accuracy resets. Achieving this requires a skillful release of the previous key before pressing the new one. This fundamental skill has been crucial in the game for years, and Razer aimed to automate this process.
Broader Concerns Beyond Razer’s Feature
Razer is not the only keyboard manufacturer with features that attempt to achieve similar results. In-game console commands, called null binds, also allow players to achieve the same effect. The Razer announcement reignited a longstanding debate about products and binds that eliminate human error. Skills like counter-strafing take time to master. An ongoing ethical conversation surrounds assisted peripherals like this. How far removed are SnapTap or null binds from a mouse that adjusts for recoil?
Razer’s esports ambassador explained that they conducted due diligence by consulting tournament organizers, who approved SnapTap. This approval raised concerns because many tournament organizers do not allow user-created null binds, which perform the same function. NA pro player and streamer Cooper publicly questioned a FACEIT admin, who confirmed that null binds are indeed prohibited but said nothing about Razer’s keyboard. This situation fueled claims that CS had essentially become pay-to-win, allowing players to purchase a skill that would otherwise take hours of practice to master for $300.
Valve’s Response
On August 14th, Gabe Follower tweeted a screenshot from CS2’s code suggesting Valve added a detection model for SnapTap. On Monday, Valve released a blog post titled “Sidestepping Skill,” identifying the rise of hardware features that blur the line between manual input and automation. They announced that, with the latest update, automation features that circumvent core skills would no longer be allowed on Valve servers. Players using these features would be instantly detected and kicked. As expected, automation quickly disappeared, and many celebrated Valve’s decision.
The Implications of Automation and Assistance in Games
The debates around SnapTap and jump throws share a common theme: automation and assistance in games. While some automated features offer an unfair advantage, considering whether to take a strict stance against all assistive features is important. Opening the door for these features could lead to unforeseen consequences down the line.
One example involves the vocal stance taken by pro player ropz. When SnapTap was first announced, ropz quickly called it cool but cheating, stating that it should be banned. Valve later validated his stance by acting against the feature. Despite ongoing debates, the community’s push for fair competition ultimately influenced Valve’s decision.
