Hey every body, got a question for those who have played the new flood gametype. As I’m sure everyone who’s played Reach’s infection game type already knows how utterly infuriating it is when you kill a zombie yet they manage to kill you even as you see their lifeless husk drop to the ground. For instance: I am a survivor and a zombie is coming at me. I fire my shotgun killing said zombie, but almost directly after the zombie has been killed, I am also killed. Me and my friends called this ‘Reaching’ or being ‘Reached’ as it only happened in Reach. It even happens when you get a bulltrue. Which makes no sense at all.
So basically, does this still happen in Halo 4’s food game type? Thanks for any and all answers and sorry if this has been discussed previously 
> Hey every body, got a question for those who have played the new flood gametype. As I’m sure everyone who’s played Reach’s infection game type already knows how utterly infuriating it is when you kill a zombie yet they manage to kill you even as you see their lifeless husk drop to the ground. For instance: I am a survivor and a zombie is coming at me. I fire my shotgun killing said zombie, but almost directly after the zombie has been killed, I am also killed. Me and my friends called this ‘Reaching’ or being ‘Reached’ as it only happened in Reach. It even happens when you get a bulltrue. Which makes no sense at all.
> So basically, does this still happen in Halo 4’s food game type? Thanks for any and all answers and sorry if this has been discussed previously
Frustrating, I know, but it is an artifact of latency. It will depends on how good your connection is, and if the netcode has been upgraded significantly or not.
I imagine that many of the annoying bugs from reach’s infection will have been dealt with or at least they’ve done as much as they can. I always used to imagine it was the force of the dead zombies body smacking into me that killed me.
Unfortunately thats not so much of a gameplay problem as a lag problem, my only tip to you is that if you get into a particularly laggy game, and this happens, next round try shooting slightly earlier than you usually would to compensate, I find this works best, even if it seems risky.
The Net-Code was updated for Halo 4, so it shouldnt be a issue now, but like Blibinator mentioned its a simple mistake caused by lag. They actually do kill you as well due to the Sword Lunge most of the time soon as you shoot and kill them.
Sword Lunge is severely downgraded now, and Flood use a more refined and tuned version of the Sword/Their Claw Arm now, so I am assuming its all been fixed.
I have one of the best connections available and minimal ping yet I was still getting betrayals for killing zombies while I was human. I couldn’t even finish half of the infection games I played because I keep getting booted.
I’ve also played plenty of infection on H3 and that NEVER happened to me once. I stopped playing Reach just because of that. Whoever designed that part of the game for Reach is a moron.
I figured it was something to do with the NAT type, but I have a pretty -Yoink!- good connection. It isn’t always lag I can tell you that though. But if Halo 4 has an upgraded NAT code or type or whatever then that makes me very happy 
> Unfortunately thats not so much of a gameplay problem as a lag problem, my only tip to you is that if you get into a particularly laggy game, and this happens, next round try shooting slightly earlier than you usually would to compensate, I find this works best, even if it seems risky.
i believe this to be false, hit scans determines weather you got the kill or not off of whats on your screen not where the enemy player is at. not 100% sure if i’m right or wrong i can’t remember which weapons were hit scan.
with that being said you and the enemy player both can have a good connection but still kill each other because of this feature, seeing how you can kill the player before he kills you, but of his screen he is still not dead so he hasa split second of time left to kill you.