JavaScript is required to use Bungie.net

ヘルプ

助け合おう
6/11/2019 10:09:54 AM
2

Weasel error led to temporary ban; a Destiny 2 networking suggestion

I play on PC (Win 7 Pro 64), and for the last couple weeks or so I've been getting weasel errors every 40 minutes or so that I play Destiny 2. It makes playing multiplayer not only frustrating from a match completion standpoint, but from the fallout due to the way Bungie has programmed Destiny 2:[b] the game thinks you left the match willingly, as opposed to being disconnected due to an error. This means I got temporarily banned from Gambit due to my "quit" ratio being higher than my completion ratio, even though it's an error and NOT a willing dropout. [/b] Surely Bungie's servers can tell when there was a problem with someone's network versus a willing disconnect. If so, the game shouldn't punish players who have internet issues. (I am currently running a very long ping of my network to find any packet loss; it's worth noting that I did not have the weasel error at all until about 2 weeks ago, though as I said I'm still trying to find the cause) Is there a ping threshold for the game (e.g., 300ms) that would result in a weasel error?

投稿言語:

 

マナーを守りましょう。投稿する前に、Bungie の行為規範を確認してください。 キャンセル 編集 ファイアチームを作る 投稿

トピック全体を表示
  • The servers punish players for ‘leaving’ because this gives their team a disadvantage. It does this both for error codes and for willing leaves. Willingly leaving a match warns you immediately not to, until eventually you get a restriction for quitting. With network errors, it restricts you so that you can fix your issues and to prevent you harming other teams. The servers do know the difference, and they punish you for playing online with poor connection [u]repeatedly.[/u]

    投稿言語:

     

    マナーを守りましょう。投稿する前に、Bungie の行為規範を確認してください。 キャンセル 編集 ファイアチームを作る 投稿

このコンテンツはご覧いただけません。
;
preload icon
preload icon
preload icon