> For the complete documentation index, see [llms.txt](https://docs.rivalryze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rivalryze.com/contests/auto-start-rules.md).

# Auto-Start Rules

How a Contest decides **when to actually begin** depends on three optional settings the host can configure:

* **Minimum participants** — won't start until N players have joined.
* **Maximum participants** — caps the player count.
* **Scheduled start date** — a specific date/time to begin.

The combination of these decides the start behavior. Here are the three patterns.

## Pattern 1: Minimum + duration set (no max)

The Contest starts the moment the minimum participant count is reached.

* The configured duration begins from that moment.
* If the minimum isn't reached by the scheduled start date (if set), the Contest is cancelled and entry fees refunded.

**Example:**

* Min participants: 4
* Duration: 7 days
* Scheduled start: in 3 days

Three players join immediately. On day 2, a fourth joins → the Contest starts and runs for 7 days from that moment.

{% hint style="success" %}
Use this when you want the Contest to launch as soon as there's enough interest, without waiting for a fixed date.
{% endhint %}

## Pattern 2: Maximum participants set

The Contest starts under either condition, whichever comes first:

* The maximum participant count is reached (the Contest is "full").
* The scheduled start date arrives.

**Example:**

* Max participants: 8
* Scheduled start: tomorrow at 8pm

If all 8 spots fill by 5pm today, the Contest starts immediately. If by 8pm tomorrow only 5 players have joined, the Contest still starts (assuming any minimum is met).

{% hint style="success" %}
Use this for Contests where you want a capped, predictable group — like an 8-person tournament.
{% endhint %}

## Pattern 3: Neither min nor max set

The Contest starts at its **scheduled start date**, with whoever has joined.

**Example:**

* Scheduled start: Saturday at noon

Whoever has joined by Saturday at noon is locked in. The Contest starts and runs for its configured duration.

{% hint style="info" %}
If no one (or only the host) has joined by the scheduled start, the Contest is auto-cancelled and any entry fees refunded.
{% endhint %}

## Quick reference

| Min set? | Max set? | Scheduled start? | When it starts                                                                                |
| :------: | :------: | :--------------: | --------------------------------------------------------------------------------------------- |
|     ✅    |     ❌    |         ✅        | When min is reached, before scheduled start. Cancelled if min not reached by scheduled start. |
|     ❌    |     ✅    |         ✅        | When max is reached, OR at scheduled start — whichever first.                                 |
|     ✅    |     ✅    |         ✅        | When max is reached (it's "full"), OR at scheduled start if min is met.                       |
|     ❌    |     ❌    |         ✅        | At scheduled start, with whoever's joined.                                                    |

## Race-style goals are different

For **Bounty** Contests using Hunter modes (Achievement Hunter, Platinum Hunter, Completion Hunter), the Contest can end the moment someone hits the target — or stay open until the end date if the host wants multiple winners. The auto-start rules still control **when** the Contest starts; the Objective Mode controls **when it ends**.

For **Battle** Contests (Points modes, and Collector modes when they launch), the Contest runs for its configured duration and ranks players at the end.

See [Objective Modes](/contests/objective-modes.md) for the full breakdown.

## What players see

* **Before the Contest starts**, the Contest page shows the start condition ("Starts when 4 players have joined" or "Starts Saturday 12pm").
* **The moment it starts**, all joined players get a notification: "Your Contest has started." This is your cue to sync your gaming platform and start playing.
* **If cancelled**, all joined players get a notification and an automatic refund.

## Can the host change these after publishing?

The host can edit minimum, maximum, and scheduled start **before the Contest starts** — useful for tuning if the Contest isn't attracting enough joiners. Once the Contest has started, these are locked.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rivalryze.com/contests/auto-start-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.