![]() |
Re: 1vs3 What would you do?
For the 1 team alliance, I think they should definitely play to the best of their ability.
If a robot can't make it to the field due to a mechanical failure then I think both alliances should play their hardest. If the reasoning behind the 1 vs. 3 was that the teams were just late to the field after their timeout rather than being broken and unable to come out, I think the circumstances are different. As the 3-team alliance, I'd be more inclined to discuss, with the other alliance, the possibility of creating a 0-0 tie situation in order to have a more evenly matched elimination round. To me, it would be less satisfying to win the 2/3 when one of the alliances lost a match with only one robot on the field. |
Re: 1vs3 What would you do?
Quote:
A related anecdote from FTC, where the matches are two on two. An alliance had a disqualified robot, so the other robot was going to play 1 on 2. The single robot then got hung up in an almost impossible way on a game piece during autonomous, which meant that the entire teleop period was going to be two on none. I believe the two-working-robot alliance were all rookies. For the first part of the match the two bots worked on scoring while quite a few people were yelling "knock them off," and the poor stranded robot tried to break free. Eventually, one of the 2-robot alliance nudged the single robot off the game piece and the crowd cheered for them. I think the drivers learned something about what GP means in FIRST. It was a great little moment (even if the single robot was my son's team...). |
Re: 1vs3 What would you do?
Quote:
2) hit the kill button and sit there the whole match... its not fair to steal the show or fight with unfavorable odds.. not to mention that it shows some serious gp to possibly lose a match because the other alliance is pretty much handicapped |
Re: 1vs3 What would you do?
In either situation... use the EMP. Definately.
|
| All times are GMT -5. The time now is 01:08. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi