Tournament Creation, Settings, and Structures

Tournament management is the core of the organizer workspace. It supports the full lifecycle from setup to publication to live execution to final completion.

Tournament Lifecycle

Organizers can move tournaments through clear operating states, including setup, publication, active operation, pause or cancellation scenarios, and completion.

That means the platform supports more than creation alone. It also supports:

• publishing an event to the public experience,
• starting and running it,
• pausing or resuming it when needed,
• completing it when results are final,
• cancelling it when business or operational conditions require it,
• cloning an existing event to speed up repeat programs.

Tournament Creation

Tournament creation supports both direct setup and reusable configuration patterns.

Organizers can:

• create a tournament from scratch,
• start from a reusable template,
• use custom competition modes when they need special rules or a partner-specific event variant,
• browse template collections,
• review template categories and recommendations,
• compare template details, reviews, structure, and analytics-style signals before selection.

This is valuable for partners because it reduces repeat setup work across similar events.

Custom Modes And Special Rule Sets

Not every partner runs a standard event. Some need special scoring rules, adjusted team sizes, limited map pools, or a recurring branded format that differs from the usual setup.

Tournament Suite supports this through custom mode capability. In business terms, this means a partner can package a distinctive event format and reuse it instead of rebuilding the same unusual rules every time.

Settings Model

Tournament settings are split into practical sections so organizers can configure events with more control.

Current settings areas include:

• general settings,
• event details,
• registration rules,
• participant rules,
• match rules,
• discipline or game configuration,
• identity and public-facing identity settings,
• contact information,
• appearance,
• LAN-related settings,
• permission-related settings,
• map veto-related settings.

Together, these settings cover both operational logic and public presentation.

Structure Design

Structure design is a major operating capability rather than a simple bracket upload.

Organizers can work with:

• stage-based structure planning,
• structure summaries and history,
• stage creation, editing, and deletion,
• topology and visualization views,
• preview generation before publication,
• full structure publication,
• freeze and unfreeze controls,
• regeneration previews and full regenerations,
• placement rules,
• final standings management,
• downstream match handoff preparation.

This makes structure management suitable for both standard and more advanced event models.

Bracket Sizing And The Reserve Bench

Single-elimination and double-elimination brackets are sized to the number of approved participants, not the tournament's maximum participant count. Because a clean bracket needs a power-of-two number of entrants, the platform builds the bracket at the largest power of two that is less than or equal to the approved count. For example, an event with 12 approved entrants seeds an 8-participant bracket.

Any approved participants beyond that power-of-two cutoff are not dropped — they are placed on a reserve bench, ordered by seed, so the strongest available entrants are the ones seeded into the bracket first. Organizers can move a participant to the reserve bench manually, and can promote a reserved participant into the approved roster later (for example, to backfill a slot opened up by a withdrawal), as long as there is room in the approved roster to do so.

Round-robin, Swiss, and group-stage structures do not have this power-of-two constraint, so every approved entrant is scheduled and nothing is held in reserve.

Seeding

Seeding determines the starting position of each participant in the bracket, and it is a distinct step from building the structure itself. Organizers can:

• generate seeding automatically based on the tournament's seeding method,
• preview a proposed seeding before it is applied,
• apply seeding to lock in starting positions,
• validate a seeding arrangement,
• adjust individual seeds by hand, including drag-and-drop reordering,
• update seed assignments in bulk.

Because bracket sizing depends on approved entrants and seed order (see above), reviewing and refining seeding is a normal part of preparing a structure for publication, not just a one-time setup step.

Supported Competitive Formats

The organizer workspace includes structure support for a broad set of competition models, including:

• single-elimination style flows,
• double-elimination style flows, with full loser-bracket routing and a grand final,
• round-robin configurations,
• Swiss formats,
• group-and-playoff style designs,
• custom or mixed structures,
• duel and free-for-all style views where relevant.

Tournament Workspace Sections

Once a tournament exists, organizers work through a connected set of spaces such as:

• overview,
• settings,
• structure,
• participants,
• matches,
• live operations,
• officiating,
• streams,
• broadcast,
• analytics,
• fantasy,
• payouts,
• branding,
• share tools,
• final standing and placement management.

The important point is that Tournament Suite treats the tournament as a living workspace, not a single record.

Branding And Presentation

Tournament presentation is also handled inside the tournament workspace.

Organizers can manage:

• logos and banners,
• public-facing presentation,
• social presentation,
• visual branding,
• share-oriented assets and links.

That helps a partner operate events that are both functional and brand-consistent.

Typical Tournament Setup Flow

1. Choose the project the tournament belongs to.
2. Create the event directly or from a template.
3. Configure settings, rules, and participant requirements.
4. Build or refine the structure and preview the outcome.
5. Add branding, sponsors, communications, and financial setup.
6. Publish the event and move into participation and live operations.

Why This Matters For Non-Gamers

For a non-gaming reader, this area is similar to a mix of event configuration, rules management, and operational publishing.

It is the part of the platform where a partner decides:

• what kind of event is being run,
• how the event works,
• what makes it standard or special,
• what participants must do to join,
• how the event should look and behave once it goes public.

Related pages:

• Live Operations, Broadcast, Streams, and Media