Why 60% of Call of Duty Cheating Reports Target Console Players (But Data Says Otherwise)

Ricochet Anti-Cheat’s latest progress report contains a number that should make every Call of Duty player stop and think: over 60% of cheater reports in Warzone are filed against console players — yet nearly all detected cheaters come from PC. The gap between who players accuse and who actually cheats is not a rounding error. It’s a systemic misunderstanding of how the game works, and Ricochet now has the data to prove it.

That data, released in Ricochet’s most recent quarterly update ahead of Season 3, also comes with a practical fix — an expanded killcam system launching April 3 that tells players exactly why they died and exactly how they were spotted. The goal is to replace guesswork with information, and reduce a flood of reports that are clogging the pipeline with false positives.

The 60% Console Reporting Paradox

The number itself is striking enough. Console cheating exists — nobody from Ricochet is pretending otherwise — but the team’s own detection data describes it as “an extremely low population of detected cheaters when compared to PC.” That’s a direct quote from the progress report. Cross that against the 60%+ share of reports targeting console accounts, and the math stops making sense.

What it reveals is a perception problem running through the entire Call of Duty player base. PC players have genuine access to a wider range of cheat software; the barriers to running external programs are lower, the market for paid cheats is demonstrably active, and Ricochet’s own ban waves reflect that reality consistently. Console architecture adds meaningful friction — not a perfect wall, but enough that the actual caught-cheater population skews heavily PC.

So why are console players getting reported at this rate? The answer isn’t that the majority of accusers are acting in bad faith. Ricochet’s team explicitly gives players the benefit of the doubt, and the evidence supports that interpretation. People are genuinely seeing something in a killcam that reads as suspicious. They’re just wrong about what they’re seeing.

This matters beyond the individual false report. Every inaccurate submission diverts review resources, potentially delays action on real cheaters, and — on the other end — puts a legitimate player through an automated flagging process they did nothing to deserve. The 40-year-old on a PS5 who just played a perfect rotation gets reported for wallhacks. That’s the actual failure mode here.

Why Players Mistake Mechanics for Cheats

Warzone has, by design, multiple legitimate systems that give one player information about another player’s position through walls or at range. This is intentional. It’s part of the tactical layer. But in a killcam with no context labels, it looks identical to a wallhack from the victim’s perspective.

Ricochet’s report specifically names two examples: the Recon Scout perk and the Spy Cam field upgrade with live ping active. Both can result in an enemy knowing your location before they should, by any intuitive measure. If you’ve never used those tools yourself — or didn’t notice your opponent deploying them — the resulting death feels inexplicable. And “inexplicable kill through a wall” is exactly the behavior profile people associate with cheating.

The problem compounds because killcams in their current form don’t annotate the mechanics in play. You watch your own death. You see the enemy’s crosshair track toward you through cover. You don’t see the Spy Cam icon that was pinging you on their screen, or the perk indicator showing their scout had you marked. The information asymmetry that made the kill possible is invisible to the person being killed.

Three categories of legitimate mechanics that consistently trigger false reports:

• Recon Scout perk — marks enemy locations through walls after sustained tracking
• Spy Cam with live ping — provides real-time position updates on pinged targets, visible to the full squad
• Unsuppressed weapon fire — reveals the shooter’s minimap position to nearby enemies, enabling fast flanks that appear preemptive

Each of these is working as intended. None of them are cheats. But their output — an enemy who seems to know too much — is behaviorally indistinguishable from wallhack output if you can’t see the source.

Ricochet’s New Killcam Transparency Tool

The fix arriving with Season 3 on April 3 is direct: surface the information that was hidden. An “Affected by” module added to Warzone’s killcam will display every intel advantage the killing player held at the moment of the engagement. No more guessing. No more pattern-matching a death to a cheat profile.

Here’s what the expanded killcam will show, based on details from the Ricochet progress report:

A mid-season patch will extend this further, adding callouts for equipment, killstreaks, field upgrades, and perk interactions. That second wave matters — it’s specifically where Recon Scout and Spy Cam notifications will likely appear, since those are the mechanics most often misidentified as wallhacks.

The practical value here goes beyond reducing false reports. If you know that your unsuppressed AR gave away your position, that’s actionable information. You can attach a suppressor. You can change your firing angle. The killcam becomes a feedback loop, not just a death replay. That’s a meaningful quality-of-life shift regardless of the anti-cheat framing.

The Data: Where Cheaters Actually Are

Ricochet’s detection record, accumulated across multiple ban waves and quarterly reports, points consistently in one direction: PC. The team hasn’t released a specific percentage breakdown of PC versus console cheaters in this report, but the language is unambiguous — “extremely low population” on console, sustained detection activity on PC.

This tracks with what cheat developers themselves publish. The active PC cheat market for Warzone includes paid subscriptions running anywhere from $15 to $80 per month for aimbots, wallhacks, and radar overlays. Console equivalents require hardware-level exploits — external HDMI capture devices feeding into a secondary system, or chronus adapters for aim assist manipulation, neither of which operates at the same capability ceiling as PC software cheats. The technical barrier isn’t absolute, but it’s real.

“Console cheating is possible, but our data has consistently shown it represents an extremely low population of detected cheaters when compared to PC, which means that this large volume of cheater reports are inaccurate even if the KillCams may have made it seem like the player was cheating.” — Ricochet Anti-Cheat progress report, 2025

The implication for cross-play lobbies is worth flagging. Warzone’s default cross-play settings mix PC and console players in the same lobbies, which means console players are regularly killing PC opponents who may instinctively attribute the loss to cheating. The assumption that a console player who outplays you must be on PC “with cheats” is a known bias — and the 60% reporting figure is its measurable consequence.

What Season 3 Changes Mean for Accusations

Season 3 drops April 3. The killcam module is the anti-cheat headline, but it lands alongside a broader update that includes Verdansk’s return to Warzone — which means significantly higher player counts, higher lobby intensity, and almost certainly more heated postgame reports as players rediscover a map they’ve been away from.

That timing is either coincidental or pretty deliberate. Returning players who haven’t played Warzone in months won’t be current on which perks and field upgrades have been added or rebalanced. Recon Scout and similar intel tools will catch people off guard. Without the new killcam context, that would generate another wave of bogus reports pointed at whoever killed them — console player or not.

The “Affected by” module landing at the same time as Verdansk essentially functions as onboarding for returning players. See what killed you. Understand why. Ricochet is betting that a significant share of the current false-report volume comes from confusion rather than malice, and that transparency alone will move the number.

Shadow ban restrictions tightening around Ranked play — also part of this update — suggest Ricochet is trying to concentrate enforcement pressure where it matters most competitively, while simultaneously reducing noise in the general report queue. Both changes point toward the same goal: fewer false positives clogging detection, more accurate signal from the reports that remain.

How to Report Actual Cheating

Given all of this, the practical question is what actual suspicious behavior looks like — versus what the killcam will now explain away legitimately.

Before filing a report, check the killcam’s “Affected by” section when it launches in Season 3. If any of the listed intel advantages are flagged — live ping, UAV active, unsuppressed weapon — that explains the kill. Not a cheat. A mechanic.

Behavior that remains genuinely suspicious even after reviewing killcam context:

• Pre-aiming exact head height at a doorway before entering, with no line-of-sight or ping on your position
• Tracking through thick cover with no UAV, no Recon Scout, no Spy Cam callout in the new module
• Snap tracking at ranges and speeds inconsistent with any controller or mouse input (more relevant for PC opponents)
• Kill patterns where a single player eliminates an entire squad sequentially with zero repositioning time

To report in Warzone: open the scoreboard or the killfeed, select the player’s name, and choose “Report.” Specify the category accurately — aimbot, wallhack, and spam/griefing are different queues. Ricochet has stated that categorized reports are processed more effectively than generic ones. A timestamped, specific report from a player who checked the killcam first carries more signal than a rage-report filed three seconds after respawn.

The system works better when the reports it receives are accurate. That’s exactly what the new killcam is designed to make possible — and if the 60% console-reporting figure drops significantly after Season 3 launches, that’ll be the clearest evidence yet that players were genuinely confused, not just looking for someone to blame.