Queue Settings Reference

Unique identifier for the queue; forms the DynamoDB key `queue_id = client_id|queue_name`. Set once at creation, never editable.

Headline shown on the queue/launcher embed.

Optional at creation — omitting it reuses queue_name as the headline. No Discord configure modal edits the title after creation, so post-creation edits are web-dashboard only.

Body text on the queue/launcher embed.

Like title: optional at creation, and post-creation edits are web-dashboard only.

Which Elo leaderboard this queue's matches record ratings on.

Blank-submit asymmetry in the Discord modal: headless preserves the current value on blank; hosted clears it to null.

Banner image on the queue/launcher embed.

Free text shown when players vote on match results (e.g. 'Submit screenshots to #evidence').

Whether player names are displayed in the queue join list.

Discord modal field is named `show_names` but persists as `join_notification_show_names`.

Players per team. Versus/team queues are two equal teams; anonymous queues can set the two sizes independently at creation.

The Match Rules modal takes one `team_size` number and writes `team_sizes: [n, n]` plus the display string `versus: "NvN"` — asymmetric sizes are creation-time (anonymous) only. Creation writes a separate `versus_format` display key that the modal does NOT update (see internal keys).

Players needed before an FFA/co-op match fires (headless) or a lobby can start.

The web form shows min/max players for every queue type; the Discord Match Rules modal only shows them for FFA/co-op.

Cap on players per FFA/co-op match.

Players needed to fill a co-op hosted lobby. Also feeds the default lobby size for host customization.

FFA/co-op range queues hold the pop open after min_players is reached: the first crossing arms a grace window of this many minutes so more players can join (up to max_players). Reaching max_players pops instantly; at the deadline the match starts with everyone present.

No configure modal edits it — the web queue-settings form is the only post-creation editor. Enforced ONLY when min_players < max_players (creation defaults max_players to min_players when omitted, so queues without an explicit max keep instant pops). The window is armed once per min-crossing and not extended by later joins; if players drop below min before the deadline it clears without a match. Runs on QueueGraceTimeoutWorkflow, recovered by the deploy sweeper.

How players are split into teams when a match forms.

This is the QUEUE vocabulary. The /host command and lobby runtime use a different `team_mode` vocabulary (see HOST_TEAM_MODES); hosted-lobby creation translates one into the other ('balanced_teams' → 'balance_elo', etc.). The web form additionally offers a bare 'captains' value — the runtime recognizes it (generic captains display mode, part of CAPTAIN_MODES) but no Discord surface offers it.

Per-queue custom team display names, inherited by every match the queue spawns.

One Discord paragraph field (`team_names_input`, comma/newline-separated `emoji:name` segments) persists TWO parallel arrays: team_names + team_emojis. Blank resets both to defaults (null).

Per-queue custom team emojis (parsed from the same input as team_names).

Maximum rating gap allowed between players when forming a match.

Minutes before the same two players/teams can be matched against each other again.

Clears the rematch cooldown between two players once either of them plays someone else.

Choice-based (faction/position) matchmaking keyed to a leaderboard choice definition: teams are all-same-value or one-of-each-value.

Persists an object {rival_choice, rival_choice_display, choices, scores, balance_teams?, team_quota?} — Discord-only (deliberately omitted from the web form). Modal field is named `rival_team_choice`. Re-selecting the same choice preserves scores; picking a different one zeroes them.

Fixed per-position formation (e.g. 'goalkeeper:1, defender:2') each team must satisfy under balanced Unique Choice Matchmaking.

Requires SOME rival choice to be configured first (the submit rejects only when none exists — a non-balanced Faction-vs-Faction choice passes and the quota saves, though it is only honored in balanced mode). Nested under rival_teams; saving rewrites the whole object.

Whether results record, affect Elo, and who approves them.

Fans out into four derived booleans persisted alongside: match_result_disabled, ranked, admin_confirmation, admin_decide (see internal keys). No longer a creation option on any queue mode — every queue is created as 'ranked' and changed from the Match Rules modal or the web form. (Co-op queues never had one.)

Series structure: one match, unlimited matches, best-of-N, or cumulative points over N rounds.

Persisted as a single string ('best_of_3', 'cumulative_5'); the modal/web split it into a format select + count input. The Discord Match Rules modal rewrites competitive_format on EVERY submit — a submit meant to change only the voting mode still rewrites the format. No longer a creation option on any queue mode: every queue starts at 'single_match' and picks up a series format from the modal or the web form.

How the series result becomes a leaderboard rating change — fires once per series (after the final round for multi-round formats).

Naming inversion: 'Configure Scoring' persists the series_* keys, while 'Configure Cumulative Scoring' persists the plain scoring_mode/placement_points keys (per-round). Discord-only.

Per-place rating points (e.g. '25,15,10,5') for Placement Points mode, or the win/loss base for Stat Points mode.

A blank submit never clears a saved list (deliberate, so toggling modes does not wipe it). Discord-only.

How each round's placements become scoreboard points whose totals decide a multi-round series (the 'Match Score' axis, distinct from Rating Mode).

Menu entry only appears for best_of_* / cumulative_* formats. Discord-only.

Per-place points each round awards to the in-series scoreboard (e.g. '20,15,12,10').

Blank never clears a saved list. Discord-only.

Named per-round stats (kills, caps, …) with points-per-unit and optional rounding, submitted each round of a cumulative series.

Modal field is named `stat_definitions`. Menu entry only appears for cumulative_* formats — stricter than Cumulative Scoring, which also shows for best_of_*. Discord-only.

Whether one captain submits team stat totals per round or every player submits individually.

Custom noun for each round of the series (e.g. 'Game', 'Map', 'Half').

Whether the highest or lowest cumulative total wins the series.

Auto-remove idle players/teams from a headless queue after this many minutes (enforced by the queue timeout Workflows).

No longer a creation option — headless queues are created at 10 and retimed from Configure Queue Timeouts or the web form. Hosted launchers no longer write it at all, which is harmless: hosted lobby auto-close actually reads `lobby_timeout_minutes` (Configure Lobby Limits), and the hosted-stored idle_timeout_minutes never had a consumer in the lobby-create path.

Re-queue cooldown applied immediately after players are matched (before the match is played).

Blank submit clears the stored value, which reverts behavior to the runtime default of 1 minute — set 0 explicitly to disable.

Re-queue cooldown applied after a match result is recorded.

Prevents players from re-joining the queue until they report their pending match result.

Blocks joining a new lobby while already in an ongoing match, per-queue or server-wide.

Replace/remove players who never join the match voice channel after a match forms (via the voice-join timeout Workflow).

How long players have to join voice after a match forms before being treated as dodgers.

How long a voice dodger is blocked from re-joining the queue. Admins can pardon via the Pardon Dodge Cooldown menu action or the web dashboard.

Ping players not yet in voice this many seconds before the dodge timeout fires.

Named map pool the queue draws maps from.

How maps are selected for matches. FFA/co-op/anonymous creation only offers Simple; the full veto strategies are versus/team.

Cross-surface drift in the product: creation offers stage_striking / stage_striking_counterpick but not random / smash_striking; the configure modal and web form offer random / smash_striking but not the two stage_striking values. All are real runtime strategies. The modal's 'none' choice persists as null.

Simple Vote only: auto-conclude the map vote after N seconds, picking the leading map (random on no votes). Headless: countdown starts at match creation; hosted: when the lobby fills.

Channel where match/lobby-start announcements post.

No longer a creation option — the queue_* commands seed it with the channel the command was run in, and Configure Match Announcements (or the web form) retargets it.

Channel where finished matches are listed; also where 'ping on recorded' mentions post.

Same as match_start_channel: no longer a creation option, seeded with the channel the command was run in and retargeted from Configure Match Announcements or the web form.

Where the match/lobby panel (roster, map vote, report buttons) is posted. A dedicated channel: the bot creates one text channel per match — placed under the Temp-Channel Category and named with the Shared Channel Name Template — and deletes it when the match ends. Results still post to the Match End Channel.

Private = visible only to the match participants, the configured admin role(s), and the bot. Public = visible to everyone, so non-players can tune in and watch. The Temp-Channel Category controls placement only (where the channels nest), not visibility; with no category set the channel is created at the server root. The per-match channel doubles as the shared text channel (no separate one is created); voice channels are still governed by Shared Match Channel / Per-Team Channels. Legacy queues saved with the old single "dedicated" value are treated as private.

Discord category where auto-created match channels are placed.

Auto-create a shared text/voice channel for all players in each match; deleted when the match ends.

Auto-create per-team channels, private (team-only) or public.

Known quirk: the Discord Auto-Channels modal persists this key unconditionally with default 'disabled', so submitting that modal on an FFA/co-op queue (where the field isn't shown) resets any stored value to disabled.

Spin up a public or private thread for each match.

Cross-setting coupling: when no dispute channel is set, disputes fall back to the match thread — which only exists if threads are enabled here.

Whether the bot moves players into (and back out of) auto-created voice channels.

Naming template for the auto-created shared channel. Tokens: {code} {title} {vs}.

Naming template for auto-created per-team channels. Tokens: {code} {title} {team} {emoji} {n} {vs}.

Naming template for the auto-created match thread. Tokens: {code} {title} {vs}.

Channel where queue join/leave events post.

Role mentioned in the join-notification post.

Role pinged when a match starts.

Role pinged when a match ends.

Who gets a real mention in the match-end-channel post when a result records.

Posts into match_end_channel — a silent no-op if that channel is unset (the modal warns). The Discord modal for it is headless-only, but hosted lobbies consume the setting too (copied onto the lobby at creation); for hosted queues set it via the web form.

After one captain reports a result, auto-record from that single report if the other captain never votes within this many minutes.

Blocks recording a match result until a screenshot has been submitted as evidence.

Adds a 'Scan Result' button that has AI read a scoreboard screenshot to pre-fill the match result.

Scoreboard-reading instructions live on the leaderboard/server config (/leaderboard_config screenshot_instructions), not on the queue.

When an AI scan reads every player and stat cleanly, record it with no manual approval step.

Channel where players upload match screenshots.

Channel where match events (scores, disputes, results) are logged.

Channel where dispute notifications post when players request admin help.

Role mentioned when a dispute is filed.

Password players must enter to join a headless queue.

Creation option exists only on /queue_versus headless; every headless queue can set it post-creation via the modal or web. Never pre-filled in modals (sensitive).

Password required to open a lobby from the launcher.

Default join password applied to newly created hosted lobbies (hosts can change it per lobby).

Hide the lobby code from the embed and only reveal it via a button click once the lobby is full.

Lives in two different Discord modals depending on mode. The web form only shows it for hosted queues.

Rating floor to join (or host from) the queue; unrated players are treated as the league’s default rating.

The headless menu hides this for team queues (teams join with team ratings); the launcher menu always shows it. Discord-only — not editable on the web.

Which of the player’s ratings the floor is checked against; per-format types resolve from the actual match being joined.

Nulled automatically whenever min_elo_to_join is cleared.

Roles (beyond server administrators) allowed to confirm/reject results in Admin Approval / Admin Decides modes. Holders are also granted visibility into the private lobby channels and (via Manage-Threads on the parent channel) private lobby threads the bot creates, so an admin can oversee a lobby they aren’t a participant in.

Every save also mirrors the first role into the legacy single `admin_role` key. The web form edits only the legacy `admin_role` (single role), not this array.

Enables the '👥 Join as Party' button so pre-made groups queue together with a same-team guarantee.

Runtime eligibility additionally requires: team size ≥ 2, formation not players_choose/captains/no_teams, unique-choice matchmaking off, and no queue password.

Whether pressing 'Host Lobby' creates a lobby immediately with queue defaults or first shows the host a customize modal.

Lower bound of the player count a host may pick when customizing their lobby.

Upper bound (hard cap 25) of the player count a host may pick when customizing their lobby.

Restrict who may open lobbies from this launcher.

Caps simultaneous open lobbies for one host in this queue. Admin hosts bypass this cap (staff seeding).

Caps still-forming lobbies across all hosts (started/full lobbies stop counting). Enforced for everyone, including admins.

Auto-close a hosted lobby that never fills after this many minutes (scheduled as a Cloudflare Workflow at lobby creation).