Destiny 2 error codes are something you'll encounter if something has gone wrong during your session - possibly a download issue, almost certainly a connection problem - but always delivered with a mysterious code word named after an animal or fruit.
Bungie has been upfront and said to expect them as part of the Destiny 2 beta - it is a pre-release test after all - and if it's anything like the first game, they will come in many types.
Destiny 2 error codes we know about so far, including Olive, Chicken, Weasel and Centipede
Here is a list of error codes encountered in Destiny 2 so far, and what to do next. Be fully aware that not every error code has a straightforward solution - some things, such as server issues, could simply be out of your control.
Olive - This started to occur more in frequency in the beta, and seems to have cropped up in the main game too.
So far Bungie's main piece of advice is to relaunch the client and 'power cycle' the system - which is essentially a full restart and not going to standby. Continued errors could also suggest Bungie is doing tests on its end, so it may be a case of being patient until this is fully resolved.
Chicken - Bungie recommends retrying the activity again, and if it occurs once more, close the Destiny client and restart. Bungie says it it keeps happening, it is likely testing its end.
Issues causing some Destiny 2 players to receive OLIVE and CHICKEN errors, as well as PONY and SHEEP errors have subsided.— Bungie Help (@BungieHelp) September 11, 2017
Weasel / Centipede - This is a "general" networking error. While connecting to a wired connection will help, the main thing is worth addressing your NAT type (from Strict / Type 3 into Open / Type 1). Sometimes this will be impossible - if you are using a university or office network, for example - or it could be something your ISP should sort.
There is also Weasel, which is similar to Centipede, so use the same solutions there. Otherwise, restarting the console (without going to standby and ensuring the power is off fully) is recommended.
Weasel also cropped up during the beta. At the time Bungie investigated and fixed an issue causing them more often than not. Otherwise, those on the Destiny sub-Reddit have offered their own solution, which involves changing clan settings.
We have addressed an issue causing elevated WEASEL errors in the Destiny 2 Beta. We are continuing to investigate OLIVE and MOOSE errors.— Bungie Help (@BungieHelp) July 20, 2017
Moose - This is vaguely described as a "general networking error". Players report it occurs during the opening Homecoming mission of the beta, with Ikora and enemies failing to load before the error occurs.
Bungie is currently investigating the issue, and until then, recommends you restart the activity and try again.
We are investigating reports of Moose errors in the Destiny 2 Beta. Players who encounter this error should relaunch their activity.— Bungie Help (@BungieHelp) July 18, 2017
Termite - Described as "Failed to download configuration files from Bungie servers", this has appeared regularly for those who attempted to access the Destiny 2 beta as soon as it began.
It was likely due to high server demand, and Bungie has said the error should have now resolved itself.
If it happens again, continue trying to log in and it should remedy itself. Bungie also recommends you also attempt to exit and reload the Destiny 2 beta client between log in attempts, too.
Certain members on the official Bungie support site are also recommending PS4 users Restore Licences - performed by going into Settings, then PlayStation Network / Account Management.
If you are still getting this after a significant period of time and have exhausted usual troubleshooting measures, it also suggests deleting and re-installing the game, but with servers naturally being up and down, we'd do this only as a very last resort.
Destiny 2 known issues including PS4 error CE-34878-0
Ahead of the Destiny 2's launch, Bungie has warned players about Destiny Server Queues, which may occur during "periods of high traffic" before you can log into the game. The only fix for this is to simply be patient, though it has specified several notes:
- If you lose your connection while waiting in the queue, you will be removed from the queue.
- According to Bungie, how long you will wait depends on server traffic and the numbers of people playing. At launch, we suspect there will be quite a high volume.
- If, once you reach the front of the queue and for some reason cannot connect, then you must re-enter from the back of the queue.
The other known issue are PS4 crashes, particularly when it comes to PS4 Pro. There is no known fix right now, but PlayStation itself has said it is working with Bungie "to resolve" the issue. We assume a patch will be coming to help in the coming weeks, but for now Bungie recommends disabling HDCP settings to help "reduce or circumvent this error" in the meantime.
We're aware that some Destiny 2 users have seen crash issues on PS4 Pro. We and Bungie are working to resolve, thanks for your patience.— Ask PlayStation (@AskPlayStation) September 11, 2017
At the time of writing, those are the known issues affecting the launch right now, and we'll update this page when we hear more.
For Season of Plunder, we have the Sails of the Shipstealer quest, Treasure Coordinates and Map Fragments, Cryptic Quatrains and weapons such as the Quicksilver Storm and Taipan 4FR. Meanwhile, there's the arrival of King's Fall and King's Fall challenges, plus weapons including Doom of Chelchis and Touch of Malice. For The Witch Queen, learn how to get Exotics including Dead Messenger and Parasite.
Common error codes in the original Destiny
While we can't be certain error codes will match those of the original Destiny, here is a run down of the most common error messages encountered during the three years of the original Destiny, and what to do next, in the event you come across them again in the sequel.
Baboon: This network connection issue is due to packet loss between your network and the game servers. It's recommended you connect to a wired connection, or force quit the game to try and remedy it. Otherwise, try standard networking troubleshooting techniques on the console and network.
Beaver: This is a network connectivity issue. While the cause is unknown, it was speculated to do with matching with other players of different NAT settings in social areas, and was addressed as part of a hot fix in summer 2016.
Beetle: This one is vaguely described as a "general networking error". The disconnect was reported to Bungie as it happens, and if it repeats over and over, attempt standard networking troubleshooting to the console and network.
Bird: Described as a general networking error by Bungie, many players report this disconnect occurs after performing multiple kills in Crucible matches - far from ideal timing. Few solutions are available outside of general troubleshooting techniques and / or fully restarting the console.
Tapir: The game is "likely" down for maintenance - checking official Bungie accounts will let you know about scheduled and unscheduled downtime.