The Bug Glimmer of Destiny 2 was not as crushed as Bungie hoped

You cannot limit a good bug. This is what Bungie learned while the bug glimmer disappearing last week appeared to force destiny 2 offline servers for about eight hours. Although the problem was not so widespread this week, enough players were assigned that Bungie had to kill the servers once again and restore the player’s account information in the state in which he was before reset weekly.

Destiny 2 Bugged
In a blog article on bungie.net, the development team has come into the details of the cause of the bug, and it is certainly an interesting reading for anyone interested in the complexity of the development of the game. The problem comes From a corrective that Bungie set up a few months ago to correct a bug with the sorting of the Quest Journal. Quests, which are treated like other inventory objects, are horoded when you receive them. The quest order was broken when the players finished part of the quest, because the control system would make a new horoditing at that time, replacing the original horoditing and breaking the order of quests.

Although this should have been a perfect solution for the problem to be resolved, it had a training effect on the rest of the cleaning process that occurs every time a player connects. When you connect to the game, a process runs to guarantee that everything that is in your inventory corresponds to what is live in the game, and that the maximum expected number of objects of objects. According to Bungie, “the net result was that the game calculated the amount of incorrect ceiling for stacked items (such as currencies and materials), which led to the loss of items above the ceiling.”

The reason for which the problem returned this week is due to a crash. Some WorldServers were restarted after update 2.7.1.1. The servers having broken down, the correction of the problem of disappearance of materials has never been applied. During the manual rebound of the servers, the players who took care of them were again affected.

In his blog articles, Bungie highlights several learning and new practices on this subject, to guarantee that something similar can no longer happen again. Other guarantees are in place to ensure that the servers cannot start with an unexpected version of an fix, and the WorldSserver planting problem has also been corrected and will be deployed at the start of season 10. They also plan to Raticing the restoration and recovery systems, so even if a character restoration is required in the future, it will not take so long.

Leave a Reply

Your email address will not be published. Required fields are marked *