JavaScript is required to use Bungie.net

Help

Help us help you.
4/18/2020 1:44:05 AM
5

Unexpected network manipulation warning

Today, I played several Iron Banner matches with friends on Stadia, then swapped over to PC to run a Trials card. While on PC, 7 of the 9 matches we played tonight had someone get error coded out. 6 of the 7 matches, a member of the opposite team would get dropped, on one match I was dropped. After playing to 7 wins (with 2 losses on the card), I stopped playing and attempted to switch back to Stadia to continue playing Trials with some other friends on that platform. After having some stream buffering issues with Stadia, I was able to get a solid connection and proceeded to leave the tower. Once I reached orbit, I received the warning in the attached imgur link. Please feel free to check my previous match history per the trials.report link below, I do not have any history of DDOSing (and I uphold my clan not to cheat or DDOS while playing PVP - I have previously banned people for that). Tonight's matchmaking was severely unfortunate for the other teams, and I want to ensure that I will not be receiving a ban or be getting blamed for unfortunate matchmaking results where players are unable to keep a consistent connection due to in-game error codes. To my knowledge, DDOS attacks on PC players are extremely rare now due to the network topology changes put into place by Bungie at the beginning of this season for Steam accounts, yet network errors are extremely common and happen with great frequency. I would like to have someone check into this to ensure that I will not receive a ban for the unfortunate circumstances. Please see my Trials.Report from tonight's matches (as well as my previous weeks' activity). https://trials.report/report/2/4611686018452852272

Posting in language:

 

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

View Entire Topic
  • As much as I would like to blame my two teammates for DDOSing, there are critical pieces of information I would like to point out here. 1 - A portion of my evening was spent on Stadia, where DDOSing is impossible due to the hosted nature of the platform. If someone can DDOS others on Stadia, then I would expect Google would like to have a word with those users for multiple reasons. 2 - Bungie changed the network topology for Steam players, forcing them onto Steam's networking protocols for peer to peer communication. This is DDOS protection and touted by Bungie as such. I have confirmed that the same networking rules that previously applied to consoles no longer apply to Steam, as local communication travels to Steam's servers where the peer to peer handshake occurs. Again, if someone can DDOS another player via Steam's servers, I would think that Valve would like to have a serious word with those who are successful as well. 3 - Feel free to check my fireteam's matchmaking history, as well as my own. All of my fireteam members from tonight have our match history public and open for all to view. Typically, anyone who is going to DDOS others would have hidden match history and would have many more games where another player was disconnected. 4 - As much as I would like to believe my team was attempting to DDOS others, I more believe that the errors in the game's updated networking are the culprit. There have been days where it takes 5-10 attempts before I'm able to join PVP matches due to the constant animal network errors. These errors did not frequently occur prior to this season, and if they did occur, they were rare enough that they could be ignored. My clan has experienced more networking errors this season than we have since switching to PC for Shadowkeep. If other players don't want to take my word for the issues I've been experiencing, then that's OK. I'm more looking for some sort of acknowledgement from Bungie than anything.

    Posting in language:

     

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

    2 Replies
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon