When a cheat is detected, the ban often does not land for weeks. Anti-cheat teams collect detections, wait, then ban thousands at once. The delay protects the detector: if every ban landed the moment a cheat was spotted, cheat developers would know exactly which trick got caught.
The delay is the defense
Cheat development is a feedback loop. A developer ships a cheat, players use it, some get banned, and the developer studies the bans to learn what was detected. An instant ban is a precise signal: this account, this cheat, this moment, this detection. A delayed ban is noise. The developer knows the cheat was caught eventually, but not which feature, which match, or which behavior gave it away.
That is why detection and enforcement are separate. The detector flags the account the day it spots the cheat. The ban lands weeks later, mixed in with thousands of others, and the signal the cheat developer gets is a wave, not a diagnosis.
What a wave actually contains
A ban wave is rarely one cheat. It is usually a batch of accounts flagged by several detections over several weeks, banned together so no single detection can be isolated. Some waves target a specific cheat that grew popular. Others sweep up every account flagged since the last wave, across many different cheats and behaviors.
The numbers are large because the delay lets the list grow. A wave can hit tens of thousands of accounts in a single day, and the forums fill with cheaters comparing notes and finding nothing useful, because the ban gives no reason and no timing.
The innocent-looking gap
The gap between detection and ban is the part players notice most. A cheater gets reported, keeps playing for a month, and the community concludes the report did nothing. The report did its job the day it was filed. The ban is waiting for the wave, and the cheater's continued play is the price of keeping the detector hidden.
This is also why reporting still matters after a cheater is already flagged. Reports add weight to the behavioral score and can push a borderline account over the threshold, and replay review can confirm what the automated system only suspected.
What waves cannot fix
Waves are a delaying tactic, not a cure. Cheat developers adapt by shipping private builds, rotating features, and testing detection with throwaway accounts. A wave bans the accounts caught this cycle. The next cycle starts the day after, with a new cheat and a new detection to build.
The real measure of a ban wave is not how many accounts it removes. It is how long it takes the cheat developers to figure out what changed, and how many of their customers get banned in the meantime.
Keep reading
Related guides on this site: BattleEye vs Vanguard at the kernel level how DMA cheats hide in a PCIe slot how HWID bans fingerprint hardware More from Bot Protection For Games.
Frequently asked questions
How long does a ban wave take to arrive?
Usually weeks to a few months after detection. The delay is deliberate: anti-cheat teams collect flagged accounts and ban them together so cheat developers cannot tell which trick was caught or when it was spotted.
Why was a cheater I reported still playing a month later?
The report likely worked the day it was filed, but the ban waits for the next wave. The account stays playable until the batch ban lands, and that gap is the cost of hiding the detection method from cheat developers.
Do ban waves ever catch innocent players?
They can, which is why the detection thresholds are set conservatively and the systems combine several signals before flagging an account. A false positive is costlier than a missed cheater, so the bar for a wave ban is high.
Is a delayed ban worse than an instant one for ranked play?
For the players in that cheater's matches, yes. The cheater keeps ruining games until the wave lands. Anti-cheat teams accept that cost because instant bans hand cheat developers a precise signal about what was detected.