Destiny 2 has been offline for 16 hours now, in the wake of a large hotfix that was supposed to remove blue drops and nerf airborne effectiveness, but accidentally broke the entire game.
A fix is supposed to be deployed some time this morning, but that timeline is subject to change, and we’re already past the originally stated 3-4 AM PT window. I do not envy the Bungie staff effectively pulling all-nighters to fix whatever is going on here, which started with the discovery that some players had lost triumphs and titles, and ended with server instability so severe, you could kill an enemy three times and watch them come back to life due to lag.
Bungie has said they will be issuing an actual rollback to a pre-hotfix state, which means any loot farmed right before or right after the hotfix went live will be lost. That’s not great considering right after reset is when many in-game things reset and when many players will immediately start farming, myself included. So that’s lost raid drops, crafting patterns, exotic bows. It’s only the third full rollback in Destiny 2 history.
It’s becoming pretty clear that Destiny 2’s mounting technical problems are the chief issue with the game. This season alone, Bungie has had to turn the API off twice to fix error code and server issues, one of which marred the release of its new dungeon. It has players worried about the state of Lightfall and its raid race which launch in just over a month, understandably.
The problem is there are no easy answers here. While I may always be shouting suggestions at Bungie for nerfs or buffs or economy changes, the fanbase really cannot make any educated commentary on what’s going on behind the scenes here. The laundry list of go-to culprits blamed is usually:
Last Gen Consoles – The game is being held back by hanging onto PS4 and Xbox One, when it should be focused on PS5, Series X and PC.
Content Vaulting – Either too much/not enough. Bungie did say that content vaulting would help with Destiny’s technical challenges, but so far things have only gotten worse. Some are guessing things could be resolved when seasonal content is cleared out before Lightfall, but again, that’s all it is, a guess.
The Tiger Engine – This is Destiny 2’s long-running engine which has been upgraded and reformatted many times over the years, but players believe it’s just too old now. Some are calling for a familiar refrain that Destiny should move to Unreal Engine 5. That’s…not going to happen. It’s possible these problems are tied to the engine but we don’t know how or the extent of that.
Destiny 3 – Destiny 3 started trending online as everyone said it was time for Bungie to simply leave Destiny 2 behind and make a new game as these issues mount. And yet who knows if Destiny 3 would solve these problems if problems remain with say, underlying server architecture, and not just the meat of what’s actually in Destiny 2. Or that problems couldn’t carry over between games.
So yes, I think we can say that this is a very clear, very pressing problem, but this is one area where I don’t think we can make any prescriptions. Unless Bungie goes into great detail about what exactly is going on here, we’re just guessing, and it sure seems like even they don’t really know the full extent of the problems the game has, given that this keeps happening at an increased frequency.
This does not feel sustainable however, and may require some larger, painful changes to come. As for this week, check back here and I’ll update this when Destiny 2 comes back online.
Follow me on Twitter, YouTube, Facebook and Instagram. Subscribe to my free weekly content round-up newsletter, God Rolls.
Pick up my sci-fi novels the Herokiller series and The Earthborn Trilogy.