{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/17/2020 1:14:14 PM
14
ANTEATER:
This can be the result of ISP issues, packet loss, complications with various network hardware, Wi-Fi glitches and other impacting variables to general connection stability. We recommend as a first step that players ensure their current connection is working as intended to remove any outside variables.
English
-
don't mean to sound off, but what Anteater code kicks all the players including the enemy team out of a trials match. You claim its a problem with ISP, inferring potential individual randomness. But that's not the case. I also forgot to mention my teammates got Guitar Error Code (seems too random for Guitars error codes in PvP given how long it took to fix that in the Last Wish Raid), but left it out because I can neither confirm nor deny it. Can you at least look into the problem because I wouldn't so easily complain about something that affected both my team and my opponents team resulting in both of our losses.
-
Editado por Decca0805: 10/17/2020 1:31:51 PMWhich match was this exactly? I can’t find such a match in your game history. As destiny uses Peer To Peer networks for PvP, there must be stability from all parties for the server to hold up. If there were several players with severe network issues connected, it might cause everyone to lose connection. Can you ensure your network meets the minimum requirements at all times?
-
what you want me to link the PGMR? I can link the both matches
-
That would be helpful as I can’t seem to spot them. Re-read my other message, I added more to it.
-
I can assure you that me and my mates connection meets beyond the minimal requirements as we have been playing together for almost a year now with no problems such as these, aside from the occasional Dos Attacks which is quite noticeable. Its just a bit unusual to have both teams booted from a trials match both receiving losses. Here are the PGCR... Bungie.net: https://www.bungie.net/en/PGCR/7035979545?character=2305843009261979047 https://www.bungie.net/en/PGCR/7033593974?character=2305843009261979051Destiny Tracker Network: https://destinytracker.com/destiny-2/pgcr/7035979545 https://destinytracker.com/destiny-2/pgcr/7033593974
-
And you were kicked from these matches with an error code? It shows victory on here. DoS attacks are noticeable because they don’t just kick you out with an error code, they literally turn off your router (essentially.) A DoS attack wouldn’t allow you to just start matchmaking again, you’d have to wait for your home network to come back online. If you’ve been removed from matches with error codes outside of the circumstances I described, that is highly likely to be a network error. If this is the case, I can determine a potential network problem if you provide me with; Upload speed Download speed Latency Packet loss (if possible) Jitter (if possible) Are you on a wired or wireless connection?
-
I'm on a wired connection, might I remind you it was my whole team and the opponents team that was booted. Not just me, my friend even has messages from the other team inquiring if we were error coded from the game as well. I very well know it was not a Dos Attack, because me and my team were able to start another match immediately. we did receive a loss as well did the other team but it costed us our mercy as well as the other team. Look I'm gonna give it to you short and easy. I'm not looking to report anyone or seek action against anyone. I'm here to address that a problem from both sides had occurred, upon multiple times now and it seems to not be an individual network problem but something beyond that. I know you are just doing your job but it seems I'm not being just not being heard. But yeah I can try to find those stats for you out if it will further help the company address a potential problem and remedy it for the community as a whole. Because a bit proactiveness is always nice. Just need to know where I might find that information for you.
-
I’m not a bungie representative, I’m just another player trying to figure out what the problem is where possible and offer suggestions on how to fix it. The scenario you’re describing is very unusual, and I can’t imagine what would be causing it outside of everyone in that match simultaneously having a significant network error - which is extremely unlikely. Trust me, I hear you, I just can’t explain it. The stats could help either way, just to confirm there’s absolutely nothing off at all. Being on a wired connection in the first place puts you a long way towards being in the clear by default either way.
-
Lord have mercy. I'm done here, have actually been done in. Not worth my time anymore.
-
Well what did you think? Bungie doesn’t have an official support thing for this. Much easier for them to use people like me, who are free to use, to give help to people.
-
I think I have been catfished and was about to give you a whole bunch of information that essentially would have only just reiterated what I already knew the entire time. You have no ability to check to see if it was a bungie related error. You quite literally can only confirm whether someone's internet is trash or not. And that's is not useful, especially when under the guise of helping others, when in all actuality it's just making other intelligent people doubting themselves to actually think that they are ignorant. I know my stuff, all you did was make me look stupid. That's not cool.
-
No, I don’t believe I did. If you already knew all of the answers why are you even here asking for help? I can only offer what I am able to, that is correct. The point is this error is given by a certain cause and you claim to be getting it for something different, which doesn’t make a whole lot of sense. The majority of issues with destiny boil down to network problems. That’s just the fact of it and I’m sorry to disappoint by not coming to the conclusion that bungie is terrible for one reason or another which, lets be honest, is the answer you were looking for. I can’t offer a fix because I don’t understand the problem. I’m not just going to make one up for you.
-
No you don't listen at all, this shouldn't even be a discussion, if it were a bungie they would have immediately noticed that something was wrong if the all members of the entire match were booted from 1-2 error codes not resulting from Dos Attack. It's simple enough to put 2 and 2 together. What part doesn't make sense to you that I am trying to inform Bungie of an obviously unusual problem that affects the entire match and not just one team? You are trying to remedy from a single individual's possible problems and are completely missing the point where I state over and over again that the "entire lobby was booted". And I digress, you still had the audacity to continue by clarifying whether my internet connection was stable as if it were an individual problem when it was collective problem. No I wasn't looking for a response that " Bungie is terrible" because many times when there was a problem and I addressed it to an actual employee, it would be noticed. You can stop trying to get that exclusive Ninja emblem now, you have been found out. You were not helpful at all, all you did was waste my time on unsurprising redundant knowledge.
-
Trust me if anyone’s looking to be ninja it isn’t me. Pretty sure I’m in a long list of names that aren’t ever getting on there. Im sorry I didn’t give you the answer you wanted. Feel free to continue screaming until someone does or to simply move on. Bungie isn’t going to answer you, as that is precisely why this forum exists.
