Skip to content

Using the bot to run a tournament (bot commands)

Nick Bottone edited this page May 17, 2023 · 5 revisions

Setting up the schedule at the beginning of the event

  • /generate_schedule <participant role> <number of rounds>
    • Generates the match schedule on the Google Sheet! Takes in a discord role that should be assigned to everyone that is on the event roster. The number of rounds is the number of matches each player will play. Warning: surrogate matches are untested. Warning: the number of matches should exceed the number of players. This command only needs to be done once, but can be done again to regenerate the schedule. Requires that MatchMaker is present.
  • /build_matches
    • Copies over the schedule to the matches on the Google Sheet! This command only needs to be done once, after the schedule is generated.
  • /make_playoff_channels [optional: number of alliances]
    • Create voice channels for every playoff alliance. This command only needs to be done once, at the beginning of alliance selection. Defaults to 8 alliances.

Running the matches during the event

  • /summon_for_match [optional: Qual or Playoff] [optional: match number]
    • Sets up the voice channels for the next two matches and notifies the players involved via DM. Attempts to find the next unplayed match, or can be overridden with the optional parameter. Does not manage voice channels for playoff matches, but continues DMing players.
  • /save_match_results <field> [optional: Qual or Playoff] [optional: match number]
    • Saves the results of a completed match on a particular field to the Google Sheet! Then proceeds to delete the voice channels for the completed match and setup new voice channels for the next two matches, performing the same actions as /summon_for_match above. Attempts to find the next unplayed match, or can be overridden with the optional parameter. Does not manage voice channels for playoff matches, but continues DMing players and managing scores.

Misc.

  • /ping
    • For testing the bot's latency
  • /reload <command>
    • For reloading a command during development