(Or, make this a toggleable option for any given tournament. Tho that would be harder)
The queue is nice to keep suspense, and to giveusers a feel for when their matches might be played.
However, for tournaments, those factors aren't so useful. Also, the queue can expose winners of the tournament, especially the final tournament, as watchers can count the number of matches to infer the number of rounds, and infer whether the low seed has reset the bracket (forcing an extra match) or if the high seed won in the first match
Before you submit this issue...
If you are not a Battlecode dev, please keep the triage label.
If you are a Battlecode dev, the following would be great, but optional.
[ ] If you know the priority, assign a label for it. (the red labels)
[ ] If you know the module(s), assign a label (or labels) for it. (the green labels)
[ ] If you know the type(s), assign a label (or labels) for it. (the yellow labels)
[ ] If you know this is a simple issue or fix, assign good first issue. (the blue label)
[ ] If you did not fill any of the above, please keep the triage label.
Description
Please include a description of the issue below, including steps to reproduce.
n8kim1
commented
3 months ago
(Or, make this a toggleable option for any given tournament. Tho that would be harder)
The queue is nice to keep suspense, and to giveusers a feel for when their matches might be played. However, for tournaments, those factors aren't so useful. Also, the queue can expose winners of the tournament, especially the final tournament, as watchers can count the number of matches to infer the number of rounds, and infer whether the low seed has reset the bracket (forcing an extra match) or if the high seed won in the first match
Before you submit this issue...
If you are not a Battlecode dev, please keep the
triagelabel.If you are a Battlecode dev, the following would be great, but optional.
good first issue. (the blue label)triagelabel.Description
Please include a description of the issue below, including steps to reproduce.