Some error codes have crept into the beta of Destiny 2: Termite, Moose, and Weasel are occurring frequently.
Last night, on July 18th, the closed beta of Destiny 2 launched on PS4. At exactly 7 PM, countless Guardians tried to connect to the servers. For some, this worked perfectly, while many others struggled with termites – as the Termite error code prevented them from logging in.
Bungie has been working hard over the last few hours to contain the error codes. New issues have arisen during this process.
Error Codes in the Destiny 2 Beta – Here’s What Bungie Says
At the beta launch, Bungie informed that players should expect queues when logging in. However, a queue was not the issue, as many players were kicked indiscriminately during the login attempt and overwhelmed with “termite” errors.
- Termite: This login error was reportedly fixed by Bungie about three hours after the beta launch. Whether it will return for the beta launch on Xbox One today remains to be seen.
- Moose: Just a few minutes after the announcement that the termites were dealt with, Moose errors reportedly occurred frequently according to Bungie. This is a general network error. It is recommended to restart the activity when a Moose error occurs.
- Client Crashes: There are multiple player reports of the beta client crashing. This crash can occur in-game and during login. About 8 hours ago, Bungie tweeted that investigations are still ongoing.
- Weasel: The latest status update from Bungie informs about Weasel error codes. This error occurs for some players when returning to orbit or inspecting their gear.
Keep in mind that such errors are not uncommon during major game launches – and in this case, during a beta launch. Some errors will likely resolve themselves once player traffic diminishes. But: Bungie is working on it. At least we now know that the error codes have Tier names in Destiny 2.
What issues have you already encountered in the beta?
You can read all the information about the “Destiny 2” beta here.
