Essay III · Tournaments
Fair Play on the LAN Stage
Offline events remove most of the privacy dilemma: the organiser owns the machines. They do not remove the need for rules, evidence and due process.
Why the LAN changes the problem
At a home PC, anti-cheat must negotiate with an owner who controls the hardware. At a LAN, the organiser controls the hardware, the network and the room. That flips the trust model. Tournament PCs can be imaged before each match, locked down, monitored by administrators and kept off the open internet. Running kernel-level anti-cheat on a machine the player does not own raises few privacy objections; the machine is equipment, like a referee's ball.
The weak points move elsewhere: to the peripherals players bring, to the people with physical access, and to the information that flows into the booth. Players usually bring their own mice, keyboards and headsets, and a peripheral with programmable firmware can, in principle, store macros or act as an input device for something else. Most major events now inspect peripherals and require software configuration to be done on admin-approved installs.
The case that changed procedure
In October 2018, at the eXTREMESLAND finals in Shanghai, an Indian Counter-Strike professional, Nikhil "forsaken" Kumar, was caught by an admin running a cheat disguised as a legitimate file on a tournament PC. His team was disqualified and he received a long ban. The case mattered because it showed that a cheat could be smuggled onto a stage machine, and because it was caught by human attention as much as by software. Organisers responded by tightening USB policies and reviewing how players access tournament systems.1
— From this essayOn a stage, the most effective anti-cheat sensor is still an attentive admin standing behind the booth.
Integrity is more than software
Some of the most damaging integrity cases in esports involved no cheat program at all. In 2015, members of the North American team iBUYPOWER were banned after an investigation into a thrown match from 2014, a case that shaped Valve's approach to match-fixing. In 2020, ESIC and tournament organisers investigated a spectator-camera bug in Counter-Strike that let coaches view parts of the map they should not see; dozens of coaches were eventually sanctioned. These cases required forensic work on demos, communication records and betting patterns, the domain of integrity investigators rather than anti-cheat engineers.2
The Esports Integrity Commission, founded in 2016 and modelled partly on integrity units in traditional sport, works with organisers such as ESL and with betting monitors to detect suspicious wagering. Its existence reflects a recognition that competitive integrity spans cheating, match-fixing, doping and abuse of game bugs, and that no single vendor can police all of it.
Online qualifiers: the hard middle
Many professional careers begin in online qualifiers, where players use their own machines. Organisers typically require a platform client such as FACEIT's, sometimes combined with webcam or screen-share proctoring for higher-stakes matches. This is where the privacy tension returns at full strength: a player seeking a place on stage is asked to install kernel software and, occasionally, to film their room. Good practice is to explain these requirements in the rulebook, limit retention of recordings and give an appeal route.
Research milestones
A simplified timeline of moments that shaped how the field thinks about fair play.
- 2000PunkBuster released by Even Balance, an early widely deployed third-party anti-cheat.
- 2002Valve Anti-Cheat introduced on Steam.
- 2004BattlEye founded, initially for Battlefield Vietnam.
- 2015Valve bans iBUYPOWER players for match-fixing.
- 2016Esports Integrity Commission established.
- 2018VACnet presented at GDC; Epic Games acquires Easy Anti-Cheat's developer, Kamu; forsaken caught at eXTREMESLAND.
- 2020Riot Vanguard launches with Valorant; Counter-Strike coaching bug investigation.
- 2021Activision announces Ricochet; EAC and BattlEye add Proton support.
- 2022Abuse of a game anti-cheat driver by ransomware publicly reported.
A checklist for organisers
Define what counts as cheating in plain language. Specify which software is mandatory, at which stage, and what it collects. Keep admin logs. Preserve demos. Separate the person who detects from the person who decides, and publish how appeals work. The final essay asks who these people are.