There is once again excitement and unrest in the Destiny 2 community after another player lost a character due to the mysterious launch bug. However, unlike the first time, there is now hard video evidence on the table. MeinMMO tells you whether you should be worried now as well.
What error has thrown the community into turmoil? A few weeks ago, players in Destiny 2 were already worried about their characters, in which they have invested several thousand hours.
Back then, the Guardian CyanSolar was affected, who then desperately reported in the Bungie forum. He had spent over 2000 hours in Destiny 2 before deletion. After the error during the startup process of Destiny 2, his Titan with all the equipped weapons he had at the time of deletion was irretrievably gone.
Bungie made a one-time exception: Normally, character deletion in Destiny 2 is irreversible. Bungie’s official guidelines state that erroneously deleted or manually deleted characters or items due to unauthorized account access cannot be restored.
However, Bungie made an exceptional exception for CyanSolar in January 2023 and initiated the official and, according to its own statement, complicated rescue of his character after an examination.
In this context, it was emphasized that the preservation of characters and progress is the highest priority. At the same time, Bungie also clarified via Twitter that “no characters or progress have mistakenly been lost through our systems,” which initially calmed the Destiny community.
But now, video evidence provided by Guardian Octo shows that the launch bug, which became known a few weeks ago, apparently does exist and can lead to unforeseen deletions of your characters in Destiny 2.
Player Provides Video Evidence for Character Loss
What is seen in the evidence video? The video shows Octo trying to start Destiny 2 and receiving several error messages stating “Destiny 2 Servers are being contacted”.
After that, the game takes him, as usual, to the character selection menu, and he selects his Warlock to play with.
It is only the fraction of a second, but the display with “Delete Character” between all the reconnects and black screens is indeed visible at second 0:55. Shortly thereafter, the Warlock has already disappeared from the character list, leaving only an empty slot.
On Twitter, Octo published the relevant evidence video and addressed Bungie:
I lost my Warlock on Destiny 2 due to error codes for unknown reasons, even in the API when I check DIM. I would like to know what happened and if anything could be done to restore my character.
the player informs Bungie via Twitter and forum post
Here you can get an impression of the video and the deletion process of the character titled “Bug Deleted My Warlock”:
Must all Guardians tremble now? The video evidence from the player Octo went viral in the Destiny 2 community incredibly quickly. Especially since it initially shows that the error previously suspected apparently does exist and could affect any player.
However, it is not entirely clear what exactly happened. Normally, the prompt requires that you hold down a button to delete a character for a few seconds.
But some players immediately accused Bungie, saying that the developer had merely obscured the truth in January to avoid having to take responsibility for their mistakes.
- Dr. Ditters comments in the Bungie forum: “Unbelievable. Some people spent thousands of hours playing this game, and then they just lose it like that? All this time they blamed the players for the character deletions.”
- “I would curse for days while I leveled up the character again,” the Guardian ChopSue empathizes with the affected player.
- The well-known streamer Luckyy10P says instead: “If this is true, this is the holy grail of character deletion errors!”
Others, like dc213baseball, think that it is not a game bug, but the Guardian’s own fault.
First, you shouldn’t just press buttons without waiting for the screen messages to fully display. Second, it looks like the Weasel error code along with the reconnect in the game was caused by someone else trying to log into the account at the same time, which “kicked” the Guardian out. Accordingly, he should check his linked accounts and the associated 2FA logins.
The player cread92 also doubts that the character deletion was unintentional due to a game error or bug in Destiny 2. He says:
The only problem I have with this [evidence video] is that you don’t see him clicking “No” on the security prompt. You only see it disappear. As far as we know, he clicked “Yes,” and then it was his own fault that the game thought he was trying to delete his character. But he had a chance.
writes cread92 via Twitter
Destiny Bulletin, on the other hand, directly suggests Bungie a simple and very practical solution. On Twitter it says: “Bungie really needs to implement a function where you are asked to type ‘DELETE’ when deleting a character instead of just pressing the button. It’s that simple.”
Bungie’s reaction is still pending: Under Octo’s video, the community has now tagged the Destiny 2 team and hopes for a response.
This incident has already shown one thing: transparency and open communication between developers and players is essential. Bungie has claimed and proven in the past that they will do everything to improve the player experience. This also includes rescuing characters when they have really been lost due to an error.
However, whether this is the case here must now be examined by the developer themselves. Therefore, it remains to be seen how Bungie will respond to these accusations. MeinMMO will keep you updated and will update this article accordingly.
What do you think about the alleged evidence video? Do you believe that it is proof that character deletion can happen just like that and can affect anyone? Or do you say that this is just a one-time occurrence, so you are not worried? Please leave us your opinion in the comments.
Other Guardians are less worried about launch bugs than about the ultimate achievement in solo content, as this player here proves:
Your opinion is important to us!
Do you like the article? Then let us know!
