Destiny 2: Players are experiencing frustrating connection issues

earthpressnews

Destiny 2 players are currently struggling with frustrating connectivity and stability issues. After the displeasure in the community grew, Bungie has now reacted and given an unusually open insight into the causes and the planned solutions. MeinMMO will tell you when things will finally get better.

Destiny 2 currently has these problems: For months, the Guardians have been plagued by persistent server and stability problems in Destiny 2.

  • This includes disconnects with the message “Contacting Destiny 2 servers”.
  • Error codes, such as Weasel, Baboon or Mongoose, which could also throw you out of the game and even lead to a temporary, unauthorized ban because you had “aborted” a competitive game mode by being kicked out.
  • Matchmaking issues that caused Destiny 2 to become a single player game due to the inability to form fireteams.

    • Due to this large number of incidents, Bungie has recently had to schedule unexpected emergency maintenance to stabilize the game.

    While this temporarily resolved the issues, it didn’t really reduce Guardian frustration. On the contrary.

    For players, the increasing number of crashes and connection issues is a clear sign that Destiny 2 has reached the end of its life cycle after almost 7 years. Also because such problems occurred much less frequently in the past.

    But now Bungie has taken a stand on this topic more openly than ever before and has revealed concrete statements about the solutions in a roadmap.

    Destiny 2: Season of the Deep drops Guardians into the water

    More videos

    auto play

    “No process that happens overnight”

    Here’s what Bungie says about server stability and issues: In the current TWiD (“This Week in Destiny” blog) from June 29, Bungie has for the first time reacted in detail to the current Destiny 2 server problems and informed more openly than ever about the current status of the server technology.

    There was good news and bad news for the Keepers here.

    The good news: Bungie knows which system is causing the problems. It is the Destiny key service “Claims”.

  • Claims transfers all player data between the various Bungie servers, normally ensuring smooth communication between players, servers and other components so that every kill, bullet and Glimmer unit is sent to the right recipient.

    • So if it happens that the communication channels from “Claims” to other services are disrupted, this can lead to error codes like Weasel or Baboon. However, a simple restart of the service is often not enough to fix the problems.

    So, while Claims is just one of many services that are constantly being updated and maintained, the improvements being made to this service are a critical step in addressing both the immediate issues and any potential future ones.

    There are still many buttons to be pressed on the Destiny servers until the end of the year.

    The bad news: Getting stability back into Claims and Destiny 2 will not be an overnight process, according to Bungie.

    This is what the TWiD says:

    Fixing these issues is a top priority for our support team, but we must proceed with extreme caution. If we get it wrong, we could unintentionally decrease stability for players or introduce new problems. This is not a process that can happen overnight and we must ensure that [alles] reliably delivered to keep the Destiny 2 experience smooth and stable.

    writes Bungie in TWiD of June 29, 2023

    Why did Bungie work on these services in the first place? In preparation for the current DLC “Lightfall” and the future major releases of Destiny, Bungie has started to scale the server infrastructure. Mainly so that it can serve more simultaneous players in the future.

    So when will things start to run smoothly again? To address the issues, Bungie is planning a combination of server maintenance, network system tweaks, and bug fixes.

    However, the developers also noted that this will continue to test the patience of the Guardians, as the improvements take time.

    This is the current master plan for fixing the issues:

  • With the Midseason Update 7.1.0.5 for Season 21, the coming out in a few weeks, Bungie will first implement an improvement to its logging and alerting systems. This is intended to prevent the stability problems from getting worse in the future.
  • Then, at the start of Season 22 on August 22, 2023, Bungie will add what it called a “self-healing” ability to “Claims” to reduce the likelihood of Destiny 2 having to be temporarily taken offline if an issue occurs .
  • In early December, with the launch of Season 23, the improved logging from Season 21 will then be leveraged to introduce deeper and broader architectural improvements that enable service stability and rapid recovery, as well as a number of other unspecified improvements.

    • The development team is aware of the difficulties and emphasizes that they can understand the frustration of the players. Because this schedule means that the patience of the guardians will be tested at least until the end of the year, as there can always be outages.

    And even after that, Destiny 2 will remain a live service game that will always be more or less “in progress.”

    However, Bungie wants to work to minimize this risk through extensive testing and 24/7 monitoring to at least bring everything back online as quickly as possible in the event of instabilities.

    Given the other issues Destiny 2 is currently struggling with, this open communication is at least a step in the right direction, even if it only addresses part of the issues.

    How do you feel about the proposed solutions and how willing are you to support these changes? Please leave us a comment with your opinion on it.

    At least the Destiny story is going great right now and has now answered the biggest question from Lightfall and teased a big resurrection.

    Destiny 2 finally explains what failed Lightfall’s campaign in 3 minutes

    mmod-game