Run It Back

Run It Back is an optional queue setting that adds a rematch button to completed match result cards in the queue channel and dedicated match channel. It is off by default. Scores-channel copies do not include the button.

When every original player opts in, the bot starts a new match with the same teams. Players do not need to rebuild the lobby or rejoin the public queue.

Enable Run It Back

1. 1

   Open the queue

   In the web dashboard, select your Discord server, open Queues, and choose the queue you want to edit.

2. 2

   Open Behavior

   Find Run It Back in the queue's Behavior settings.
3. 3

   Turn it on and save

   The setting applies only to that queue. Leave it off on queues where immediate rematches do not fit your format.

You can also enable Run It Back while creating a new queue.

Player flow

1. A staff member reports the queue match result.
2. The completed result card shows Run It Back in the queue channel and dedicated match channel.
3. The first player clicks the button. The bot privately confirms their vote and notifies the remaining players in the result channel.
4. Each original participant clicks the button once. Eligible queue-channel and dedicated-channel copies show the same ready count.
5. When every available player agrees, the bot starts a new match with the same teams.

Votes are shared across the queue-channel and dedicated-channel result cards. The scores channel remains a clean result record without rematch controls.

If a player is already queued

Run It Back never silently pulls a player from another queue:

• A player waiting in a solo queue receives a private confirmation showing the queue and its current count. They can choose Leave Queue & Run It Back or Stay in Queue.
• Confirming removes the player from each listed solo queue, updates those queue boards, and records the Run It Back vote as one operation.
• A player queued as part of a party must leave that party queue first. The bot will not split the party.
• A player in an active match cannot vote until that match is resolved.
• If someone votes for Run It Back and later joins a normal queue, the newer queue join wins. Their older vote is withdrawn, the result-card count updates, and their private join confirmation explains what changed.

What carries into the rematch

• The same players stay on the same teams.
• Draft captains remain captains.
• Current player ratings are loaded after the completed match.
• The queue's current map setting still applies. Random-map queues pick again, and map-vote queues open a new vote.
• Dedicated match channels are created when that queue has them enabled.
• A fresh pair of team voice rooms is created when the queue has Team Voice Rooms enabled.
• The new match has its own match number, result, and rating changes.

Run It Back can be used again after the rematch is completed, as long as the queue setting remains enabled and every player agrees again.

Safeguards

• Unanimous only: Every original player must opt in.
• Participant only: Spectators and staff who were not in the match cannot vote.
• 15-minute window: Votes expire 15 minutes after the result is completed.
• One rematch per result: Repeated or simultaneous clicks cannot create duplicate matches.
• No silent moves: Leaving a solo queue requires a private confirmation. Party queues are never split, and active matches are never interrupted.
• No stale consent: Joining a different queue withdraws the player's older Run It Back vote.
• Queue state respected: A paused, disabled, or reconfigured queue will not start an invalid rematch.
• Restart safe: Votes and result-card locations are stored in the database, so a backend restart does not lose the ready count or create a duplicate rematch.

Availability

Run It Back supports regular queue matches, including Auto Match and Schoolyard Pick queues. Direct challenge wagers and tournament matches use separate match rules, so their result cards do not offer Run It Back.

If you enable the setting after a result card was already posted, that older card will not gain a new button. The next completed queue match will use the new setting.