In 2023, the Destiny 2 servers were offline for hours due to a bug and when they were online again, there was a rollback, a reset on the game to an earlier period. A developer now admits that his team is responsible for this was.
What kind of confession is that? Destiny developer Alan Blaine reports to the English-language magazine PCGamer that Bungie recorded a severe decline in the Destiny players at the end of 2022-this was in the months after the expansion “The Witch Queen”.
During the same period, the developers found that the mood among the players was noticeably worse. Bungie then founded a team including Blaine, which should improve the binding of the players to the game by quickly recognizing and resolving problems.
According to Blaine, however, this quick action led them to bring a serious bug into play: “In our hurry to deliver quickly and vigorously, as our mission was, we accidentally delivered an evil character that were damaging to us to shut down the game for 24 hours and to carry out the second rollback from a character database in the history of Destiny.
Destiny 2: launch trailer for the new episode heresy
More videos
Autoplay
Bug robbed players of their valuable successes
What kind of mistake was that? On January 24, 2023, some players reported that after an update they lost some of their triumphs – including triumphs for completing raids. In addition, some players also lacked catalysts and seals.
The update should actually bring a small “Quality of Life” improvement by shifting inconvenient achieves into the archive area of the Triumph menu. Blaine describes this as a small, nice change, which you should have simply discarded in the planning phase in terms of the consequences.
This is the old dream of all MMO players: Bungie reacted to the bow and drove Destiny 2’s servers down for emergency maintenance. On January 25, 2023, Bungie carried out a rollback to get their hard -earned success again, which reset the progress of all players to January 24th at 5:20 p.m.
A rollback is considered a nightmare for MMO players, because thereby losing the progress that it reaches between the rollback and the stand on which the progress is added. Many developers therefore want to avoid rollback. If the progress still occurs, it is often a sign that something really serious went wrong and that it had to use the extreme.
“None of us took it seriously”
What triggered the error? Blaine explains that there were actually several reasons for the bug: “The mistake had many causes: an incorrectly configured tool, an outdated documentation, not enough time to understand the risks of the solution.”
To make matters worse, the error even occurred in a test, but bungie nevertheless brought the update – and the bug – into play: “In a test run, the symptoms of the error were determined, but none of us took the bug seriously or understood the cause, admits Blaine.”
Not every bug causes 2 violent problems in Destiny and corrupts your progress. Some game errors even really enjoy the players of the Loot Shotoer. Such a bug can now stay in the game: popular bug becomes a feature in Destiny 2 so that keepers can have fun