Destiny 2 beta error codes: what to do about Moose and Weasel, crashes and identified points

The Destiny 2 beta shouldn’t be with out its issues. Here’s the newest on error codes and identified points.

If you’re having an issue with the Destiny 2 beta, it could possibly be an error, or it might simply be the truth that you’re serving to to check an unfinished product. In both case, it’s not sudden and it’s best to anticipate some interruptions to gameplay.

That doesn’t imply you simply must dwell with it, although. Prior to the Destiny 2 beta start, Bungie offered a listing of identified points it anticipated gamers to run into. You can seek the advice of that beneath, or scroll down additional for present error codes and options.

Destiny 2 beta identified points

The greatest and most evident downside Bungie has highlighted prematurely is networking points, one thing you’re sure to run into in a stress take a look at like this. Other points embrace location names not showing in Crucible matches, bugs associated to becoming a member of an in-progress sport of the Inverted Spire strike, lacking localisation for some content material, and extra.

Here’s the total record as of the time of writing:

• Players could expertise a wide range of networking error codes when trying to play the beta
• Bungie will likely be testing server stability all through the beta, which can trigger error codes to look periodically
• Location names typically don’t seem throughout Crucible gameplay
• Players typically are kicked to orbit after witnessing a black display screen when coming into a Countdown match
• Players could typically be positioned at the start of the Inverted Spire strike when becoming a member of in progress
• Sandbox balancing continues to be going down: some weapons or talents could have greater or decrease harm than meant
• Not all content material has been localised in all languages
• If you encounter any community associated points in the course of the Destiny 2 beta, please comply with our community troubleshooting information to make sure correct community settings for Destiny gameplay

Bungie advised that gamers report any points not listed above in the help forum if and once they run into any.

Destiny 2 beta error codes

Now that the Destiny 2 beta has opened for PS4 early access, we’ve seen a crop of error codes and crashes. Here’s what to do should you encounter every one:

• Client crashes

  If your Destiny 2 beta shopper crashes whereas enjoying or when logging in, uh – sorry? Open it once more. Bungie is investigating this problem.

• Moose error code

  This error crops up whereas enjoying numerous actions. The newest replace from Bungie suggests restarting the exercise.

• Weasel error code

  This error happens after a participant is returned to orbit throughout an exercise or when inspecting gear. Bungie doesn’t but have an answer.

• Termite error code [resolved]

  The Termite error prevented gamers from hook up with the Destiny 2 beta, however seems to have been resolved. Restart the shopper should you’re nonetheless caught.

The Destiny 2 beta began first on July 18 for pre-order clients on PS4, then a day afterward Xbox One. It goes open to everyone on July 21.

The beta contains entry to a single-player mission, a strike, and two PvP maps and modes.

 
Source