{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/16/2016 6:51:30 PM
4
That guy got disconnected, you shoulda gone after the one that was trying to kill you.
English
-
Edited by Rufnek2014: 1/18/2016 8:17:59 PMAccording to my death screen later on, he was NOT disconnected. Come on....its simple net code issues and poor quality code handling. It adequately highlights the need for Bungie to address all the issues surrounding lag, red bar players, hit detection, range issues, etc.
-
Well you shoulda specified that in your post lol, cause most of the time if someone is standing still and not taking damage like that they're usually getting disconnected.
-
I can understand the confusion...but really I find too many people are experiencing too many 'odd' things. The challenge is that the vast majority will interpret some logical reason for the anomaly and that becomes 'fact' when in reality all the oddities should be taken as a whole and it becomes obvious that there are massive issues with net code, physics, locations in game of players and code cleanup.
-
I'm just saying that the most common thing associated with that kind of event is the person getting disconnected from the game, or getting the baboon error and being put back in the game. As the majority of us know as it is the coding and overall quality of PvP is crap, so a lot of things could happen that shouldn't.
