No one enjoys encountering error screens, but the error codes in Destiny 2 have become a source of amusement due to their amusing names. While players still find them frustrating, it’s hard not to crack a smile when everyone is hit by a “weasel” code.
On November 8th, a Destiny 2 player suggested that Bungie should create an Error Codes section in the game’s collection tab. This would allow players to view all the weapons and armor they have discovered, as well as the error codes they have encountered.
To take it a step further, Bungie could even add error codes as triumphs in the game. Similar to tracking triumphs and showcasing them on your emblem, players would be able to display how many times they have received a specific error code. Imagine proudly showing off your 4,200 beavers!
Destiny 2 players have also pondered what kind of title a player could earn for collecting all the error codes. Suggestions range from “Zookeeper” due to the abundance of animal-themed codes, to “Naturalist” to encompass errors with plant names. The inclusion of the “guitar” code may be a bit puzzling, but perhaps playing a song for a weasel can be considered nature-friendly?
Some players would go as far as farming Iron Banner to obtain the desired title, while others might intentionally replicate errors in the game to achieve their goal. It would undoubtedly be chaotic, but nothing can surpass The Craftening at this point.
In recent months, Destiny 2 servers have had a life of their own, leading creators like Aztecross to create memes about them. One memorable video featured a warning saying “I’m boutta do this shit,” before promptly booting the player back to orbit. Kudos to the editors for such a high-quality clip.
Jokes aside, it would be beneficial to have a readily accessible list of Destiny 2 error codes and their explanations for when the servers act up again. While they can currently be found on the Bungie Help website, the articles are outdated and the descriptions may not be entirely accurate.
Source: DOTESPORTS
