Bungie explains Destiny 2’s recent 20-hour outage
Bungie shut it down two days ago destiny 2 Server while the studio was investigating an issue where players appeared to be losing progress on in-game challenges. This outage lasted a little longer than expected as the free-to-play loot shooter remained offline for almost 20 hours. So what happened? Today Bungie pulled back the curtain and explained exactly what went wrong and why the game had to be reset, erasing a few hours of people’s quest progress.
On January 24 around 2:00 p.m. Bungie tweeted that it is taking Destiny 2 offline while it investigates an “ongoing issue causing certain Triumphs, Seals, and Catalysts to lose progress for players.” A few hours later, at 5:51 p.m., Bungie tweeted that it may have found and tested a solution to the problem, but couldn’t specify when or if destiny 2The servers of would go online again. Almost four hours later Bungie tweeted for the last time that night, announcing it destiny 2 would not be playable that evening. Almost 12 hours later, around 9:55 a.m., Bungie announced that it had finally resolved the issue and servers would come back online after a hotfix. The nearly 20 hours of downtime left some players worried about the health of the game and its future. After years of bugs and buggy updates, it really felt like it The seven-year-old shooter was held together with duct tape.
So what happened in those 20 hours and why was the game down for so long, seemingly without warning? Bungie explained what broke, why and how it was fixed his latest blog post. And surprisingly, the developer is more transparent than you might think about the technical details of the issue.
According to Bungie, shortly after the release of a previous update to the game (Hotfix 220.127.116.11), players began reporting that many Triumphs, Seals, and Catalysts were gone. Bungie realized this was caused after it moved some “currently unsolvable” challenges to a different area of the game data. To do this, Bungie used a “very powerful” tool that allows the studio to tinker with a player’s game status and account. Apparently, due to a configuration error, Bungie accidentally “re-ran an older state migration process” that was used in a previous update. Due to this error, the tool copied old data from that last update to 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 addition.
Lyma manufactures the next generation of nutritional supplements – peer reviewed and formulated to unlock your potential.
“As soon as we determined that the issue resulted in a loss of player status,” Bungie wrote, “we shut down the game and rolled back the player database while we investigated how to remove the dangerous change from the build.”
After creating a new patch that removed the offending change, the problem was fixed and after some testing, Bugnie deployed the update. However, as a result of this patch, all player accounts had to be reset a few hours before the pesky update was released. This means that any player progress made between 8:20am and 11:00am on January 24th will be lost. All purchases made during this period were also refunded.
While it sucks that the game was down for so long and the team was forced to spend many hours fixing its bug, it’s refreshing to see a developer speak so openly and honestly about what happened and how it was fixed. At a time when games feel more buggy than ever, and players are fed up with lags, dropouts, and buggy updates, it’s wise to pull back the curtain and show everyone how difficult it is to make video games this complex, to maintain and maintain destiny 2
Hopefully, new next month destiny 2 Extension, incidence of lightand the upcoming Season 20 rollout will be a little smoother than this 20-hour hiccup.
https://kotaku.com/bungie-destiny-2-outage-servers-offline-why-jan-24-1850038131 Bungie explains Destiny 2’s recent 20-hour outage