FIRST-Tech-Challenge / FIRST-Tech-Challenge/scorekeeper
Better handling of match replays
- Dominant language
- No language data
- Stars
- 110
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
There are situations as laid out in T301 that can cause a match to be replayed. We had this happen at an event this last weekend and found that the score system does not handle this edge case all that well. There are two different edge cases here neither of which is currently handled.
_Case 1: match not committed_
In our case the match was aborted before the end due to field damage. Because the match partially played before aborted the decision was made to replay it after the last qualification match. However since that match was never committed or fully played for the rest of the day clicking "load next match" would try to load the skipped match, and the score keeper had to manually click play on each match.
_Case 2: match committed_
There is another case where a match is played and score are committed but then the decision is made to replay it. This seems likely to happen since some of the requirements to replay are "match affecting" and the team must request it. In the case that the match is decided to be replayed it will typically be replayed after the last qualification match, however the original score will show up in the score system all day effecting rankings and potentially confusing teams and spectators.
**Describe the solution you'd like**
A way to mark a match as "to be replayed" in the score system. This should clear out the score as if it hadn't been played (without deleting score history), and it should allow it to be skipped over in the score system so "load next match" doesn't keep trying to load it.
**Describe alternatives you've considered**
You can just manually select which match to play next for Case 1, and for Case 2 we just try to have the game announcers and emcee communicate what is going on to the audience and teams.
**Additional context**
N/A
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.