VALORANT Custom Game Settings & Tournament Mode Guide (2026 Official Referee Handbook)

A shocking percentage of community VALORANT tournament disputes start before a single bullet is fired—caused by a lobby host rushing through the Custom Game options menu and forgetting a single toggle. Launching a map with `Allow Cheats: ON`, forgetting `Overtime: Win by Two`, or leaving `Hide Match History: ON` can invalidate a 50-minute map, block automated API score reporting, or suddenly end a 12–12 nailbiter in a single-round sudden-death coin flip.

In both VCT Challengers circuits and automated community brackets on CLUTCH ARENA, the **Higher Seed Captain** (or Map-Picking Captain in BO3/BO5 series, as specified in your Match Room) is designated as the **Lobby Host**. Before inviting the opposing captain via `RiotID#TAG` or private Party Code, the Lobby Host must configure the lobby to **Closed** and verify every single parameter inside the `Options` modal.

Professional VCT teams toggle `Hide Match History: ON` during private weekday scrimmages so upcoming league opponents cannot scrape their pistol setups or Viper orb lineups from public stat trackers. Because amateur players hear pros mention that setting on stream, they frequently enable it out of habit when hosting weekend community tournaments—unintentionally sabotaging modern tournament automation.

When `Hide Match History` is set to **ON**, Riot Games' match-v1 production servers mark the match payload as restricted. External tournament engines, including CLUTCH ARENA's Riot and HenrikDev telemetry pipeline, receive a masked or unauthorized response rather than round-by-round kill events, plant timestamps, player PUUIDs, economy loadouts, and X/Y player coordinates.

Setting **`Hide Match History: OFF`** unlocks the entire automated post-match workflow: the moment the final round concludes, CLUTCH ARENA ingests the cryptographic Match ID, confirms that all 10 registered Riot accounts participated on the correct vetoed map, updates the live tournament bracket without anyone uploading a screenshot, calculates tournament-wide ACS/KAST leaderboards, and compiles the full interactive **2D Minimap Replay** across all rounds.

While 5v5 Standard follows Riot's out-of-the-box VCT presets across the active 7-map pool (**Abyss, Bind, Corrode, Haven, Lotus, Summit, and Sunset**), 1v1 Aim Duels and 2v2 Wingman cups require explicit custom ruleset agreements so aggressive players cannot abuse Ultimate orbs, Odin wall-spamming, or multi-site Spike plants when only two defenders exist.

Inside the VALORANT client, you have two ways to run compact formats: Riot's built-in **Skirmish** custom mode (ideal for pure 1v1 and 2v2 gunplay arenas without Spike economy overhead) or **Standard Mode Single-Site Retake/Plant Rules** (popular for tactical 2v2 Wingman brackets where economy management and Spike pressure matter). Whichever sub-mode your tournament selects, publish the exact equipment and site boundary matrix inside your ruleset.

Players transitioning from VALORANT Ranked Competitive queues into organized tournaments are frequently surprised by two mechanical differences at `12–12`. First, **there is no Overtime Draw Vote** in Custom Game Tournament Mode. Unlike Ranked—where a single exhausted player can force a `13–13` or `15–15` draw when vote thresholds drop—Tournament Mode forces teams to battle through unlimited two-round Overtime sets until one roster achieves a clean **2-round lead** (`14–12`, `15–13`, `18–16`, and so on).

Second, understanding the exact **Overtime Economy & Ultimate Reset** transforms how IGLs call Round 24 (`12–11` or `11–12`). Because regulation Creds and Ultimate orbs never carry over into Round 25 (`12–12`), saving an Operator at `11–12` when the round is unwinnable has zero economic upside—your entire bank will be wiped and replaced with exactly **5,000 Creds** anyway.

In pan-European tournaments where an Iberian roster from Lisbon faces a Polish squad from Warsaw or a Nordic five-stack from Stockholm, server pod selection directly impacts peeker's advantage, Operator hold reaction windows, and hit registration. Allowing the Higher Seed to blindly pick their home 8ms server while forcing opponents onto 68ms destroys competitive integrity.

Sanctioned tournaments enforce **Minimum Ping Differential ($Delta ext{ms}$)** rather than minimum average ping. The objective is to select the Riot Game Pod where the difference between Team A's 5-player average latency and Team B's 5-player average latency is as close to **0ms** (and strictly under **15–20ms** where geographically possible).

Toggling `Tournament Mode: ON` transforms the Custom Game lobby screen from a standard 10-player grid into a structured esports staging area with dedicated **Team A Coach**, **Team B Coach**, and **Observer** rails—plus granular **Moderator** crowns.

Understanding who may sit in which slot prevents accidental Sixth-Man coaching violations (one of the severest offenses in Riot competitive play).

Players frequently confuse tactical momentum timeouts with hardware crash pauses, leading to heated arguments in `[All]` chat when a team pauses for 4 minutes after losing four rounds in a row. Your tournament rulebook—and your referees—must enforce a crystal-clear wall between three distinct stoppages.

Even in flawless setups, VALORANT patches occasionally introduce edge-case client bugs during weekend brackets. Keep these rapid recovery playbooks on hand so a minor glitch never derails your tournament schedule:

• **Vanguard `VAN 1067` / `VAN -81` Client Crash:** Caused by Windows TPM 2.0 or `vgc` service hanging mid-match. Instruct the affected player NOT to verify full game files (which wastes 8+ minutes); instead open `services.msc`, restart the `vgc` service, and relaunch Riot Client—typically restoring them inside 150 seconds.

• **Voice Chat Dead After Halftime / Reconnect:** If in-game Team Voice stops transmitting, players already seated inside their locked `ClutchBot` Discord Team Voice Channel experience zero disruption—one of the biggest reliability advantages of running Discord-synced voice rooms alongside the game client.

• **Host Accidentally Left `Play Out All Rounds: ON`:** If Team A reaches their **13th round win** (for example `13–7`) and the client starts Round 21 instead of ending the game, **the match is officially over at `13–7`**. All 10 players may immediately leave the custom game; referees validate the `13–7` timestamp via round timeline telemetry.

• **Catastrophic Server Crash Mid-Map (Score Recovery):** If a Riot server pod crashes entirely at `8–5` and drops all 10 players back to the main menu, recreate the lobby on the fallback pod, play from `0–0` using a **Continuation Offset** (first team to reach `13 - current_rounds` with proper side continuation and a standardized 5,000-Cred pistol/gun restart agreed by the Head Referee).