Bungie Explains Destiny 2’s Recent 20-Hour Outage

Spread the love

Screenshot: bungie

Two days ago, Bungie turned off the destiny 2 servers while the studio was investigating an issue that was apparently causing players to lose progress on in-game challenges. This outage lasted a bit longer than everyone expected, with the free loot shooter staying offline for almost 20 hours. So what happened? Today, Bungie pulled back the curtain and explained exactly what went wrong and why they had to revert the game, wiping out a few hours of people’s quest progress in the process.

On January 24 around 2:00 p.m.., Bungie tweeted that it was taking Destiny 2 offline while investigating an “ongoing issue causing certain Triumphs, Sigils, and Catalysts to lose progress for players.” A few hours later, at 5:51 p.m., bungie tweeted that he had possibly found a solution to the problem and was testing it, but could not specify when or if destiny 2The servers would come back online. almost four hours later bungie tweeted for the last time that night, announcing that destiny 2 it would not be playable that night. Almost 12 hours later, around 9:55 am, Bungie announced that it had finally resolved the issue. and the servers would be back online after a review. The nearly 20 hours of downtime had some players concerned about the health of the game and its future. After years of bugs and broken updates, it was really starting to feel like the seven-year-old shooter was being held with duct tape.

So what happened during those 20 hours, and why was the game down for so long, seemingly without warning? Bungie has explained what broke, why, and how it was fixed in his latest blog post. And surprisingly, the developer is more transparent than you might think, going into the technical details of the problem.

According to Bungie, shortly after releasing a previous update for the game (Hotfix, players began reporting that many Triumphs, Sigils, and Catalysts were missing. Bungie realized this was because he moved some “currently incompletable” challenges to a different area of ​​the game data. To do this, Bungie used a “very powerful” tool that allows the studio to play with a player’s game account and state. Apparently, due to a configuration error, Bungie “accidentally re-ran a previous state migration process” used in a previous update. Due to this bug, the tool copied old data from this previous update into the current version of the game, which basically undid some players’ recent achievements in the game.

“Once we identified that the issue resulted in the loss of player state,” Bungie wrote, “we removed the game and rolled back the player database while we investigate how to remove the dangerous build change.”

After creating a new patch that removed the erroneous change, the issue was fixed, and after some testing, Bunnie deployed the update. However, as a result of this patch, all player accounts had to be reverted a few hours before the problematic update was released. This means that any player’s progress made between 8:20 and 11:00 am on January 24th will be lost. Any purchases made during this time were also refunded.

While it sucks that the game was down for so long and the team was forced to spend what seems like many hours trying to fix their bug, it’s refreshing to see a developer being so open and honest about what happened and how it was dealt with. solved. . In an age where games feel buggier than ever and gamers are fed up with lag, crashes, and broken updates, it’s smart to pull back the curtain and show everyone just how hard it is to create, maintain, and sustain video games as complex as fate 2

With a little luck, next month new destiny 2 expansion, light falland the launch of the upcoming season 20 will be a bit smoother than this recent 20-hour hiccup.

#Bungie #Explains #Destiny #20Hour #Outage

Leave a Comment

Your email address will not be published. Required fields are marked *