{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Spawn:
1/25/2015 4:04:59 AM
2
IT'S NOT US, IT'S YOU, BUNGIE!!!
Enough with the cut and paste responses to the networking issues.
The problem is obviously not on the players' end if nearly everyone is having issues. So, stop telling us to reconfigure OUR connections and get to work on YOURS.
-
Posts like this are so ignorant it's hard to take them seriously. Bungie does not blame the player connection unless the error code is related to our network settings specifically. They offer possible solutions for error codes if they are available. That way the user can try something to fix the problem. If it works, great. Continue gaming. Otherwise, Bungie is continually hard at work trying to find the source of the network issues that plague some players. To say 'most' players experience these codes is incredibly inaccurate. The vast majority of players enjoy Destiny with zero errors. You only get the impression 'everyone' has these errors by looking at the forums. Of course there's going to be a lot of posts on the forums about error codes. That's what the forums are for. No one is going to come onto the forums to say 'I have no network issues with Destiny.' Believe me, I know how frustrating the error codes can be. I used to experience the bee error code every 15-20 minutes. I haven't gotten a bee error in months.
