Call of Duty admits RICOCHET false-banned FormaL in the Modern Warfare 4 beta

The short version

RICOCHET permanently banned a Call of Duty world champion for playing well, and the devs have admitted it. Matthew “FormaL” Piper was mid-killstream in the Modern Warfare 4 beta, using the Oris 8.6 Marksman Rifle, when he was kicked from the lobby and served an “Account permanently banned” message live on stream (Dexerto).

The official Call of Duty CM account reversed it and explained why:

“We wanted to follow up on what happened after we quickly reverted his ban and spent some time investigating this situation. RICOCHET Anti-Cheat systems flagged this account in Beta due to a unique overlap between separate detections.”

And, crucially: “The underlying issue has since been fixed. Beta is a test for our teams too – we’re actively working on thresholds and reviewing results.”

That second sentence is the story. RICOCHET’s public line has always been about what it catches. This is the anti-cheat team saying, on the record, that the system produced a permanent ban it should not have.

What actually happened

The clip that spread it was posted by ModernWarzone on September 2 (X). FormaL drops several enemies in quick succession with the Oris, the killfeed rolls, and the lobby drops him.

Neither the clip nor the dev reply explains what tripped it. The joke doing the rounds — that the Oris is so strong it flags you as a cheater — is a joke; the devs pointed at overlapping detection signals, not at the gun. The specific detections have not been disclosed, and the devs did not say whether other players in that lobby had reported him.

The timing matters too. The open beta ran August 28 to September 1, and RICOCHET was live in it from day one — the beta was as much a stress test of the anti-cheat as of the maps and the time-to-kill.

Why this one is different

Every competitive community has a running argument about false bans. It is normally unwinnable: the accused say they were clean, the anti-cheat team says nothing, and the ledger stays closed.

This case broke that pattern for two reasons:

• It happened on camera, to someone with receipts. A CoD world champion with a live VOD is about the hardest possible case to wave away.
• The devs answered in public, within a day. Reversal, cause, and a fix — not a support ticket.

Several outlets have framed this as the first time RICOCHET has publicly conceded an erroneous ban (Gameranx). We’d put it slightly more carefully — it’s the clearest public admission we’ve seen, but Activision has never published a false-positive rate, so “first ever” isn’t something anyone outside the studio can verify.

What it means for launch

Be realistic about the scale here: one account, reversed, on a beta build. This is not evidence of a ban wave, and nothing in the dev statement suggests one.

The useful read is about thresholds. An anti-cheat that combines multiple detection signals has to decide how much combined evidence equals a permanent ban, and the devs said outright they are still tuning that — during a beta, on purpose, before the retail build ships. A threshold tight enough to catch cheats will occasionally catch outliers, and elite players are outliers by definition.

Modern Warfare 4 launches on October 23, 2026. If you get flagged in the retail game, the visible path is still the standard appeal — this incident was resolved because it happened loudly and publicly, which is not a process anyone can rely on.

It also lands in a busy month for Activision’s anti-cheat side of the house: the publisher recently tracked a Call of Duty cheat seller down to his front door and filmed the visit. The enforcement push is real; so, apparently, is the collateral.

Sources we check

The dev quotes here come from the Call of Duty CM account’s public reply, reproduced verbatim and identically by Dexerto (September 3), Gameranx (September 3) and Techtroduce (September 4), with the original clip from ModernWarzone (September 2). Activision has not published a blog post or patch note on the incident, so the statement is on the record but not in an official long-form source — we’ve flagged where that limits what can be confirmed. Beta dates and the launch date are from our own beta player-numbers breakdown. We have not seen any confirmed report of other accounts affected by the same detection overlap; if one lands, we’ll update this page.