Game intel
Marathon
Marathon Recompiled is an unofficial PC port of the Xbox 360 version of Sonic the Hedgehog (2006) created through the process of static recompilation. The port…
Bungie just turned the volume up on anti-cheat rhetoric: anyone caught cheating in its March 5 extraction shooter Marathon will be permanently banned “with no second chances.” That’s the headline. The real story is the teeth behind it – Bungie is trying to make cheating impossible by moving authority for movement, shooting, and loot entirely to dedicated servers, layering in BattlEye kernel-level anti-cheat, and running a server-side Fog of War so clients can’t see what they’re not supposed to. Those systems are going live for a Server Slam beginning Feb. 26, and that’s where the promise meets the first real-world stress test.
Extraction shooters live and die on trust. If your run can be ruined by someone teleporting through walls or using loot-reveal hacks to steamroll the economy, the whole loop collapses. Bungie’s message is simple: enforcement will be unforgiving because the economic and competitive stakes in Marathon are high. That tone matters because, after messy cheating scandals in other extraction projects, players are allergic to companies that sound lenient.
Promising permabans looks great in a blog post. The uncomfortable fact is that detection is never perfect, and kernel-level anti-cheats like BattlEye are intrusive by design — they operate deep in a player’s OS to catch cheats, which has historically led to driver conflicts, crashes, and a chunk of angry threads when false positives hit big creators. Bungie acknowledges “no system is perfect” and offers an appeals path, but the more aggressively a game enforces bans, the higher the political cost when mistakes happen. The appeals process will be the real test of whether this policy protects legitimate players or just scares them off.

There are three technical pillars here: server-side authority, Fog of War, and BattlEye. Moving hit registration and inventory decisions into the server makes many common cheats — teleporting, infinite ammo, fake kills — much harder because the server rejects illegal state. The Fog of War runs on the server to limit what data the client receives, cutting the usefulness of wallhacks and ESP. BattlEye sits at kernel level to monitor and block external cheat tools. Together, these are standard best practices — but their value depends on execution. Server-side bullet tracking has to tolerate packet loss and latency; Fog of War mustn’t introduce janky gameplay; BattlEye needs to not break players’ systems.
How will you balance rapid, automated detections with human-reviewed appeals during launch week so creators and high-profile players don’t get perma-banned before Bungie can triage false positives? A blanket “permaban” is only as fair as the follow-up process.

Bungie is staking Marathon’s competitive credibility on authoritative servers, BattlEye, and a server-run Fog of War — and it’s promising permanent bans for cheaters. That approach is technically sound and honest, but it raises the risk of painful false positives and driver-level headaches on launch. The Server Slam starting Feb. 26 is the first concrete moment to see whether Bungie can enforce hard bans without breaking the player base.
Get access to exclusive strategies, hidden tips, and pro-level insights that we don't share publicly.
Ultimate Gaming Strategy Guide + Weekly Pro Tips