Bungie Hid Destiny 2 Sunsetting as Marathon Got Resources
Baca dalam 60 detik
- Internal sources confirm that the majority of Destiny 2's development team was unaware of the sunsetting timeline until the public announcement.
- This opacity allowed Bungie to maintain morale and productivity while funneling talent to Marathon's development pipeline.
- The move mirrors industry trends where studios quietly deprioritize legacy titles to fuel new IP launches.

Bungie's decision to sunset Destiny 2 after a decade of updates comes amid a quiet but aggressive resource shift toward Marathon, a new extraction shooter. Internal sources confirm that the majority of Destiny 2's development team was unaware of the sunsetting timeline until the public announcement. This opacity allowed Bungie to maintain morale and productivity while funneling talent to Marathon's development pipeline.
The move mirrors industry trends where studios quietly deprioritize legacy titles to fuel new IP launches. By keeping developers in the dark, Bungie avoided the talent drain and negative press that often accompany early sunsetting disclosures. Marathon now benefits from a concentrated team, potentially accelerating its release window and competitive edge against rivals like Escape from Tarkov.
Destiny 2's final update in June 2026 will serve as a capstone, but the franchise's future remains uncertain. Bungie's strategic bet on Marathon positions it to capture a growing extraction shooter market, projected to reach $5 billion by 2027. However, alienating Destiny 2's loyal player base could backfire if Marathon fails to deliver.
Power Move: Bungie's stealth resource reallocation is a high-risk play: Marathon must succeed to justify Destiny 2's premature sunsetting. If Marathon flops, Bungie loses its cash cow and its futureโa classic all-in bet on new IP. Expect Marathon's launch to be aggressive, with Bungie leveraging its entire studio to ensure it hits the ground running.
This article was edited with AI assistance for readability. Read original here.



