Bird Error Code Destiny 2

Destiny 2 error codes - Olive, Chicken, Weasel and Centipede errors, plus other known issues including PS4 fault CE-34878-0

Got one of many mysterious error messages? Hither'due south what Bungie suggests to do side by side.

Destiny 2 error codes are something you'll run across if something has gone wrong during your session - peradventure a download upshot, most certainly a connection problem - just always delivered with a mysterious code word named later on an animal or fruit.

Bungie has been upfront and said to expect them as office of the Destiny 2 beta - it is a pre-release test after all - and if it'due south anything like the first game, they will come in many types.

Destiny ii mistake codes we know about so far, including Olive, Chicken, Weasel and Centipede

Here is a list of error codes encountered in Destiny 2 then far, and what to practise next. Be fully aware that non every error code has a straightforward solution - some things, such as server bug, 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 master game likewise.

And then far Bungie's main piece of advice is to relaunch the client and 'power wheel' the arrangement - which is substantially a full restart and not going to standby. Connected errors could as well suggest Bungie is doing tests on its end, so information technology may exist a example of being patient until this is fully resolved.

Chicken - Bungie recommends retrying the activity again, and if information technology occurs once more, close the Destiny client and restart. Bungie says information technology 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 Aid (@BungieHelp) September xi, 2017

To come across this content delight enable targeting cookies.

Weasel / Centipede - This is a "general" networking error. While connecting to a wired connectedness volition assist, the principal affair is worth addressing your NAT type (from Strict / Type 3 into Open / Blazon one). Sometimes this will be incommunicable - if you are using a university or role network, for example - or it could be something your ISP should sort.

There is too 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 besides cropped up during the beta. At the time Bungie investigated and fixed an consequence causing them more often than not. Otherwise, those on the Destiny sub-Reddit have offered their own solution, which involves changing clan settings.

We accept addressed an issue causing elevated WEASEL errors in the Destiny 2 Beta. Nosotros are continuing to investigate OLIVE and MOOSE errors.
— Bungie Help (@BungieHelp) July twenty, 2017

To see this content please enable targeting cookies.

Moose - This is vaguely described every bit a "general networking error". Players report it occurs during the opening Homecoming mission of the beta, with Ikora and enemies failing to load earlier the error occurs.

Bungie is currently investigating the issue, and until so, recommends you restart the action and attempt once more.

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 xviii, 2017

To see this content please enable targeting cookies.

Termite - Described as "Failed to download configuration files from Bungie servers", this has appeared regularly for those who attempted to admission the Destiny two beta as shortly as information technology began.

It was likely due to high server demand, and Bungie has said the mistake should have now resolved itself.

If it happens again, proceed trying to log in and information technology should remedy itself. Bungie also recommends you also effort to exit and reload the Destiny 2 beta customer between log in attempts, too.

Certain members on the official Bungie support site are also recommending PS4 users Restore Licences - performed past going into Settings, so PlayStation Network / Account Management.

If you lot are nevertheless getting this after a significant menstruum of time and have exhausted usual troubleshooting measures, it also suggests deleting and re-installing the game, but with servers naturally beingness upwardly and down, we'd do this only every bit a very final resort.

Issues causing error lawmaking Termite on the PS4 Destiny 2 Beta should at present be resolved. Please restart Destiny if you still see this fault code. https://t.co/vRGEDRvIHo
— Bungie Help (@BungieHelp) July eighteen, 2017

To meet this content delight enable targeting cookies.

Destiny 2 known issues including PS4 mistake CE-34878-0

Alee of the Destiny two'south launch, Bungie has warned players well-nigh Destiny Server Queues, which may occur during "periods of high traffic" earlier you can log into the game. The only fix for this is to but be patient, though information technology has specified several notes:

If you lose your connection while waiting in the queue, you volition be removed from the queue.
Co-ordinate to Bungie, how long you will wait depends on server traffic and the numbers of people playing. At launch, nosotros suspect there will be quite a loftier volume.
If, once you achieve 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 upshot are PS4 crashes, particularly when it comes to PS4 Pro. There is no known fix right at present, merely PlayStation itself has said information technology is working with Bungie "to resolve" the result. Nosotros assume a patch will be coming to assist in the coming weeks, merely for now Bungie recommends disabling HDCP settings to help "reduce or circumvent this fault" in the meantime.

We're enlightened that some Destiny 2 users have seen crash problems on PS4 Pro. We and Bungie are working to resolve, thanks for your patience.
— Ask PlayStation (@AskPlayStation) September xi, 2017

To see this content please enable targeting cookies.

At the time of writing, those are the known bug affecting the launch right now, and nosotros'll update this page when nosotros hear more.

Flavour of the Haunted is here! Get upwardly to speed with our levelling guide. For The Witch Queen, learn how to go Exotics including Dead Messenger and Parasite. Late last year, we saw the Bungie 30th Ceremony, which adds the Grasp of Avarice dungeon, Strange Coins and new Exotics, including the Gjallarhorn and Forerunner.

Common error codes in the original Destiny

While we can't exist certain mistake codes will match those of the original Destiny, here is a run downwards of the well-nigh common fault letters encountered during the three years of the original Destiny, and what to do next, in the upshot you lot come across them again in the sequel.

Baboon: This network connection upshot is due to packet loss between your network and the game servers. It's recommended you lot connect to a wired connection, or force quit the game to effort and remedy it. Otherwise, try standard networking troubleshooting techniques on the console and network.

Beaver: This is a network connectivity outcome. While the cause is unknown, it was speculated to do with matching with other players of unlike NAT settings in social areas, and was addressed as part of a hot set in summer 2016.

Beetle: This one is vaguely described as a "general networking fault". The disconnect was reported to Bungie every bit it happens, and if information technology repeats over and over, attempt standard networking troubleshooting to the console and network.

Bird: Described as a full general networking error by Bungie, many players study this disconnect occurs after performing multiple kills in Crucible matches - far from platonic timing. Few solutions are available exterior of general troubleshooting techniques and / or fully restarting the panel.

Tapir: The game is "likely" down for maintenance - checking official Bungie accounts will let y'all know about scheduled and unscheduled downtime.