Skip to main content

/tournament create

Admin Command

This command requires administrator permissions.

(BETA) Create a new tournament and shows signup buttons.

Usage​

/tournament create [maximum_participants] (tournament_type) (auto_start_on_fill) (auto_create_matches) (auto_create_new_tournament) (team_size) (name) (url) (details) (forfeit_timer_sec)

Arguments​

  • maximum_participants: (Required) Maximum number of teams that can register.
  • tournament_type: (Optional) (Default: Single Elimination) Tournament type.
        Options: single_elimination, double_elimination, round_robin, swiss
  • auto_start_on_fill: (Optional) (Default: True) Automatically start the tournament when the participant capacity is hit.
  • auto_create_matches: (Optional) (Default: True) If the bot should automatically create matches when ready.
  • auto_create_new_tournament: (Optional) (Default: On Completion) Automatically create a new tournament when this one starts/ends?.
        Options: On Start, On Completion, Never
  • team_size: (Optional) Number of players on each team.
  • name: (Optional) The tournament name, also the name of the queue/stats storage for determining seeding.
  • url: (Optional) Challonge tournament URL, or omit to auto generate.
  • details: (Optional) Any extra details to show in the queue message.
  • forfeit_timer_sec: (Optional) How longer players have to join the match (in seconds) before forfeiting.

Details​

Creates a fully configurable tournament, posts a persistent signup message with interactive Join/Leave buttons, and optionally generates or links to a Challonge URL for bracket viewing. Internally the bot records the tournament settings with its scheduler and matchmaker, enforces participant limits and team sizes, manages forfeit timers, handles automatic behaviors (start on fill, auto-create matches or successor tournaments), applies payout/entry options and third-place handling, and restricts execution to administrators.

Required Permissions​

Permission Required

This command requires either:

  • A configured NeatQueue Staff Role
  • Manage Channels permission