Destiny 2 has been struggling with a serious beaver problem for some time now. Behind the funny name lies an error code that completely spoiled the fun for some players. The problem is finally supposed to be a thing of the past.
What is the beaver problem about? In Destiny 2, beavers are not welcomed. But not because they gnaw on trees, but because this is the term for a really annoying error: the Beaver Error.
The Beaver Error causes, for example, that you land in an empty instance. Affected players are then kicked out of activities quickly, often multiple times in a row. Guardians are soon forced to give up once they are caught in the trap.
Especially PC players have been suffering from the problem since the migration of Destiny 2 to Steam.
This is what the players say: Players have been reporting for months that they are literally haunted by the Beaver Error. On reddit and Steam, there are plenty of such angry posts:
Every. Single. Time. I load into the game and it says “Beaver”, I’m removed from the game world and brought to the ship. […]
12 “Beaver-Errors” in 5 minutes.
Killed Joy via Steam
The problem can occur in all Destiny areas. It is particularly annoying when you get caught in the recently updated raids or in a Trials round, end up after a black screen in orbit, and then read that the beaver struck.
Beaver Error is finally supposed to be fixed on PC and Steam
Bungie’s report: The Destiny developer announced that on July 16, they were able to identify the source of most Beaver Errors. On July 22, an update followed stating that the error had now drastically decreased.
The error code has not completely disappeared (Bungie via Twitter) and can still appear occasionally. However, the nasty problem that caused constant disconnects has been resolved.
Hardware issue at Valve could be behind the problem
Wasn’t it Bungie’s fault? Forbes reports that attentive players have stumbled upon a strange coincidence. Because around the same time the announcement was made that the source of the Beaver Error was found, a technician at Valve solved a long-standing problem:
Curiously, the Valve employee found that the problem was not due to software but hardware – a defective relay was the culprit. Valve is the massive tech company behind the distribution platform Steam.
Whether this really is the reason for Destiny’s beaver problem remains unconfirmed. The main thing is that now gaming should be as smooth as possible.
It would be desirable if the hacker problem disappeared next: Destiny 2 has a serious problem with cheaters – Twitch streamer has had enough
