We often hear that there is a problem with the game, wait for it to be fixed, read that it is fixed and then move on with our lives, none of us are as smart as what has just happened. So, it's nice to see Bungie going back and filling everyone in with the bug fix.
What Conclusion 2 was supposed to be posted offline this week ( the second time this has happened in a month)
From Bungie's report for this matter:
Over the past few months, players have reported that the kutaka script editing is not working properly, and we want to fix that. The team investigated that the refinancing process reset the time path to the claims set, which was contrary to the timetable. We decided to fix this by disabling timestamp rework for quests. Those repairs were thought of in theory but, with subtle side effects, eventually paralyze too many defects in the cleaning process. The result was that the match was calculated by the incorrect cap value of the included items (such as money and materials), which caused the items beyond the collar to be lost. We knew this code was critical and, in our normal process, we were two domain experts providing code updates for that change – but sadly, we didn't see a bug.
A few days later, our internal testing teams are tackling the problem. However, we incorrectly concluded that it was caused by a failure to use the tools with the debugging function we used to test, not the actual interruption during the game. Having received all our due diligence, the issue went in 2.7.1.
As to why the issue reappeared this week, Bungie says it's because the server is re-canceling the progress they had made earlier:
Let's go back again today, February 11, when we released the 2.7.1.1 update that is compatible with Crimson Days launch. After launch, some WorldServers were disabled earlier because of the high volume of servers starting at the same time. Once again we restarted those servers manually and thought everything was going well. We were wrong.
We do not know, this accident resulted in those WorldServers not using the character data correction of the previous character. This meant that a small percentage of WorldServers was running old code and a bug that corrupted character data.
They also have details on how to try and avoid mistakes like this happening again, such as adding "some security measures to our processes" to quickly install "our servers to make sure they won't start in unexpected form".
It's a real read, for both technical and PR reasons, and anyone who has played Deliny — or just wondering what's going on in this process other than "bug comes magically and then magically corrected" you can check it out here.