Got booted for saving the team?

So, game was 4 - 4 in Capture the Flag…

Both teams had the other teams flag, but the other teams carrier was dropped dead right in front of their flag scoring point… So roll on 25 seconds of furious defense, when two enemies are just about to pick up the flag… I shoot them to -Yoink- with a sticky detonator, BUT some idiot who went in trying to beat ONE of the TWO guys to death also got killed. So, roll on I get booted from the game because some -Yoink- apparently thought it was better to have the other team win and he get a CC kill.

This is what has ruined Halo 4 for me. No matter how an accidental betrayal was commited, there is no consideration for what to do about the matter. EVERYONE JUST BLOODY KICKS THE OTHER GUY. Its really annoying, and is quite frankly driving me away from the game due to the immature suckers 343i has wanted to bring onboard with Call of Halo.

/rant

I’m pretty sure they wouldn’t get the option to boot if this was a one off for you.

You must have a poor betrayal history meaning they got the option to boot after just one betrayal.

I got betrayed a couple of times the other night but no option to boot appeared so whoever betrayed me probably doesn’t do it too often.

If this doesn’t apply to you because you hardly ever betray then I don’t know what to say. Maybe the betrayal booting system needs a fix?

The same type of jerks were in Halo 2 and 3 as well. Unfortunately the only possible solution to this is to play with a team that isn’t full of some boot happy randoms.

> If this doesn’t apply to you because you hardly ever betray then I don’t know what to say. Maybe the betrayal booting system needs a fix?

Its the system that needs fixing. Its limited how I can kill one guy and get betrayed, but then there can be this one sucker that kills me every time I pick up the power weapon without me getting to boot him from the game. Same problem was in Reach. In Halo 3 I found the booting system to actually work well, never had any problems back in that game.

> The same type of jerks were in Halo 2 and 3 as well. Unfortunately the only possible solution to this is to play with a team that isn’t full of some boot happy randoms.

I agree, also boot happy randoms were in full swing in reach also, then there are the ones that betray you, you get the option but dont use it thinking “hey its prob accident”, happens 2 more times and you kill them they boot you instantly

> > I agree, also boot happy randoms were in full swing in reach also, then there are the ones that betray you, you get the option but dont use it thinking “hey its prob accident”, happens 2 more times and you kill them they boot you instantly
>
> Those guys are the worst ones.

> In Halo 3 I found the booting system to actually work well, never had any problems back in that game.

> In Halo 3 I found the booting system to actually work well

> In Halo 3…booting system…work well

Haha, good joke!
Oh wait, you were serious.

In all seriousness though, the betrayal system has always had problems in each game. I console myself by being glad it works well sometimes.

The boot system seems even more mangled than before. I got betrayed today on Castle DLC, was blatantly an accident so I let him off. Yet when “that guy” kills me 1397467 times, I don’t get a boot option.

I’ve yet to find a decent betrayal/boot system in any video game.

I rarely get the option to boot in Halo 4, but then again i’m rarely betrayed. It tends to happen more frequently in objective games where players are piled up on an objective/hill/whatever.

Still and all, I sometimes get betrayed and accidentally boot the betrayer. Not intentionally… i’m slamming buttons in a effort to hurry up my respawn and sometimes don’t have time to react to the pop-up message. I feel bad… I’d only boot if the player was truly unsportsmanlike.

Ive watched people get booted in tournaments before. hilarious. And rather than blame the game for getting booted, blame the idiot who booted you. booting is there for a reason, and if you havent booted anyone before, im rather surprised