{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by OohaPieceaCandy:
10/9/2014 4:06:40 AM
470
(Edited) Absolute proof Iron Banner is complete bullsh*t!
I was making a new warlock and got through the 4th mission or so. I was level 4 with my friends who are all high level like my main. I decided to test Iron Banner because last night I really didn't see much of a difference playing with my lvl 30, it felt like regular crucible. So I joined up with my friends to play some Iron Banner. I was expecting to walk in and get one shotted with an ankle shot, instead I was baffled at what happened. Watch the video, and let me know what you think.
Edit- Here is my second video as well, this was my third game and did even better than my first. http://youtu.be/h2rUdKnB_4M Check it out and let me know what you think! Also thanks Deej for replying at least, I was not expecting that. Although you did leave us with your usual vague wait till the update answer. Please don't just address it, please actually fix it!
A big shout out to my fireteam, thanks for helping me make this video ClearVue, AssasiNinja187x, ojndeath1, DukeNukem786, and xxKunntryxx
-
4 RepliesEdited by doomshaman: 10/9/2014 12:50:02 AMI am not surprised at all but the root cause is the netcode. Players are complaining about everything else but there is no way to tell anything with a bad netcode. The main problem with the crucible is the netcode allowing too much lag and the high latency to be abused. It's open game for lag switches and/or anything that hogs the bandwith. The guy with the highest latency in the match has the upper hand before anything else, gear, level, class and skill. Bungie needs to fix the netcode before anything else and have the matchmaking based on same range ping values, anyone's ping spike during the match should be disconnected from the session.
