ROFLIB_ wrote:QUOTE (IB_ @ Sep 6 2007, 06:55 PM) Yes. Highly doubtful you would score 22 goals in the second half /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
Mutiny and R.O.C.
-
rojomojo915
- Posts: 448
- Joined: Tue Jun 06, 2006 7:00 am
- Location: Long Island, NY
-
CraftyCelt
- Posts: 440
- Joined: Tue Aug 22, 2006 1:26 am
- Location: Eire
Once again IB is correct...IB_ wrote:QUOTE (IB_ @ Sep 6 2007, 11:55 PM) Yes. Highly doubtful you would score 22 goals in the second half /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
TheVoid37 wrote:QUOTE (TheVoid37 @ Aug 6 2008, 02:47 AM) We literally saw No humans in many of the spots we were in.
European football or American football? American football you'd have a chance of coming back, as (For some odd reason) a touchdown is worth 7 points and a Field Goal (Which I've never been sure exactly what it is) is worth 3 points... so 3 touch downs and a field goal, not extremely difficult, where Euro Football would be.IB_ wrote:QUOTE (IB_ @ Sep 6 2007, 06:55 PM) Yes. Highly doubtful you would score 22 goals in the second half /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />



-
Grim_Reaper_4u
- Posts: 356
- Joined: Wed Jul 30, 2003 7:00 am
- Location: Netherlands
You might wanna reconsider/explain that lame response BV esp. after reading Frags last post. Since when is booting a pilot that has done nothing wrong (after he lost command), didn't argue or whine, didn't basesit or generally $#@! up, a valid reason to boot? All the arguments which Frag puts forward point in the direction of a retaliatory boot and IMHO are against ROC#10 both in letter and in spirit.BlackViper wrote:QUOTE (BlackViper @ Sep 6 2007, 07:27 PM) I am BV and approve Frag's post.
I don't give a @#(! about what Frag did and I could care less if you slap his wrist but i do think you should make it clear that booting a commander after a succesful mutiny is not $#@!ing allowed unless he becomes a pain in the ass. /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />
Grim_Reaper_4u wrote:QUOTE (Grim_Reaper_4u @ Sep 7 2007, 10:50 AM) You might wanna reconsider/explain that lame response BV esp. after reading Frags last post. Since when is booting a pilot that has done nothing wrong (after he lost command), didn't argue or whine, didn't basesit or generally $#@! up, a valid reason to boot? All the arguments which Frag puts forward point in the direction of a retaliatory boot and IMHO are against ROC#10 both in letter and in spirit.
I don't give a @#(! about what Frag did and I could care less if you slap his wrist but i do think you should make it clear that booting a commander after a succesful mutiny is not $#@!ing allowed unless he becomes a pain in the ass. /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />
Meh. Let's not nanny sit the comm's. I mean, come on, I think any comm should have the ability to boot anyone on his/her team. (With the exclusion of numbers -- I do think that's a wise rule). The 'retalitory' side of the PoC is mostly a feel good. It sounds next to impossible to enforce -- a comm can always find a reason to boot someone if they have their heart set on it without making it look retalitory. And this is as it should be, IMHO. Power to the people.. er.. comms!
/still a noob, feel free to discard as a dumb n00b post

-
BlackViper
- Posts: 6993
- Joined: Thu Aug 07, 2003 7:00 am
- Location: Green Bay, WI
Clarifications:
Any commander may boot any player from his team* Period. In simple english, the commander does NOT need a so called "valid reason". It has been that way for a long time.
*(The exception is for players with a rank 4 or below without warning or giving an opportunity to explain to them what you want done.)
A commander who shows a history of retalitory booting, B.O.S. lists, excessive booting, etc. will get hammered.
---------------------------------------------------------------------------------------------------------------------------------------------------
Now, before the @#(!storm starts. Stop and think for a second. We have had huge uproars in the past over "regulation" of commanders. The community DEMANDED that commanders be given leeway. This is why I keep a very loose rein on commanders now. I allow them alot of leeway. And I will continue. You can not have it both ways. I am not going to regulate commanders to death.
I might not agree 100% with Frag's decision, but I will back him as the commander of the team at that moment. I do not see it as a retalitory boot. He made a command decision.
I would assume by now most players keep a "do not fly for" list just like I do.
Any commander may boot any player from his team* Period. In simple english, the commander does NOT need a so called "valid reason". It has been that way for a long time.
*(The exception is for players with a rank 4 or below without warning or giving an opportunity to explain to them what you want done.)
A commander who shows a history of retalitory booting, B.O.S. lists, excessive booting, etc. will get hammered.
---------------------------------------------------------------------------------------------------------------------------------------------------
Now, before the @#(!storm starts. Stop and think for a second. We have had huge uproars in the past over "regulation" of commanders. The community DEMANDED that commanders be given leeway. This is why I keep a very loose rein on commanders now. I allow them alot of leeway. And I will continue. You can not have it both ways. I am not going to regulate commanders to death.
I might not agree 100% with Frag's decision, but I will back him as the commander of the team at that moment. I do not see it as a retalitory boot. He made a command decision.
I would assume by now most players keep a "do not fly for" list just like I do.
Last edited by BlackViper on Fri Sep 07, 2007 7:33 pm, edited 1 time in total.
Always in the Shadows...


