|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Please cite the rule?
|
|
#2
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
It's a clever theory, but it's in a somewhat unwritten rule of FIRST. It is specifically countered, but not by a "rule," more of a guide line.
Quote:
|
|
#3
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Technically, there isn't a rule. But yeah, you can't do that.
|
|
#4
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
The competition manual does leave some things to common sense. For example you cannot pick a team that is not at the event, but there is no actual rule against it.
Another way to look at it: Once you have picked, you are picked by the team you picked. Last edited by jspatz1 : 04-04-2012 at 18:03. |
|
#5
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Quote:
Quote:
Quote:
|
|
#6
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Number 8 picks numbers 1 and 2....
lol no |
|
#7
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
More like number three picks numbers one and two. Definitely not a "lol."
|
|
#8
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Ah, but it doesn't SAY that they have to be at the same competition. That's just a common perception.
|
|
#9
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Quote:
As for whether or not a ref would have to allow it: no, they wouldn't, because they're authorized to use their judgement when making calls. There is a small, valid point here that the rule could be clarified to explicitly state outright that teams already on an alliance are not available for selection, but that's nearly as silly as stating that teams not competing at that regional (or teams that either do not yet or no longer exist) are not available for selection either. |
|
#10
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
I'd say "silly" is the operative word here.
|
|
#11
|
|||
|
|||
|
Re: Picking an Alliance Captain after they have already picked
You're right - there is no rule against it. At the same time, it's obvious by the rest of the procedure that that is not supposed to happen. Still, it couldn't hurt for FIRST to clarify the rules for next year...
|
|
#12
|
|||||
|
|||||
|
Re: Picking an Alliance Captain after they have already picked
Quote:
Wetzel |
|
#13
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Quote:
![]() |
|
#14
|
||||
|
||||
|
Re: Picking an Alliance Captain after they have already picked
Off topic of the OP but we learned that as well in 2010 in Oklahoma. The only match we lost, and were one away from being undefeated in Qualifications, was our Match 8, where we forgot to turn Trigger on...
|
|
#15
|
|||||
|
|||||
|
Re: Picking an Alliance Captain after they have already picked
I recall this happening one year in during the second round, a team tried to select another seed below them (when it wasn't a serpentine selection). I think the response was something along the lines of "That team is the 8th seed and cannot be selected." The team trying to select them did it by mistake since they dropped into that slot.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|