Destiny 2 Weasel, Bat and Porpoise error codes have been appearing for people lately, even though they aren’t supposed to, and people want to know how to fix them. For the most part, these three errors indicate connectivity issues, or some error with cross play; relatively benign stuff that you can usually remedy by checking your connection. However, the problem is on Bungie’s side, as seems to be the case at the moment. We’ll share all we know with you in our Destiny 2 Weasel, Bat & Porpoise Error Fix guide.
Error Code Weasel Destiny 2
Normally, the error code “weasel” in Destiny 2 pops up in three situations.
- The first one is when you attempt to log into multiple platforms simultaneously with cross save enabled on that account.
- The second situation where you might encounter “weasel” is when you’re in an activity and get a ban.
- The third reason pops up usually after some big updates. With the latest Lightfall update the game will send you straight to that error screen. However, it seems to now be cropping up when it shouldn’t at the moment. On the bright side, Bungie is working on figuring out what’s going on, according to the Bungie Help Twitter. So, you’ll just have to be patient until they figure out what’s going on.
Error Code Porpoise Destiny 2
When it comes to the Destiny 2 “porpoise” error code, this is what Bungie says you should do, according to this post: Please retry that activity again and resume what you were doing before the error occurred. If you encounter this error again, please exit Destiny then relaunch. If you continue to see this error, it’s likely due to testing we are doing on our end, please pardon our dust!
The issue is that, as you can kinda infer from the tweet we’ve linked above, the “porpoise” error has been hitting players even when it shouldn’t at the time of writing. The developers are looking into the issue and will hopefully solve it soon. We’ll have to wait and see.
Error Code Bat Destiny 2
Error code “bat” in Destiny 2 is a general network issue. It can happen if your internet connection is spotty, or your connection to Destiny 2 servers is hiccuping, or it might even be an issue with your internet provider. It could also have something to do on Bungie’s end, as seems to be the case right now. Once again, I refer you to the tweet we’ve linked up top. I can only infer that there’s some big mess happening with the Destiny 2 servers that are causing these three error codes to keep appearing for a bunch of people. So, the most you can do is reset your connection or your console/client and see if that works. Other than that, wait for Bungie to fix the situation.
If you need further help with Destiny 2 Shadowkeep, check out our guides on Dead Ghost Locations, Jade Rabbit Locations, and Eyes on the Moon - How to Start Vex Invasion. If it's Exotic Weapons that you're after, we've got you covered with our Pain And Gain Exotic Quest and Deathbringer Exotic Rocket Launcher - Symphony of Death guides. Going back in time for new players, we can offer you guides like Ikelos Weapons - How to Get SMG, Sniper Rifle, Shotgun, or, if you're playing Forsaken content, guides like Corsair Down & Badge - Dead Body Locations.