Two days in the past, Bungie turned off the Future 2 servers whereas the studio regarded into an issue that had gamers apparently shedding progress on in-game challenges. This outage lasted a bit longer than everybody anticipated, with the free-to-play loot shooter remaining offline for almost 20 hours. So what occurred? Right now Bungie pulled again the curtain and defined precisely what went mistaken and why it needed to roll again the sport, erasing a couple of hours of oldsters’ quest progress within the course of.
On January 24 at round 2:00 p.m., Bungie tweeted that it was taking Future 2 offline whereas it investigated an “ongoing concern inflicting sure Triumphs, Seals, and Catalysts to lose progress for gamers.” A number of hours later, at 5:51 p.m., Bungie tweeted that it had presumably discovered a repair for the difficulty and was testing it, however was unable to specify when or if Future 2’s servers would come again on-line. Almost 4 hours later, Bungie tweeted for the final time that evening, asserting that Future 2 wouldn’t be playable that night. Almost 12 hours later, at round 9:55 a.m, Bungie introduced it had lastly solved the issue and servers can be coming again on-line following a hotfix. The almost 20 hours of downtime had some gamers anxious in regards to the recreation’s well being, and its future. After years of bugs and damaged updates, it was actually beginning to really feel just like the seven-year-old shooter was being held along with duct tape.
So what occurred throughout these 20 hours and why was the sport down for therefore lengthy, seemingly with little warning? Bungie has defined what broke, why, and the way it was mounted in its newest weblog submit. And surprisingly, the developer is extra clear than you may assume, going into technical particulars of the difficulty.
Based on Bungie, shortly after releasing a earlier replace for the sport (Hotfix 6.3.0.5) gamers started reporting that many Triumphs, Seals, and catalysts had vanished. Bungie realized that this was being brought on after it moved some “at present incompletable” challenges into a unique space of the sport’s information. To do that, Bungie used a “very highly effective” device that lets the studio tinker with a participant’s recreation state and account. Apparently, on account of a configuration error, Bungie by chance “re-ran an older state migration course of” utilized in a previous replace. Due to this error, the device copied outdated information from this previous replace into the present model of the sport, which principally undid some gamers’ current in-game accomplishments
G/O Media might get a fee
health
The Lyma Supplement
10 ingredients. One super-supplement.
Lyma makes the next generation of supplements—peer-reviewed and formulated to unlock your potential.
“Once we identified that the issue resulted in a loss of player state,” wrote Bungie, “we took the game down 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 mistaken change the issue was fixed, and following some testing, Bugnie deployed the update. However, as a result of this patch, all player accounts had to be rolled back a few hours before the troublesome update went live. This means any player progress made between 8:20 and 11 a.m. on January 24 was lost. Any purchases made during this time got refunded, too.
While it sucks that the game was down for so long and that the team was forced to spend what sounds like many late hours trying to fix their mistake, it’s refreshing to see a developer be so open and honest about what happened and how it was fixed. In a time when games feel buggier than ever and players are fed up with delays, outages, and broken updates, it’s smart to pull back the curtain and show everyone just how hard it is to make, maintain, and sustain video games as complex as Destiny 2.
Hopefully, subsequent month’s new Future 2 growth, Lightfall, and the upcoming Season 20 rollout will go somewhat smoother than this current 20-hour hiccup.
