Event Settings & Modes

Configure your event and pick from the available competition modes.

The event workspace separates the structure of the competition from day-to-day operations. This page explains each settings area and what locks when you publish.

Most settings save automatically after a short delay. Wait for the saved indicator before you leave a page.

Event configuration navigation and the details form

Details and visibility

Open Configuration in the event workspace. On the Details page, you set the event name, platform, visibility, region, and shareable tournament link.

Renaming the event also changes its slug, and the previous URL stops working. After a rename, send the new link to teams and production staff.

Registration modes

The event type that you choose at creation defines how participants enter:

Event typeParticipantsTeam formation
Standard tournamentExisting teamsStrave copies each team at signup.
Draft eventIndividual playersCaptains draft approved players.

Standard events can also turn on Community cup mode. This mode removes the normal 5v5 requirement and lets you choose one to five players per side:

  • With one player per side, players register as individuals.
  • With two to five players per side, teams register. In Team formation, choose Teams and friend groups or Random teams.
  • The team size locks when you publish the event.

Registration settings also control manual approval, automatic check-in for eligible late signups, signup questions, and organisation ban-list enforcement.

Stages and formats

Stages are the phases of the competition. Strave supports these formats:

  • Single elimination.
  • Double elimination.
  • Round robin.
  • Swiss.
  • Playoff stages for placement in later phases.

Each stage can set its own best-of format, maximum number of teams, groups, check-in window, schedule, and advancement. Round-robin and Swiss stages also use points and tiebreaker rules.

Create the stages in the order that teams play them. Each later stage receives the teams that advance from the previous stage. First-stage groups draw from approved signups.

Map pool and match format

In Map Pool, select a preset or a custom list of maps. The map pool locks when the event leaves the draft state.

In Match Format, define named best-of configurations, such as bo1 and bo3. Each configuration lists the ban, pick, decider, and side-choice steps that match rooms use, in order.

The number of veto steps must fit the size of the map pool. Set up the map pool first. Then test every format that a stage uses.

Rules and anti-cheat

The Rules area controls these settings:

  • Uploaded or linked rulebooks.
  • Whether teams can file protests, and for how long.
  • The anti-cheat mode and the instructions for players.
  • MOSS upload targets, deadlines, retention, and enforcement.
  • Optional automatic disqualification rules.
  • The Strave anti-cheat requirement, its start enforcement, and the instructions for players. Only administrators with the scoped configuration permission can change them, and each change needs an audit reason.

With strict MOSS enforcement, a result stays pending, or the team's next match stays blocked, until the required evidence is uploaded.

MOSS and the Strave anti-cheat are independent. An event can use either, both, or neither. The Strave anti-cheat defaults to not required. The players ready up after the map veto and before the match, so the anti-cheat never holds the veto. With hard start enforcement, a match with a complete veto cannot start until every required player is ready. It starts automatically when the last player is ready, or when an organiser overrides the hold with a reason. Anti-cheat reports never block a result: a player uploads a report only when an organiser requests one.

Team-change policy

You set separate policies for team names, logos, and lineups:

  • Open: Strave applies eligible changes directly.
  • Request: Strave sends changes to organisers for approval.
  • Locked: Strave blocks changes.

Optional date windows limit when a policy applies. You review pending changes in the team's detail view under Signups. For the full workflow, see Event teams.

Branding and broadcast

Branding provides the public event banner, description sections, sponsors, and the identity of your stream overlays. Broadcast-specific settings, such as colours, ticker lines, info content, and crew slots, are on the Broadcast page.

Test your browser sources before the first playday. For more information, see Overlay overview and Stream Manager.

Notifications

Event notifications can go to Discord and HTTP webhooks. Keep each webhook destination focused on the event messages that the receiving channel or system needs.

Select the events for each webhook in the second step of the webhook dialog. The events you can select depend on the provider:

  • Discord webhooks receive admin calls and protests.
  • Custom HTTPS webhooks receive all event notifications: registration, invites, match moderation, and draft events.

Treat webhook URLs as secrets. For example, anyone with a Discord webhook URL can post messages to that channel.

After you add a destination, send a test event to confirm that it works.

Draft and published states

Use the draft state for structural work. Publishing limits what you can change, so that active signups, brackets, and match rooms stay predictable. Before you publish, confirm:

  • Registration settings and team size.
  • The map pool and every best-of format that a stage uses.
  • First-stage groups, capacity, and check-in.
  • Rules and MOSS policy.
  • Public event content and sponsors.
  • Notification and broadcast tests.