JavaScript is required to use Bungie.net

Help

Help us help you.
4/28/2015 10:56:22 PM
2

Error code: beaver!!!

Ok i know that im just a lowly gamer and i know nothing, but you know what i cant play crucible, iron banner pr barely get into the tower. This beaver nonsense needs to be adressed. I never once got this error code until the supposed "hacking", idk what you did over there bungie but please fix it. It has nothing to do with the players routers or nat types. Stop making excuses and find a solution so everyone can play without this headache. If this issue isnt fixed, i wont be buying anymore bungie games. There are plenty of other games out there with better connection services than this trash.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Ive been beaverd 6 times in 5 mins on iron banner this is begining to piss me off

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • ERROR CODE: BEAVER / FLATWORM / LEOPARD BEAVER/FLATWORM/LEOPARD errors are caused by a failure to connect your console to another player’s console via the internet. This can be caused by connection quality issues (such as packet loss, ISP saturation, or general Internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation. However, they are most commonly caused by router or network configuration issues. We are also actively investigating the possibility of bugs that are causing these errors to happen even for properly configured and well-functioning networks. We are actively investigating this family of errors, and the following conclusions may be useful to you: We tend to see these errors most commonly when multiple consoles are connecting to the internet through a single router. Some players have been able to work around this issue by enabling UPnP on their router. Strict NATs tend to see these errors far more often than Open or Moderate NATs – opening your NAT can significantly reduce the frequency of these errors. http://bungie.net/NAT Some types of connection quality issues (packet loss, etc) can trigger this family of errors. The quality troubleshooting steps described in http://bungie.net/NETWORKING can help. Configuring NAT, UPnP and port forwarding for Destiny Certain networking issues are related to having “strict” or “moderate” rather than “open” NAT. Please note that an open NAT isn’t a magic bullet that solves all networking issues.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon