How Matches Work

The match room is the shared operational space for both teams and event staff. It keeps the competitive record separate from the public match page used by spectators.

Match lifecycle

1. The bracket or schedule assigns both teams.
2. Participants verify lineups and wait for the match to become actionable.
3. The map veto starts and teams complete each ban, pick, decider, and side choice.
4. Teams play the selected maps.
5. A team submits each map result, optionally with a score screenshot.
6. The opponent confirms or disputes the submission.
7. Required players upload MOSS evidence.
8. Strave finalises the result and advances the bracket.

The room navigation follows this order: Lineups, Map veto, Maps & scores, MOSS, and Match record.

Before the match

Open the match from the team workspace and confirm:

• the scheduled time and best-of format;
• both participating lineups;
• the rulebook and anti-cheat requirements;
• who is responsible for veto decisions and result submission.

Use match chat for coordination that should remain attached to the match. Event staff can see the same conversation.

Map veto

The event's match format defines the veto sequence. When it is your team's turn, the room displays Your turn, the required action, available maps, and a countdown when the step is timed. Otherwise it shows Waiting for opponent.

Pick and decider steps may include regular and overtime side choices. The team that selects a map is not necessarily the team entitled to choose the side, so follow the prompt shown in the room.

Submit scores

For each played map:

1. Open Maps & scores.
2. Select the map and enter both scores.
3. Attach a screenshot when required or useful.
4. Submit the result.

Scores cannot be tied. Standard competitive matches also enforce a minimum winning score. The opponent can approve the result or dispute it for staff review.

MOSS uploads

When MOSS is enabled, the room shows who must upload, how many files are expected, and the upload deadline. Upload the original .zip file; each file can be up to 500 MB.

Depending on organiser policy, missing evidence can:

• leave the match waiting for completion;
• prevent a team from starting its next match;
• trigger disqualification after the upload window.

Do not delete a submitted file unless it is wrong and the window still allows a replacement.

Admin calls and protests

Use Call admin for an active technical issue, connection problem, rule question, or player-conduct concern. Use a Protest for a formal challenge such as cheating, a rule violation, unfair play, or an incorrect score.

Include the concrete incident and relevant round or map. Staff can resolve a dispute, override a score, record a forfeit, or cancel a match. These actions are kept in the match record.

Public result and progression

Once the result is final, Strave updates the public match page, standings, and the next bracket slots. Completion can wait for an opponent confirmation, organiser resolution, or MOSS compliance even after the server result is known.