![]() |
Picking an Alliance Captain after they have already picked
Is an Alliance Captain allowed to be selected by a higher seeded Alliance Captain if they have already selected teams for their alliance?
Example: Alliance Captain #8 selects their first choice and second choice and we are proceeding back up to Alliance Captain #1 in the selection process. Alliance Captain #8 had not previously turned down an alliance invitation. Could Alliance Captain #N select Alliance Captain #8 as their second choice alliance partner? |
Re: Picking an Alliance Captain after they have already picked
Once you have an alliance partner, you can't be selected. period
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
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:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
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. |
Re: Picking an Alliance Captain after they have already picked
Quote:
Quote:
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Number 8 picks numbers 1 and 2....
lol no |
Re: Picking an Alliance Captain after they have already picked
Quote:
|
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. |
Re: Picking an Alliance Captain after they have already picked
This would allow for a situation like: 1 picks 2 and accepts, then all the selcetions go through and it gets back to 1 and they pick alliance captain 8. Then what happens? Does captain 8 wave goodbye to the 2 teams they just picked? No. Everyone looks at them like he just said 2+2=22. Why? Because you cant pick a team that is already with another team.
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
The FIRST thing to happen would be an immediate call to HQ, or whoever representing HQ is available, for clarification. Bill Miller, any GDC members onsite, whoever the ref and regional director need to get ahold of. This is because it's a situation that is not in the rules. (The fourth thing to happen would be that it would be in the rules in following years.) The second thing to happen would be the announcement of the GDC ruling. The third thing to happen would be either the picking team picking again, which is more likely, or a ton of confusion as the entire picking would need to be redone. Let's face it, if #1 picks #6 as the final pick, the #6 alliance has to have another team, or quite possibly the #7 and #8 have to move up, leaving the #9 team to move up and now they have to get picks... And the final thing to happen is memory. Your team, if they insisted on challenging this during alliance selection, would be remembered for years as "that team that caused the big mess in the Magnolia Regional alliance selection" if it was successfully challenged. (And if it was unsuccessful? Everyone knows where the rule explicitly disallowing picking alliance captains who have already picked comes from for years to come.) Of course, this is an easy tactic to defeat: All the lower-seeded captain has to do is say "We decline. As you can see, we already have an alliance." and that's that. That's been the de facto reason for years when someone who's been picked is picked again; it just hasn't been stated as such. |
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
Wetzel |
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...
|
Re: Picking an Alliance Captain after they have already picked
Quote:
Wetzel |
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
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.
|
Re: Picking an Alliance Captain after they have already picked
Common sense would also dictate you pick from the teams on the "Available" portion of the alliance selection screen. Once the #8 seed has started their alliance, they are no longer on that portion of the screen.
|
Re: Picking an Alliance Captain after they have already picked
Quote:
|
Re: Picking an Alliance Captain after they have already picked
Too bad you didn't post this a couple weeks ago. The GDC could have sent out an update saying it was legal and won the award for most concern caused by an April Fools Day prank.
|
Re: Picking an Alliance Captain after they have already picked
sigh. Patently absurd premise.
|
| All times are GMT -5. The time now is 14:30. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi