Bungie has made an official apology for the botched launch of Destiny 2: The Final Shape.
On Twitter, as part of a thread for updates on the status of the game, Bungie made their apology midway. Here’s what they said:
“Hey everyone, if connection issues have blocked you from playing or enjoying The Final Shape today, we want to apologize. We’re hard at work trying to resolve each of these issues as quickly as possible, and many of the connection issues from this morning have already been fixed.
20 Legendary Games Worth REVISITING in 2024
Gameranx
462K views • 3 days ago
Top 10 NEW Games of November 2024
Gameranx
734K views • 2 days ago
We built The Final Shape to be an exciting, cathartic, story-driven adventure for everyone to enjoy. We’re truly sorry if connection issues and instability is getting in the way of that experience, and we promise to keep working until these issues are resolved.”
They also directed players to their BungieHelp account on Twitter for updates on their progress fixing these issues. As of this writing, BungieHelp cites three error codes that have been appearing for players, all of which are related to internet connection issues.
We’re sharing each error code and what they mean below:
Currant – Errors of this nature are actively monitored by Bungie to keep us aware of trending issues impacting players. Often these types of issues transpire when interruptions between host and client connections are caused due to circumstances outside of our network.
Cabbage – Error code CABBAGE may occur when router settings block communications to or from Destiny services.
Weasel – The WEASEL error code is an all-encompassing error message that is usually an indicator that you are experiencing a general networking issue.
BungieHelp’s most recent tweet indicates that the studio deployed a rolling restart of their servers, which did kick out some people who were already playing the game. This action successfully fixed the issue for some players who received Currant errors, and they are still working on investigating the issues with players who received Cabbage and Weasel error codes.
As we had alluded to before, Bungie and Sony has a lot riding on Destiny 2: The Final Shape. Even if the detailed rumors about terrible working conditions behind the scenes at Bungie were not true, Bungie has still been dealing with a fanbase who has become tired of this live service title. Bungie has already said that they are making a Destiny 3, aside from their upcoming Marathon extraction shooter.
Here and now, they have to make fans happy with Destiny 2: The Final Shape. If the fans end up feeling that the last decade of Destiny wasn’t worth it given this final outing, it may lead to lasting damage to Bungie’s reputation.
In spite of the bad news, we do believe fans are willing to look the other way because they do want Bungie to give them the resolution they want. Hopefully, when everything is said and done, they will find that Bungie managed to pull it off.