RockTheVeto

Can someone confirm this? Just got back on reach, and have "quit" 3(?) games because of this weird glitch/bug. Preferably someone with good int. connection, because I can't trust my Xbox with this bug, it sucks connecting to my router. But, every time the glitch has occurred, I did exactly what the title implies. I unmute-ban(?) someone, because I really do wonder if most people deserve it... Then check their record to see their game history. If they end up being a good teammate, I submit a positive review... But recently, I get d/c immediately after doing this! Help? Just happy I don't quit often...

He's not going to die in vain, He's going to save halo, save you, The problem here is that you go in to save chief, and then he dies, and then comes the kicking and screaming. that's not the bad thing. The part after you escape, you'll feel like *crud* because he saved you and stuff.

The one thing I want to happen in halo 4 -or up- is I want Master Chief to die. Now, I'm not doing this to be a troll here, there is a legitimate reason he needs to die. Halo: CE. Master Chief was the wreaking machine that annihilated the covenant. But when faced with the flood, players felt helpless in the first encounter. They saw how Keyes and his squad were eaten alive. That is not the reason he needs to die. Chief doesn't need to die because he saw the flood and we need to make it fresh. He needs to die to accomplish one thing: To put our backs against the wall. Imagine a new character -we don't know him at all- was assigned to go find the chief. And we have this character reach the chief, almost make it to him and -BLAM!- The chief is dead. Now all hope for humanity is lost, and you would have to fight your way out. Not only does it make the game a lot more scary, but that puts a ton of pressure on the player as they have to fill in his shoes. This is backs against the wall. This is why the chief has to die.