In Destiny , the BEAVER error code still greatly disrupts the player experience.
Update: Bungie has an update 2.3.1.1 available.
Currently, many Guardians are feverishly working on their home networks: since Tuesday, after the activation of update 2.3.1, a troublesome beaver has been roaming the Destiny universe, supposedly causing complications with NAT settings.
The beaver is not a cute rodent that likes to build dams in its spare time, but an extremely annoying error code. Guardians are randomly kicked out of the game and receive the BEAVER error.
Only a few hours after the appearance of BEAVER, Bungie released a workaround for the problem: The beaver is said to be associated with strict and moderate NAT settings, thus the recommendation was made: Set the NAT settings to open to curb the frustrating beaver flood. This is why many Guardians are currently trying their hand as DIYers and tinkering with their home networks.
The problem does not lie with the home network, but with Bungie
Now the community manager Cozmo has spoken out to clear up uncertainties. His statement begins with: “It was us.”
He clarifies that the BEAVER error was introduced with update 2.3.1 and definitely lies with Bungie. The advice regarding the NAT settings is meant to show a way to mitigate the problem while developers are working hard on a fix. One should not misunderstand this tip as Bungie trying to deflect blame. He apologizes for the inconvenience. As soon as there is more information, the community will be informed.
Meanwhile, discontent is growing among the Guardians. For days, it’s been problematic to get into the Tower, the Reef, the Crucible, and other game modes. Either you can’t get in at all, or there is always the imminent danger of the beaver sneakily kicking you from the server.
On reddit, the advice also spreads: If there have been no issues with your internet connection so far, keep your hands off the home network. The problem lies with Bungie. You might actually cause more damage by fiddling with the router settings. Because even users who have set everything to “open” are still haunted by BEAVER.
Here you can read more about the BEAVER error in Destiny.
