Many error codes can rear their heads to ruin your planned session in Destiny 2. They can be an absolute nightmare, and the Bat error code definitely fits that particular description well. Don’t worry, though, because you can fix it.
Destiny 2: The Final Shape definitely didn’t have the smoothest launch in the game’s history. In fact, it may have been the biggest, but that’s a conversation for another day. Following it and leading into the Echoes Episode, we’ve had lots of new errors pop up to stop us from playing and just sit there like a wall you can see your goal through but have no way to get around. Thankfully, there are some potential fixes you can try.
How to fix error code Bat in Destiny 2
To fix Destiny 2 error code Bat, you must play the activity you’re trying to get the most out of in solo narrative mode. The error seems to pop up most when fireteams enter missions and activities with story elements that everyone wants to see, but occurs and prevents anyone from seeing them at all.
You can change your experience to the narrative mission in the director. Just select the story mission mode rather than the matchmaking option, and you should be fine. Also, and this probably goes without saying, don’t try to do the same activity in a fireteam of friends because you’ll get the same result.
What is error code Bat in Destiny 2?
Destiny 2 error code Bat occurs when players want to watch a story cutscene in an activity, particularly the Excision activity, but can’t because they’re in a fireteam and something goes wrong in the background. It results in no one seeing the cutscene.
This is terrible because the end of Excision and all the cutscenes in Destiny 2 are phenomenal. So, naturally, you might want to watch them again in-game instead of having to resort to YouTube. That’s why you need to play these activities like Excision solo, so you don’t miss out on that glorious cutscene magic when it should be all yours for your efforts.
Note that the error can pop up for other story moments. Excision was the most recent cause of the code following the conclusion of The Final Shape‘s race to world first in Salvation’s Edge. You might be seeing it due to another activity, but the fix remains the same.
