Please remove the ability boot players for betraying in Griffball. Yes this gets exploited in Reach, but accidental betrayals happen frequently in Griffball.
I would have thought this would have been done by now.
343 is a bit slow. Like when they didn’t even have Griffbal when Halo 5 came out.
If it does get removed, I’ll be waiting, here on Waypoint, for an influx of people complaining about constantly getting teamkilled by the same -Yoink-hole teammate.
If that happens, good luck coming back and complaining that you’re getting killed by the same teammate over and over and over again.
How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
> 2535428987050649;6:
> How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
> 2533274878104604;7:
> > 2535428987050649;6:
> > How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
>
> The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
Good points, but I think accidental teamkills (and booting as a result) happens more often in H5 than ball carriers’ refusal to score. Either way, it’s a moot point, as 343 doesn’t seem interested in doing anything more with H5 than switching out gametypes every weekend.
> 2535428987050649;8:
> > 2533274878104604;7:
> > > 2535428987050649;6:
> > > How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
> >
> > The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
>
> Good points, but I think accidental teamkills (and booting as a result) happens more often in H5 than ball carriers’ refusal to score. Either way, it’s a moot point, as 343 doesn’t seem interested in doing anything more with H5 than switching out gametypes every weekend.
boots don’t happen from the first betrayal though. if you manage to kill the same teammate twice or more that is your fault. Go play some Reach Grifball and then you’ll understand why booting is an option in Halo 5
> 2533274878104604;9:
> > 2535428987050649;8:
> > > 2533274878104604;7:
> > > > 2535428987050649;6:
> > > > How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
> > >
> > > The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
> >
> > Good points, but I think accidental teamkills (and booting as a result) happens more often in H5 than ball carriers’ refusal to score. Either way, it’s a moot point, as 343 doesn’t seem interested in doing anything more with H5 than switching out gametypes every weekend.
>
> boots don’t happen from the first betrayal though. if you manage to kill the same teammate twice or more that is your fault. Go play some Reach Grifball and then you’ll understand why booting is an option in Halo 5
You say “manage to kill” as if I’m trying to murder my teammates, which I’m not. Besides, H5 moves at about four times the speed of Reach. Things happen faster. A teammate can step between my hammer and an enemy in the blink of an eye. And that teammate can think that I killed him intentionally, which, chances are, I didn’t.
Also, it should be noted that I’m arguing against the presence of friendly fire in Grifball, not against booting. If there is friendly fire, there should also be booting, to weed out the teamkilling $#%^tards.
> 2535428987050649;10:
> > 2533274878104604;9:
> > > 2535428987050649;8:
> > > > 2533274878104604;7:
> > > > > 2535428987050649;6:
> > > > > How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
> > > >
> > > > The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
> > >
> > > Good points, but I think accidental teamkills (and booting as a result) happens more often in H5 than ball carriers’ refusal to score. Either way, it’s a moot point, as 343 doesn’t seem interested in doing anything more with H5 than switching out gametypes every weekend.
> >
> > boots don’t happen from the first betrayal though. if you manage to kill the same teammate twice or more that is your fault. Go play some Reach Grifball and then you’ll understand why booting is an option in Halo 5
>
> You say “manage to kill” as if I’m trying to murder my teammates, which I’m not. Besides, H5 moves at about four times the speed of Reach. Things happen faster. A teammate can step between my hammer and an enemy in the blink of an eye. And that teammate can think that I killed him intentionally, which, chances are, I didn’t.
>
> Also, it should be noted that I’m arguing against the presence of friendly fire in Grifball, not against booting. If there is friendly fire, there should also be booting, to weed out the teamkilling $#%^tards.
Friendly fire is a staple part of the gametype since Halo 3 and it will continue to be. if someone gets salty over an accidental team kill it’s their fault because obviously they weren’t raised to forgive accidents.
> 2533274878104604;11:
> > 2535428987050649;10:
> > > 2533274878104604;9:
> > > > 2535428987050649;8:
> > > > > 2533274878104604;7:
> > > > > > 2535428987050649;6:
> > > > > > How about this: Turn off Friendly Fire for Grifball. Riftball (from Action Sack) doesn’t allow teamkilling, and - who would’ve guessed? - the game still functions fine. Honestly, I have no idea why 343 hasn’t done this already. But then, common sense doesn’t always seem to come naturally to them.
> > > > >
> > > > > The reason betraying is left in was because the ball carrier (Grif) can be teamkilled if they are trying to exploit the game by refusing to score the ball. Also it’s just in there because RoosterTeeth wanted to put betraying in the gametype because of Red Vs Blue since Sarge liked to always hurt Grif. Do remember that 343 did not create Grifball. Bungie asked RoosterTeeth to make a gametype back in Halo 3 and it was Grifball.
> > > >
> > > > Good points, but I think accidental teamkills (and booting as a result) happens more often in H5 than ball carriers’ refusal to score. Either way, it’s a moot point, as 343 doesn’t seem interested in doing anything more with H5 than switching out gametypes every weekend.
> > >
> > > boots don’t happen from the first betrayal though. if you manage to kill the same teammate twice or more that is your fault. Go play some Reach Grifball and then you’ll understand why booting is an option in Halo 5
> >
> > You say “manage to kill” as if I’m trying to murder my teammates, which I’m not. Besides, H5 moves at about four times the speed of Reach. Things happen faster. A teammate can step between my hammer and an enemy in the blink of an eye. And that teammate can think that I killed him intentionally, which, chances are, I didn’t.
> >
> > Also, it should be noted that I’m arguing against the presence of friendly fire in Grifball, not against booting. If there is friendly fire, there should also be booting, to weed out the teamkilling $#%^tards.
>
> Friendly fire is a staple part of the gametype since Halo 3 and it will continue to be. if someone gets salty over an accidental team kill it’s their fault because obviously they weren’t raised to forgive accidents.
Whatever. Like I said, 343 isn’t going to take any action on the issue at this point.
See you on the Grifball court, bro.
There’s an active thread on Grifball in the MM section you guys can use.
Removing FF from Grifball will irrevocably break the gametype. The betrayal boot threshhold is higher in Grifball than other playlists. If you’re routinely getting booted, you need to learn to watch your radar and not swing when there’s lots of friendly dots near you. Learn to not bunch up with your teammates.