Getting Started

This page is the short path for community operators. Connect Discord, confirm which organization owns the server, then create the first ranked queue from the organization dashboard.

Four actions to get your first queue live

1. 1

   Install the bot

   Sign in to GotNext, connect a Discord server you can manage, and authorize the bot permissions. GotNext creates or reuses an organization for the server.

2. 2

   Create a queue

   Choose the game, team size, and Discord channel in the web setup flow.

3. 3

   Open registration

   Players register once, then join queues directly from Discord.

4. 4

   Report results

   A moderator uses Report Result to update ratings, result cards, and leaderboards.

Step 1: Add the bot and confirm the organization

The install flow starts from the GotNext bot page. Sign in with your GotNext account, connect Discord, and select a server where you have the Discord Manage Server permission. Authorize the requested bot permissions to continue.

Every connected server must belong to an organization. GotNext reuses the server's current organization, uses your only eligible organization, or creates an organization from the Discord server name when one is needed. If you manage more than one eligible organization, the callback asks you to choose one. The server dashboard, staff access, competitions, XP, achievements, and subscription are grouped under that organization.

To use an existing organization, your organization role must include Manage Discord. Creating a new organization during setup gives you the access needed to continue.

Required permissions:

• Send messages and embeds
• Attach files for generated match and result cards
• Manage roles for rank tier assignment
• Manage nicknames for ELO display
• Manage channels and permissions for dedicated team-match channels
• Connect for optional team voice rooms
• Move Members only when automatic voice moving is enabled
• Read message history
• Use slash commands

Step 2: Create your first queue

Open Ranked Queues in your organization dashboard, select the connected server, then choose Create queue. The guided setup asks for the game, team size, match mode, and Discord channel. If the channel does not exist yet, create it without leaving setup.

Review the defaults, create the queue, then use the queue page to open registration. Each Discord channel hosts one independent queue.

Discord-native alternative

You can create the same queue from Discord by running /setup in the text channel where the queue should live. This is useful when you want to finish setup without opening the web dashboard.

Creates a 4v4 queue with automatic team balancing and dedicated match channels inside the selected Discord category. The first team queue saves that category as the server default, so later team queues inherit it.

A 1v1 queue does not create dedicated match channels and does not need a category:

/setup options

Examples

Creates a 2v2 queue with default ELO settings.

Creates a 5v5 queue with flat +15/-15 ELO and a 5-minute cooldown.

Creates a 4v4 queue with captain draft and a 30-minute idle timeout.

Queue modes

AUTO_MATCH: The bot sorts players by ELO and uses a snake-draft assignment to create balanced teams automatically. No player interaction is needed.

SCHOOLYARD_PICK: Two captains are selected, then take turns picking players with buttons. If a captain times out, the bot auto-picks.

Step 3: Players register and join

Players only need one registration command before joining queues.

One-time registration for ELO tracking. Players start at 1200 ELO by default.

Adds the player to the queue. When enough players are in, a match is created automatically.

For team queues, players can join with a full pre-made party. Teams must match the queue's full team size and will only match against another pre-made team.

Step 4: Report match results

Team matches open a private dedicated channel for players and configured staff roles. Its match card contains the result action and any enabled voice, screenshot, commendation, or Run It Back actions.

Moderators and configured roles with Report Results use the Report Result button in that channel. The reporter does not need to be one of the players. The guided flow can capture each map, optional MVPs, optional flawless results, and scoreboard evidence.

Use /win as the authorized staff override for corrections and exceptional cases. The match ID appears in the match embed when the bot creates the match.

Other result commands

Step 5: Tune the queue

Return to the queue in your organization dashboard when you are ready to adjust its behavior.

• Configure ELO settings and rank tiers
• Set up a scores channel for cross-posting results
• Configure dedicated match channels, optional team voice rooms, and cleanup timing
• Enable queue boards, Run It Back, screenshots, challenges, maps, and other queue behavior
• Manage players, ELO edits, bans, and unbans
• Create automatic or manual player achievements
• Bulk sync nicknames and tier roles
• Re-invite the bot to repair permissions
• Configure seasons with automatic resets

See the Web Dashboard guide for full details.

Organization membership controls web dashboard access. Staff do not need to link a personal Discord account just to use the dashboard after they have been added to the organization. Discord role permissions for slash commands remain separate.

Add tournaments and ladders

Once the bot is connected, organization staff can create tournaments and ladders from the web workspace. Share the competition links through your own community channels. Competitors can use /gotnext in Discord for supported registration, check-in, match, reporting, and profile actions.

Go deeper once the first queue is running