It is quite easy to accidentally betray someone with these, but two in a row from the same person is a bit suspicious, so two then a boot
Betrayals from anything else is an insta boot. IMO it is pretty much impossible to accidentally betray with anything else, so insta boot. However, in swat it’s two then a boot because sometimes people walk in front of your view and get killed
I hate it period! The other day I shot rocket at the tank and a team mate jumped on as I shot. Then I was booted. Give me a break! I had the most kills! Just not right.
> > Twice regardless of what was used is perfect. Betraying the same person twice is almost impossible to do. Unless it’s intentional.
>
> But with that people would betray others if they knew they had a free betrayal
You system is the same way. Except you get two free splatter betrayals. Two betrayals is good because you can get your revenge on the idiot who betrayed you (on purpose). If they betray you again, they get booted.
> > > Twice regardless of what was used is perfect. Betraying the same person twice is almost impossible to do. Unless it’s intentional.
> >
> > But with that people would betray others if they knew they had a free betrayal
>
> You system is the same way. Except you get two free splatter betrayals. Two betrayals is good because you can get your revenge on the idiot who betrayed you (on purpose). If they betray you again, they get booted.
THis is better than other proposed systems, but I still don’t like it. The biggest flaw with the betrayal system is that it’s sometimes difficult for reach to identify when to allow a boot. Thus, a teamkiller will get a betrayal but you won’t be allowed to boot. This same exact thing will happen with this proposed system, except a Teamkiller will have free betrayals. And teamkillers don’t always go for just one man, so they could be decimating their entire team and not get the boot with the free betrayals, the only way to cure this would be a cap on betrayals per game, but what about people like us who just happen to get a teammate in the blast of a rocket we were toasting a tank with? There would be a bunch of innocents who might get the boot because of this.
Short version (With arguments stacked to show how one part of the system would affect the entire system):
Teamkillers don’t target one man all the time, and Halo sometimes doesn’t let you boot even when it says that you were betrayed.
–The only way to fix this is if we put a cap on betrayals, where a certain number automatically booted you.
—But as you said it’s pretty easy to get splatter betrayals on accident, as well as rocket betrayals. This is also true for grenade betrayals. Because it’s so easy to get them on accident, we would probably eliminate just as many innocents as we would teamkillers.
I say leave the betrayal system as-is. I’ve rarely had trouble with it anyway.
The betrayal system is my enemy, and forever will be. I would say about fifty percent of the time I would be booted for one betrayal. Take for example, heavies on boneyard. We had taken control of the good stuff and I was finally able to keep a banshee and was doing awesome. I had about fifty kills and had the most for the game, until I shot at an enemy. One teammate comes out of nowhere to try and kill the guy, which then got hit by my shot. One betrayal and BOOT.
Give players the option to tag someone as a team killer or betrayer in the AVOID PLAYER selection when leaving a review. Then, when a player betrays a teammate, the boot option is weighted against how many times they have been tagged as a team killer. If they have a bunch of negative reviews for team killing they are auto booted on the first betrayal. If they have a moderate number of bad reviews over a long period of time, then the betrayed is prompted with the option to boot on the second betrayal. If hardly any betrayals at all, the betrayed is prompted on the second betrayal and the third strike is auto boot.
Dunno if this is even possible but it would help differentiate between the accident prone and the -Yoink!-
I got a better one. Whenever you betray someone, 5 kills are subtracted from your score and your service record. If you betray someone a second time in that game, 10 kills are taken away. And so on.
That was already discussed in another post. IT was agreed that this would be bad because halo would just turn into a shooting fest: having a consequence to messing up is what makes you actually pay attention.
It seems to me that people in Reach seem to be a lot more boot-happy than Halo 3 players, for whatever reason. In Halo 3 I almost never got booted for accidental betrayals, but in Reach I get booted almost every time a team mate dies because they decided to assassinate the guy I just stuck.
The betrayal system isn’t perfect. And it never will be, until someone develops mind-reading technology (which will promptly be hacked, anyway) to read players’ intentions.
If you leave it entirely up to the player - that is, if you’re given the option to boot a betrayer whenever you’re betrayed - well, most of the time you can tell when it was accidental and when it was on purpose. Most of the time. But most isn’t all. And there’s always the jerks or idiots who’ll boot you for a genuine accident, because they’re mad. Boo hoo, BOOT.
If you leave it entirely up to the Reach to autoboot them if it thinks they did it on purpose, then you’re relying on the programmers to be able to find distinct definitions for when it’s on purpose and when it’s not, and for them to get it 100% correct. I guarantee that won’t happen. Which means if you go this route, there will be times it’s pretty clearly intentional and the betrayer won’t get booted, and times that it’s pretty clearly an accident and the poor guy will. Oops.
The betrayal system can be tweaked, but it will never be perfect. There WILL be times when you get betrayed and can’t boot the one responsible, and there WILL be times you get booted only because you happened to pull the trigger at just the wrong time. Sorry for the bad news, but you’ll just have to cope.