Edit: super late reply forgot to post scrub mobile....
I think there was just network shenanigans for being day one of Iron Banner.
Ha, we kept running into random issues. On our final run the swordbearer was up in the right room with us after the ogres. Luckily we kept our composure, took him down quick in there and drizzy sliced up Crota one last time..
Yeah we were seeing a lot of weird stuff last night. A lot of the usual disappearing swords and quick stand auto-kill garbage but also jacked up stuff that really seemed to be on the Destiny network/server side of things. Like StereoType said, when we finally got the kill the 3rd sword bearer was just standing in that room
staring at the wall. For no reason. Wasn't aggro'ed on us or even moving. Just standing and staring. Wtf Bungie.
I need someone who actually understands networking nonsense to explain it to me but there seem to be different types of "lag." Basic stuff like noticeably delayed hit markers when shooting enemies, but then weird stuff that seems to be on Destiny's end. E.g. Scrota will eat a bunch of rockets, his shield should be down but it doesn't register in your game, or extremely late. However, his immune response will still trigger with the timing as if his shield was down when you expected it. Worst examples I've seen are when his immune shield pops up before he even kneels.
You can't attack unless his shield is actually down on your screen or he will still smack the shit out of you. Last night he shot me in the face and never even kneeled despite the fact his shield was completely gone. I wonder if this is part of how they "fixed" the Ethernet cable cheat, by putting control of the immune response on Bungie's end. Which fucks things up when their info about immune and your info about his shield are out of sync.
Happens regardless of sword runner being host or anything else. It feels completely out of your control and can happen with all green connection bars in the fire team. Can post pics/gifs later maybe, but I need to go through old videos from Nm CE launch and see if this BS ever happened back then. Bottom line: the encounter is an abject failure on every conceivable level.