bungie error code porpoise. Recently, players have reported receiving the “Weasel,” “Bat,” and “Porpoise” error codes in Destiny 2, even though they are not intended to appear. Generally speaking, these three errors point to connection problems or problems with cross-play, both of which are easily fixed by double-checking your network settings. The issue, however, appears to be on Bungie’s end for the time being. In our comprehensive guide to resolving the Weasel, Bat, and Porpoise errors in Destiny 2, we’ll show you how to do it.
Destiny 2 Weasel Error Code
There are three common triggers for the weasel error code in Destiny 2.
The first is if you try to use the same account on multiple platforms at once with cross save turned on.
The second time you might meet a weasel is if you’re participating in an activity and then get banned.
The third and final cause usually appears after significant updates. The most recent patch for Witch Queen immediately crashes the game to that error screen. However, it recently started occurring when it shouldn’t have. According to the Bungie Help Twitter, the company is working to determine what is causing the issue. You will need to wait until they figure out what is going on.
Destiny 2 Error Code Porpoise
Here’s what Bungie recommends you do if you encounter the Destiny 2 porpoise error message: In order to proceed with your previous work, please reattempt the previous step where the error occurred. If you continue to see this error, close Destiny and start it up again. If you keep seeing this message, it’s probably because we’re conducting tests on our end; we appreciate your patience.
The problem, as you can infer from the tweet we linked to up top, is that the porpoise error has been affecting players at times when it shouldn’t. The problem is being investigated by the developers, who will hopefully find a solution soon. We’ll just have to see what happens.
Destiny 2 Error Code Bat
Bat is a generic network error in Destiny 2. It could be a problem with your internet service provider, with your computer, or with your connection to the Destiny 2 servers. Something on Bungie’s end may also be to blame, as appears to be the case at the moment. Again, please see the tweet we provided a link to above. These three error codes keep popping up for a lot of people, so I can only assume there’s a major snafu with the Destiny 2 servers. Therefore, the last resort is to try resetting either your connection or your console/client. The only other option is to patiently wait for Bungie to issue a patch.