Free Allegiance Forums

NO NO $#@!ing NO.

EVERYONE WHO POSTED ABOVE ME BESIDES FREEBEER IS A GIANT $#@!.

Alright listen up *#$@bags,

IF the game starts and you mutiny in the first five minutes, it SHOULD be a bootable offence. IF you didn't want the guy to command, WHY THE $#@! DIDN'T YOU TAKE COMMAND THEN.

Instead of mutinying and resigning, ruining the game for this person, YOU take command.

Okay so the guy won't hand over command, and there's no @Alleg. FINE but this was not EXPLICITLY MENTIONED IN THE $#@!ING THREAD BY THE $#@!ING OP.

If you're going to join the $#@!ing team for the sole purpose of mutiny and then resigning, DON'T BOTHER TO $#@!ING PLAY.

If I EVER see this I will go straight to $#@!ing BV, TE or WHOEVER THE $#@! and get your stupid asses banned. Hostaging is not acceptable and I agree with mutiny in this situation, but booting them afterwards is even less sporting. HOWEVER if they're willing to give it up, or THERE iS A FIFTEEN MINUTE LULL IN BETWEEN GAMES WHERE SOMEONE IS LOOING FOR COMMANDER, TAKE $#@!ING COMMAND AS IF YOU ACTUALLY HAD A SET OF TESTICLES.

Don't $#@!ing join and mutiny after twenty minutes waiting for a commander if you don't want this guy commanding. THIS IS WHAT PRIVATEER WAS EXPLICITLY SAYING.

And it should be $#@!ing bannable.

Don't $#@!ing get me mad by acting like tossers. I'm no $#@!ing carebear but the above stated behaviour is simply unacceptable, especially by people who have been here just as long or longer than I have and who should know better. The NEXT time this happens bring it STRAIGHT to the admins or @Alleg because I personally know certain @Alleg who will issue bans for this behaviour.

Yes, I admit I have done it before too but not straight as the game starts. 20-30 minutes in when it is obvious the commander is damaging the team. But five minutes in? EVEN IF the commander has bought another garrison or some other equally retarded @#(!, it was YOUR fault you didn't take command. Guess what $#@!ing happens when a (7) gets command after waiting 15mins for SOMEONE MUCH MORE QUALIFIED? GUESS WHAT THE $#@! HAPPENS.

$#@!ing leave and make your own server like FreeBeer said. If THAT many in NOAT could preplan a mutiny there is CERTAINLY enough to go have your own game, or NOT LETTING THE GUY COMMAND IN THE FIRST PLACE AFTER WAITING FIFTEEN MINUTES.

I have repeated it umpteen times so I $#@!ing hope it gets through to your idiotic $#@!ing brains.

Yeah, he's got a point there.

Reading the OP is healthy yo.

This is the reason that the mutiny feature was implemented.

If the community doesn't want you commanding on the main server, you shouldn't be commanding on the main server. Period.

CronoDroid wrote:QUOTE (CronoDroid @ Oct 28 2008, 02:17 AM) Instead of mutinying and resigning, ruining the game for this person, YOU take command.

A lovely sentiment but it's not possible to accomplish if the idiot in the command seat won't relinquish it. I've asked for command on more than one occaision not because I wanted to but because I knew the inexperienced player in the command chair would make the game suck. On most of those cases, the inexperienced player refused to give it up.

CronoDroid wrote:QUOTE (CronoDroid @ Oct 28 2008, 02:17 AM) Okay so the guy won't hand over command, and there's no @Alleg. FINE but this was not EXPLICITLY MENTIONED IN THE $#@!ING THREAD BY THE $#@!ING OP.

It wasn't mentioned, but considering the reality of gameplay that I have seen, it's the most likely scenario. Its a lot harder to organize a mutiny than it is to ask somebody to give up the comm chair.

Also, I recommend less caffine.

Oh, and privateer, helo has nothing to do with it, nor does privilege. It is about merit and skill. If you want to command, become a good pilot and nobody will object to you commanding.

we added #mutiny to make this easier to do, and considering that Allegskill is coming in TwoWeeks™ we should not be removing the feature that really shut up all the complainers

EDIT: I am so going to mutiny privateerm

How can a single pilot be made responsible for a mutiny? It takes the majority of the team to hit "yes" to make it pass. So when it happens, the majority of the team wants the mutiny, because they expect to have more fun with someone else commandig.

Crono must be the only person in the world to have never seen a clueless voob refuse to give up command to anyone else during prime time and there being none of the uber qualified @Alleg staff around to deal with the situation.

Well, to be fair that's not what Crono is talking about. He's talking about guys like Privateer, Yiggz, and so on, who get mutinied and booted 5 minutes into the game because they took up command when nobody else wanted to, even though explicitly saying they will give command to someone more experienced. That's just rather distasteful. IIRC Tontow, KingArthur(Not the uber one), and so on stopped playing because of this. I mean it's clear they weren't the most popular commanders, but they were learning, and that was okay with me. If their commanding is so painful, then doesn't someone take command from them before the game starts? People just enjoy mutinying and booting someone in hopes of making them stop playing.

Oh and there already is a rule for this. Pook's rule for dummies Number 1. Everyone gets to play. Anyone who does the mutiny/boot combination is already violating that, and iirc, the punishment for such is most severe.

In the terms of suckvoob mcgee hostaging, off with their head. If there's no @alleg present of course.

KlngArthur btw

Booting the mutinied guy is (often) asshattery and should be punished. Other than that, this is often necessary.

If there are proper teams and the settings haven't been set to stupid, just mutiny and play on... and let the mutinied person play too. He/she isn't holding the server / team hostage anymore afterall.