The error code Buffalo is one the most simplest errors to get rid of, yet one of the most annoying one. Destiny 2 being an online game, is rendered useless if this error shows up.
Explaination of Code Buffalo
When error code BUFFALO pops up, it means there is one major issue, i.e., when a person is already logged into a game and is trying to login again. Worst part, this error code isn’t just limited to PCs but also shows up on Xbox and Playstation. There can be various reasons for this error code to pop up and each has it’s own solution.
Reason 1: Server Maintenance
If servers are down for maintenance then Bungie usually notifies it’s clients well in advance. In case there were no such notification or then one can always check the server status from the links given below:
- For PC: https://battle.net/support/
- For PlayStaion: https://status.playstation.com/
- For Xbox: http://support.xbox.com/xbox-live-status
There is no solution for this problem, other than waiting till the servers are up and running.
Reason 2: Packed Servers
Considering the huge player base it’s no surprise that sometimes servers might be filled up.
There are 2 solutions for this.
- If a person is not too selective about which server to play on, then he/she can simply change the region, i.e., choose a different server.
- This one is for the people who are not fond of changes and have patience, keep trying to reconnect. It should connect the moment someone disconnects from that server.
Reason 3: Expired Subscription
This reason is specific to console users. For PlayStation users it’s the PlayStaion Plus subscription that might have expired. In case of Xbox users it’s the Xbox live subscription.
Solution? Renew thy subscription already!
Reason 4: Logged in from Multiple PCs
Bungie doesn’t let a user login to the same id from different PCs at the same time, well, for obvious reasons.
Solution for this would be to logout of the Battlenet client if there is any plan to switch PC.
Reason 5: Battlenet Client Error
Sometimes the client might be having problem communicating with the server after logging in.
This problem can be solved by simply logging out and logging in again. Sometimes restarting the Battlenet Client might do the trick if re-login doesn’t work.
Reason 6: Unknown
There might be a time when none of the solutions given above work. In such a case, deleting the cvars.xml file does the trick. A fresh version of this file is created when you launch the game after deleting it.
Please note: Deleting cvars.xml file resets all custom player settings.
There are 2 ways to locate this file.
- Directly access the directory: \Users\USER_NAME\Appdata\Roaming\Bungie\DestinyPC\prefs\
- Type %appdata% in Run dialog box and press enter. This command opens the Appdata folder from where Roaming\Bungie\DestinyPC\prefs\ can be accessed.
Featured Image Credits: Bungie
Leave a Reply