This happened! Thanks to all the staff and players who contributed to the smooth running of one of the largest Discord tournaments ever.
Stats are available on the database
. In Competitive, Georgetown Day A defeated "Akbar and the Boys" 510 - 260 to win the division, while Detroit Country Day B won Standard over Choate Pembroke by a score of 375 - 330.
CALISTO is now clear, and can be discussed anywhere; if you'd like feedback to go directly to the writing and editing team, feel free to post in the private discussion group, message the discussion Discord
, or get in private contact with any of us.
I'd also like to note here for posterity some of the novel ideas that were implemented in running this tournament, especially as the community is still experimenting with the best format for online tournaments.
Rather than the conventional model of having a separate text channel or text-voice channel pair for each combination of round and room, I elected to have one text channel and one voice channel per room. Each team was assigned roles according to the schedule (e.g. A1, B2, etc.) and permissions for accessing each room were given to and removed from those roles as the tournament progressed. That is, after each round each moderator would remove permissions to access their room from the two teams that just played and would add to each team permissions to view their next room. We had a Discord bot written by Karan to automate this - staff only had to input one command to move each team.
Pros of this approach included that it was just generally cleaner, that it was simpler than the conventional model for teams, who at any time only had access to one room (all rooms teams didn't have access to were invisible to them), that moderators didn't have to move as much, that it more intuitively matches how rooms are used in physical tournaments, that it involved much less manual setup (repetitive and prone to error) of permissions before the tournament, and that it was easier to adapt to a different schedule, if the need was there. There are a few drawbacks - the largest of these is that humans doing things are never going to be 100% reliable, and occasionally mods mistyped commands, which caused (easily fixable but existent) permissions errors. This could possibly be fixed in the future by delegating more to the bot, i.e. storing the schedule in the bot so that moderators would only have to signal for the ends of rounds. Also, there were a few situations where teams were not removed from channels when their permissions were removed, but I believe there are also technological situations to that. Overall, if I were running another large online tournament with a similarly Discord-comfortable set of staffers, I would use this system again.