Since I didn’t spend all season updating giant excel books, my mind is now free to suggest insane ideas for events. So, here is the newest insanity: armageddon playoff matches.
I’ve been seeing comments about playoff ties and how problematic they are. When teams score the same number of points, there are 3 options currently:
- Declare the match a tie and continue on with the tournament (currently used in quals, but not possible with current playoff structure)
- Replay the match (currently used for finals matches, but causes huge delays in certain years if applied to entire playoff bracket, see 2017)
- Use tiebreaker criteria (currently used for non-finals playoff matches, could be used in all playoff matches but very commonly ends up feeling bad/arbitrary for the winners, losers, and spectators)
Instead of any of these, I’m suggesting the use of armageddon matches in the finals. The terminology comes from armageddon chess, in which the player with the black pieces “wins” the match if there is a draw, but as compensation, the player with the white pieces receives more time on the clock in order to force a straight win.
For FRC, here is how I would propose implementing armageddon matches:
When teams submit their lineup for playoffs, they can also submit a “time bid” of how much time they would be willing to give up in order to have draw odds (that is, advance on a tied score). The alliance with the higher bid will receive draw odds for the match. If they do not submit a bid, their time bid is defaulted to 0.50 seconds. Time bids must be between 0 and 99.99 seconds and will be entered up to the first 2 decimal places. If the time bids for both alliances are even to the first two decimal places, the red alliance receives the draw odds as well as the associated time loss.
During the match, after the autonomous period, the alliance with the lower bid will be enabled immediately (as all alliances currently are). The FMS will then wait the amount of time specified by the winning (higher) time bid before enabling the other alliance. I think the start of teleop is the best time to remove time. Removing time from auto will interfere with auto routines, removing time in the middle of teleop will effectively incapacitate robots for far longer than the “bid” time, and removing time at the end of teleop will knock out robots during the most exciting and most critical moments of the match (while also taking away from a potentially finite period of time for endgame tasks).
For audience clarity, there are a few approaches that could be used to show what is happening:
- The alliance with draw odds receives 0.5 points upon winning the bid. This avoids any ambiguity about ties, but will look pretty strange to the audience and make data processing/display more difficult. It is viable but I am partial to other options.
- In game design, make all game scoring opportunities (including penalties) a multiple of 2, then provide the alliance with draw odds a 1 point bonus on winning the bid. This is functionally the same as option 1, but gets rid of annoying half points at the expense of inflated total scores. I prefer this to option 1.
- Instead of messing with the score, just put an indication on the final scoreboard that says “red advances on tie score” or “blue advances on tie score”. This could also be added to the in-game scoreboard but I’d be worried about clutter. Someone with better graphic design skills than me might be able to figure something out. I like this about as much as option 2.
I think a bidding process would add a fun little strategy component to the game and will make advancement feel more fair as teams will be responsible for their own destiny regarding ties. Don’t want to deal with any time lost? You can bid 0.00 seconds and will be active the whole match. Hate losing on a tied score? You can bid 30 seconds to make sure it doesn’t happen. The bidding process will guarantee both teams get what they want, and not one single person on any team will ever feel any heartache about losing due to a tied score ever again
Fun poll, how spicy would this rule change be?
0 voters