Two days ago, Bungie turned off the Destiny 2 servers while the studio investigated an issue that was apparently causing players to lose progress on in-game challenges. This outage lasted a bit longer than expected, with the free loot shooter remaining offline for nearly 20 hours. So what happened? Today, Bungie pulled back the curtain and explained exactly what was wrong and why it had to cancel the game, wiping out a few hours of people’s quest progress.
January 24 around 2 p.m.., Bungie tweeted that it was taking Destiny 2 offline as it investigated an “ongoing issue causing players to lose some Triumphs, Seals and Catalysts progression.” A few hours later, at 5:51 p.m., Bungie tweeted that he may have found a fix for the problem and was testing it, but was unable to specify when or if Destiny 2the servers would come back online. Almost four hours later, Bungie tweeted for the last time that evening, announcing that Destiny 2 would not be playable that night. Nearly 12 hours later, around 9:55 a.m., Bungie has announced that it has finally fixed the issue and the servers would come back online after a fix. The nearly 20 hours of downtime has some players worried about the health of the game and its future. After years of bugs and broken updates, it was really starting to look like the seven-year-old shooter was restrained with duct tape.
So what happened during those 20 hours and why was the game stopped for so long, seemingly without warning? Bungie 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 issue.
According to Bungie, shortly after releasing a previous update for the game (Hotfix 184.108.40.206), players began reporting that many Triumphs, Seals, and Catalysts were missing. Bungie realized this was caused after moving some “currently unfinished” challenges to another area of the game’s data. To do this, Bungie used a “very powerful” tool that allows the studio to tinker with the state game and a player’s account. Apparently, due to a configuration error, Bungie accidentally “rerun an older state migration process” used in a previous update. Due to this error, the tool copied the old data from this latest update into the current version of the game, which basically nullified some players’ recent achievements in the game.
G/O Media may receive a commission
The Lyma Supplement
10 ingredients. A super supplement.
Lyma makes the next generation of supplements, peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue was causing a loss of player state,” Bungie wrote, “we shut down the game and restored the player database while we investigate how to remove the dangerous change. version.”
After creating a new patch that removed the erroneous change, the issue was resolved, and after some testing Bugnie rolled out the update. However, as a result of this patch, all player accounts had to be canceled hours before the troublesome update went live. This means that any player progress made between 8:20 a.m. and 11 a.m. on January 24 has been lost. All purchases made during this period have also been refunded.
Even though it sucks that the game has been down for so long and the team has been forced to spend what feels like many late hours trying to fix their mistake, it’s refreshing to see a developer being so open and honest. about what happened and how it was fixed. At a time when games seem buggier than ever and players are tired of lags, crashes, and interrupted updates, it’s a good idea to pull back the curtain and show everyone how hard it is. to create, maintain and maintain video games as complex as Destiny 2.
Hopefully, next month’s news Destiny 2 expansion, fall of lightand the upcoming Season 20 rollout will go a little smoother than that recent 8 p.m. setback.
#Bungie #Explains #Destiny #20Hour #Blackout