Destiny 2’s days-long downtime this week was the result of… a configuration error in a developer tool


destiny 2 suffered a terrible outage earlier this week that stalled the game for more than 24 hours and even resulted in a rollback. Now Bungie is explaining what the heck happened in its weekly Dev Report.
“We determined the issue was caused when some currently uncompleted EDZ and Nessus Triumphs were moved from Forsaken to the archived Triumphs section,” says the studio. “To make this change, we used a tool that can move player status from one location to another in the player’s account. This tool is very powerful but requires careful and careful handling. Due to a configuration error, we accidentally re-ran an older state migration process that was used for the Beyond Light release. As a result, we re-copied old pre-Beyond Light data into the current configuration, essentially reversing certain aspects of player progression since then.”
This error caused the problem and has now been fixed, but not without the loss of nearly three hours of gameplay and a full day of downtime. The post doesn’t mention any compensation measures, although the studio says all purchases made in the lost time have been refunded.
The blog also covers Lightfall’s planned economic changes, Festival of Lost Armor themes, and the end of the Season of the Seraph.
advertising
https://massivelyop.com/2023/01/27/destiny-2s-day-long-outage-this-week-was-the-result-of-a-config-error-in-a-dev-tool/ Destiny 2’s days-long downtime this week was the result of… a configuration error in a developer tool