kicked from Gambit Prime because Error Code : beaver

[Raishin]

Srsly Bungie u system for Gambit prime was sucks
I got disconnect because ur server and then blame the player with suspend matchmaking ?

i got twice this week about this error make me really frustated

[Exesie]

me too....

[mintTea]

beaver guitar olive I experience them all and usually all are bungie server related errors.

bungie have done little to address them for not less than the last 14 months.

try changing the ping in steam settings to 1000 and see what happens, that should reduce but not eliminate bugie/bungie coding shortcomings.

[TheVoidSpirit]

You get a suspension because they don't know if it was an intentional DC or an error code.

[zOldBulldog]

The most insulting thing is that the game blames the player even when the issue is with the server, like the last time when bungie notified us that the servers were having major troubles and yet the game would tell *the whole team* that they had been kicked because their connection was bad and BTW "it is bad to leave a game in progress". What brain dead dev designed such a thing?

If they are such incompetent coders that they can't distinguish "who" dropped, they need to stop not just punishing people for it, they should also stop insulting us by claiming it was us when in reality they have no idea of where the problem happened.

[Raishin]

im about to kill primeval just 1/4 hp left then dc

[TheVoidSpirit]

Originally posted by zOldBulldog:

The most insulting thing is that the game blames the player even when the issue is with the server, like the last time when bungie notified us that the servers were having major troubles and yet the game would tell *the whole team* that they had been kicked because their connection was bad and BTW "it is bad to leave a game in progress". What brain dead dev designed such a thing?

If they are such incompetent coders that they can't distinguish "who" dropped, they need to stop not just punishing people for it, they should also stop insulting us by claiming it was us when in reality they have no idea of where the problem happened.

If you wouldn't get a suspension at all for a DC, you could just leave matches and ruin the experience for others. Unless you know a way to distinguish an intentional DC from an unintentional one.

[zOldBulldog]

Originally posted by TheVoidSpirit:

Originally posted by zOldBulldog:

The most insulting thing is that the game blames the player even when the issue is with the server, like the last time when bungie notified us that the servers were having major troubles and yet the game would tell *the whole team* that they had been kicked because their connection was bad and BTW "it is bad to leave a game in progress". What brain dead dev designed such a thing?

If they are such incompetent coders that they can't distinguish "who" dropped, they need to stop not just punishing people for it, they should also stop insulting us by claiming it was us when in reality they have no idea of where the problem happened.

If you wouldn't get a suspension at all for a DC, you could just leave matches and ruin the experience for others. Unless you know a way to distinguish an intentional DC from an unintentional one.

That's the thing, THEY kick you from matches then call it a disconnect even though you are having ZERO problems with any other application.

They are detecting latency, deciding that it is too high (without any further checks) and then booting you from a match while claiming that you disconnected. That is VERY different from a true disconnect and it is most of what we experience.

Even a high school kid with an ounce of brains could do better than this.

[MOSLEY]

"ERROR CODE: BEAVER

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.
These errors are most common 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.
Some types of connection quality issues (packet loss, etc) can trigger this family of errors. If you are using WiFi to play Destiny, we strongly recommend switching to a wired connection. For more: https://www.bungie.net/en/Help/Troubleshoot?oid=13604
For additional troubleshooting steps, please visit our Network Troubleshooting Guide."

Sounds like your connection is the problem.

[zOldBulldog]

Originally posted by MOSLEY:

"ERROR CODE: BEAVER

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.
These errors are most common 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.
Some types of connection quality issues (packet loss, etc) can trigger this family of errors. If you are using WiFi to play Destiny, we strongly recommend switching to a wired connection. For more: https://www.bungie.net/en/Help/Troubleshoot?oid=13604
For additional troubleshooting steps, please visit our Network Troubleshooting Guide."

Sounds like your connection is the problem.

Sigh, that could be true in a game with proper network code and real error detection. But to anyone (especially another developer) with a bit of experience in the field it is obvious that these are just excuses to hide their sloppy work.

Even from a common sense standpoint and without any technical know-how involved, did you consider how curious it is that the same players that experience problems with Destiny 2 have zero issues with other games? Or even other more demanding applications running at the same time like voice or video?

[Raishin]

i don't have any problem with other mode, playing more than 10 hours straight without dc even once. When come to Gambit Prime always dc once or twice

[Maverick]

Originally posted by Delta:

Originally posted by zOldBulldog:

Sigh, that could be true in a game with proper network code and real error detection. But to anyone (especially another developer) with a bit of experience in the field it is obvious that these are just excuses to hide their sloppy work.

Even from a common sense standpoint and without any technical know-how involved, did you consider how curious it is that the same players that experience problems with Destiny 2 have zero issues with other games? Or even other more demanding applications running at the same time like voice or video?

Mad Cause Bad Internet.

retarded kid why are you here then

[zOldBulldog]

Originally posted by Night Maeve:

Originally posted by Delta:

Mad Cause Bad Internet.

retarded kid why are you here then

ROFL @severe necropost