Developer Insight - Fair Play Task Force Update
Anybrain anti-cheat integration is now live to detect hardware and software cheating, resulting in 296 bans for mouse-and-keyboard usage on consoles.
Key Changes
- 1Integration of Anybrain anti-cheat system to analyze player inputs
- 2Mouse-and-keyboard usage on consoles is now a bannable offense
- 3296 bans issued to console players for hardware cheating
- 4Refining detection for aimbots and scripting on PC
- 5Ping-based limitations moved back to the drawing board
- 6Deployed fix for increased CPU usage issues from update 2.7
- 7EULA updated to support new anti-cheat measures
All Changes
🛡️Anti-Cheat(5)
- newAnybrain: Partnered with Anybrain to collect and analyze in-game inputs for abnormal behavior detection
- changeConsole: Mouse-and-keyboard usage in controller environments is now a bannable offense on consoles
- changeConsole: Issued 296 bans on consoles for hardware-based cheating
- newPC: Implementing and refining detection for aimbots and scripting on PC
- changeEULA: Updated the EULA to support new anti-cheat detection and enforcement measures
⚙️Gameplay Systems(1)
- changePing-based limitations: Ping-based limitations moved back to the drawing board due to technical obstacles and complexity
📈Performance(2)
- fixCPU Usage: Deployed a fix to address increased CPU usage issues introduced in update 2.7
- changeCPU Usage: Ongoing investigation into remaining CPU usage performance issues
Summary
Anti-Cheat & Fair Play
Hunt: Showdown has partnered with Anybrain to enhance detection of hardware and software cheats. This system analyzes player inputs to identify mouse-and-keyboard users on consoles and aimbots on PC. The team also updated the EULA to support these new measures, opting for a strategic surprise rollout to maximize impact on bad actors.
Status Updates
While console enforcement has already begun, the team is currently refining PC detection criteria to ensure accuracy and avoid false positives. Additionally, the planned ping-based limitations have returned to the drawing board due to technical complexity. Investigations into CPU usage issues following update 2.7 are ongoing, with a partial fix already deployed.