'The Only Way to Keep Bungie Alive Is to Support Marathon,' Ex-Destiny Community Manager Says

The final update for Destiny 2 has shipped. And the community is bracing for a future without new seasons. In the midst of the farewell, Bungie's former community manager made a striking claim: "The only way to keep Bungie alive is to support Marathon. " The statement ignited debate because it suggests the studio's survival now hinges on a yet-unreleased extraction shooter, not the franchise that carried it for a decade. From a software engineering perspective, this comparison between a mature live-service game and an unproven title reveals deeper, often ignored technical and operational realities.

As a developer who has spent years building and maintaining live-service systems, I've seen firsthand how hard it's to pivot a studio's entire technical stack. Bungie's situation isn't just about player counts or marketing; it's about the accumulation of technical debt, the cost of engine migrations and the difficulty of launching a new product while keeping an old one on life support. This article examines those engineering realities behind the headlines.

The Context: Destiny 2's Final Update and a Studio at a Crossroads

Bungie announced that Destiny 2: The Final Shape would conclude the game's main story arc, marking the end of major content releases. This has left millions of players wondering what comes next-both for the franchise and for the studio. The former community manager's plea to support Marathon (a reboot of the classic 1990s IP) is a desperate call to avoid the fate that has befallen other studios: layoffs - studio closures. Or acquisition-driven dissolution.

From a software lifecycle standpoint, maintaining a live-service game like Destiny 2 is a massive engineering effort. The game runs on Bungie's proprietary Tiger Engine, a heavily modified version of the engine used for Halo: Reach. Over the years, the engine has been patched with countless hotfixes, new rendering pipelines, and backend services to support cross-play, clan systems. And seasonal content. This accumulation of technical debt makes it increasingly expensive to develop new features while keeping the legacy code from collapsing.

The decision to sunset major Destiny 2 updates isn't purely creative; it's a resource allocation call. Every engineer assigned to fix a bug in a nine-year-old engine is an engineer not building Marathon's foundation. Bungie's leadership has clearly chosen to concentrate its best talent on the new project. Supporting Marathon isn't just a fan sentiment-it's a practical survival strategy for a studio that can't afford to maintain two large-scale online games simultaneously.

Why Comparing Player Counts Across Genres Is a Software Engineering Fallacy

The former community manager explicitly warned against comparing Destiny 2's concurrent player numbers with Marathon's. Many analysts on social media have done exactly that, citing declining Destiny 2 player counts as proof that Bungie is doomed. This comparison fails to account for the fundamentally different software architectures of an extraction shooter versus a looter shooter-MMO hybrid.

Extraction shooters like Escape from Tarkov or Hunt: Showdown share a common technical pattern: relatively small match sizes (typically 4-12 players per instance), server-authoritative physics. And a high emphasis on low-latency tick rates. In contrast, Destiny 2 uses a hybrid peer-to-peer / cloud-based system with lobbies of up to 12 players for PvP but sometimes 50+ in its social spaces (The Tower) and 9-player raids. The server scaling requirements, netcode, and state synchronization are drastically different. A new game starting with a small but dedicated player base can be perfectly healthy from a server cost perspective. While a legacy game with many concurrent players may still bleed money due to high cloud infrastructure bills.

From a product management angle, comparing metrics across genres is like comparing the CPU utilization of a Kubernetes cluster to that of a single bare-metal server. The correct comparison is against games of the same genre and technical profile. Marathon will need to hit similar retention metrics as Tarkov or Warzone, not Destiny 2. The former community manager's message is an appeal to judge Marathon on its own engineering and design merits, not on its predecessor's legacy numbers.

The marathon Gamble: Technical Lessons from Failed Extraction Shooters

Bungie isn't entering uncharted waters-the extraction shooter genre has seen a graveyard of failures. Titles like Hunt: Showdown (which eventually found a niche), Marauders, The Cycle: Frontier have demonstrated that the genre is brutally hard to balance. From a software engineering standpoint, the challenges include persistent inventory systems, cheat detection across multiple player states (in-raid vs. stash), and seamless transitions between PvE and PvP encounters.

One of the biggest technical hurdles for any extraction shooter is the server-side state machine that must handle complex extraction rules: a player's death before extraction, a disconnect during a raid. Or an inventory desync. The Marathon team has likely studied the developer blogs from Hunt: Showdown. Which documented how they rebuilt their netcode to handle mid-raid disconnects without losing loot. Bungie's experience with Destiny 2's notoriously buggy inventory system (e, and g, the "Weasel" errors that plagued early seasons) may actually be an advantage, as they've already learned painful lessons about state replication and database consistency.

Furthermore, Marathon will need a robust anti-cheat system from day one. Combatting cheaters in an extraction game is more critical than in Destiny 2's PvE-heavy environment because a single aim-bot in a raid can ruin the entire session for all other players. Bungie has already invested in BattleEye and internal detection tools. But they must redesign them for the new threat model. The success of the game's engineering infrastructure, not its story, will determine whether Marathon survives its first year.

Bungie's Long-Running Technical Debt: The Tiger Engine and Live Service Scalability

Bungie's Tiger Engine is a source of both pride and dread. It was originally written in the late 2000s for Halo: Reach, and over the years it has been modified to support Destiny's public events, Destiny 2's patrol zones. And finally the cross-play infrastructure required by Sony's acquisition. Each modification added layers of abstraction that now make the engine difficult to maintain. In a 2023 interview, Bungie engineers acknowledged that some core systems-like the activity scheduling service-rely on legacy code that only two senior engineers fully understand.

For Marathon, Bungie has stated they won't use the Tiger Engine. Instead, they're building on top of a modern engine (likely Unreal Engine 5, though unconfirmed) that supports features like Nanite virtualized geometry and Lumen global illumination. This means the studio must rebuild its entire tech stack from scratch: networking, matchmaking, physics, rendering. And asset pipelines that's a monumental undertaking for a studio that has spent 15 years optimizing for a single engine. Even with Sony's financial backing, the transition carries enormous risk. The former community manager's plea to support Marathon reflects the reality that a studio can't fund two engine teams indefinitely.

From a DevOps perspective, the build and deployment pipelines for Destiny 2 are rigid and bureaucratic-updates take weeks of certification across Xbox, PlayStation. And PC. Bungie would be wise to invest in a new CI/CD Workflow for Marathon that allows weekly hotfixes without the approval backlogs that have frustrated Destiny 2 players. If they fail to decouple deployment from their legacy processes, Marathon may suffer the same slow patch cadence that drove players away from the previous franchise.

From Halo to Destiny to Marathon: The Peril of Repeated Pivot Strategies

Bungie has a history of dramatic pivots. They left Halo to create Destiny, a new IP with a then-unproven MMO-like model. The pivot almost killed the studio during Destiny 1's launch, when the story was infamously rewritten and content was cut. Now they're pivoting from Destiny 2 to Marathon, again abandoning a successful franchise for a risky new genre. Each pivot forces the engineering team to discard years of domain knowledge and tooling.

One risk is that the institutional memory of how to build a looter shooter will be lost as senior engineers transfer to Marathon or leave the studio entirely. The Destiny 2 codebase, despite its technical debt, contains countless hard-won lessons about matchmaking fairness, reward scheduling. And encounter design. If Marathon requires a fundamentally different game loop, that knowledge may not transfer. Worse, the studio could repeat mistakes: for instance, Destiny 2's early years suffered from a lack of meaningful progression outside of raids, a problem that took years to fix. Extraction shooters have their own progression pain points-stash limits - gear fear,, and and RNG-based loadout acquisitionBungie must resist the temptation to copy-paste design patterns that worked in a different genre.

From a business standpoint, pivoting to a new engine and genre simultaneously is a high-risk, high-reward move. The former community manager's statement about "keeping Bungie alive" implies that the studio's cash reserves are limited. If Marathon fails to generate significant revenue within the first six months, Bungie may not have the financial runway to course-correct. This is why they're positioning Marathon as a premium-priced game with potential microtransactions, rather than a free-to-play title that requires massive user acquisition budgets.

The Community Manager's Plea: A Data-Driven Look at Player Retention Metrics

The former community manager's argument centers on the premise that Destiny 2's player retention is artificially inflated by the massive content drops over the past decade. While Marathon will need to prove its retention capabilities with a much smaller content budget. Data from industry reports (such as Game Developer's live-service retention benchmarks) indicate that extraction shooters typically have a D7 (day 7) retention rate of 15-25%. While MMO-lite games like Destiny 2 hover around 30-40% after seasonal updates. However, the cost to acquire and retain a player in a niche extraction shooter can be higher due to the need for competitive matchmaking and cheat-free environments.

From an engineering perspective, retention is heavily influenced by server performance and bug frequency. Destiny 2 has suffered from notorious downtime during expansion launches (the "Weasel" errors, "Currant" errors, etc. ), which directly correlates with player drop-off. For Marathon to succeed, Bungie must guarantee that the game's servers remain stable under launch load-a non-trivial challenge when building a new backend from scratch. Stress testing using synthetic players (locust io, GCP's load-testing tools) should be a priority months before release.

Additionally, the former manager's point about not comparing player counts is mathematically sound: Destiny 2 has a cumulative base built over 10 years. While Marathon will start at zero. The correct metric is the rate of player adoption relative to the launch budget. If Marathon attracts 500,000 players in its first month with a $30 price tag, that's $15 million in revenue-a healthy start for a AA title, but not enough to sustain a studio of Bungie's size (estimated ~1,000 employees). Sustainable revenue requires a retention loop that keeps players coming back repeatedly, which is a design challenge as much as an engineering one.

What Bungie Needs Beyond Fan Support: Better Engineering Practices