# Season leagues

Leagues are recurring competitions with season standings, divisions, and permanent season awards. The first format is inspired by [TMtour](https://tmtour.org/views/rules.html): groups of 4–7 players playing four-player games. League standings are separate from the boardgame's general Elo ranking.

## Playing a season

Open **Community → Leagues**, choose a league, and read the season's rules and game settings before registering. Registration is an explicit commitment to all four assigned games; those games are created and seated automatically when an organiser starts the season. Register again for each season you want to play.

Registration is not capped at seven players. Groups prefer seven players, with smaller groups at the bottom so every eligible registrant is seated when at least four register. A group of **N players plays N four-player games**:

- Each player participates in four games.
- With seven players, each pair meets twice.
- With six players, each player meets three opponents twice and two opponents three times.
- With five players, each pair meets three times; with four, each pair meets four times.
- Each player occupies each initial seat once.

For Gaia Project, the initial seat also determines the initial nomination position; auctions can change the eventual playing order. The schedule does not guarantee each post-auction turn position once.

New league games are public, rated, and have independent random setups. They affect the boardgame's ordinary Elo under the usual game-end rules; league points and standings remain separate. Previously created unrated games keep their original rating setting, including on retries. Rating is a format rule, not a saved engine-setup option: newly created fixtures use it even for seasons whose setup was saved earlier. There is no restriction on watching other league games. The format does not use mirrored series or compare raw victory points between tables.

Both manual and automatic starts require at least four eligible, consenting players. Below four, the season waits; there are no bot fillers. Divisions have capacity for 1, 2, 4, 8, … groups. Groups are filled from the top and rebalanced at the bottom: 8 → 4 + 4; 9 → 5 + 4; 10 → 5 + 5; 13 → 7 + 6; 15 → 7 + 4 + 4; 18 → 7 + 6 + 5; 22 → 7 + 7 + 4 + 4. Players may withdraw before the season starts. Once fixtures exist, contact an organiser rather than trying to replace a player through the ordinary lobby controls.

## Points and standings

Finishing positions earn **6, 3, 1, and 0** league points. Tied players share the points for the positions they occupy. For example, two players tied for second receive `(3 + 1) / 2 = 2` points each.

The platform uses the game's final rankings, including any native tie-breaks, rather than assuming higher raw scores always win. Final Gaia Project scores already include auction costs; the league does not subtract them again.

The season page publishes the standings tie-break and division-placement policy. The first season uses boardgame Elo for seeding. Later seasons use previous league performance, with promotion and relegation. Group winners target one division up; the bottom player in groups of four or five, or the bottom two in groups of six or seven, target one division down, within the previous season’s division limits. Departures and incomplete division tiers can require filling vacant places from lower-ranked entrants.

A season normally lasts two calendar months. An unfinished game does **not** automatically give everyone zero points at the deadline. Cancelled games, exceptional endings, and missing results require organiser review. An organiser can record a reasoned result or extend the deadline. All fixtures must be resolved before a league admin finalizes the season.

Finalization saves standings and awards. An ordinary game finishing and a league season being finalized are separate events.

## Game settings

The competition format stays fixed, but the season's game setup is configurable: expansions, auction method, and the boardgame's other supported options.

Settings start from:

1. Explicit season overrides.
2. Otherwise, the previous season's saved settings.
3. For the first season, the boardgame's current **Play live** preset and game defaults.

These are copied values, not a live reference to the preset. Editing Play live settings later does not change an existing season. The preset supplies game rules, **not** its live clock or player count: league games have four players and their own asynchronous clock.

Organisers should review the resolved settings before opening registration. Game settings are frozen when registration opens, so players know the rules they are committing to; player assignments are frozen when the season launches. The next season copies the previous season's resolved setup, with an opportunity to change it before registration opens.

## Organising a league

Each boardgame has one league, with numbered seasons at addresses such as `/leagues/gaia-project/seasons/season-1`. Permissions are scoped to that league. An organiser role grants only the league permissions described below, never site administration privileges.

| Role         | Responsibilities                                                                   |
| ------------ | ---------------------------------------------------------------------------------- |
| Site admin   | Create leagues, appoint league admins, and retain oversight.                       |
| League admin | Configure seasons, manage organiser access, and finalize standings.                |
| Organiser    | Open registration, manage participants, launch fixtures, and resolve match issues. |

Management controls appear on the league and season pages only for authorised users; the server independently verifies permissions. Role changes, result adjudications, and finalization are audited.

Automatic fixture processing is retryable. A retry must retain the same game IDs, participants, seats, settings, and seeds rather than creating a second set of games. An organiser can request reconciliation when a fixture needs its start or result processing retried.

## Recurring seasons

Existing leagues stay manual until a league admin or site admin saves a recurring schedule on the league page. Create and configure the first season first. Choose **two calendar months** (the default) or **three calendar months**, a planned next start, and a reason (5–2,000 characters). Schedule inputs explicitly use **UTC**; public dates display the viewer's timezone.

The scheduler creates the next season from the saved setup and opens registration **14 days before the planned start**. Players must explicitly register and consent again every season: previous participation never enrols them automatically. The scheduler starts only after all of these conditions hold:

- The planned start has arrived.
- Registration has actually been open for at least **seven days**.
- The previous season is finalized and at least **seven days** have passed since finalization.
- At least **four eligible, consenting players** are registered.

Late games delay the next start rather than receiving automatic zeros. Fewer than four players also leaves the season waiting, without bots. For recurring leagues, the scheduler finalizes a fully resolved season; unresolved fixtures still require organiser attention. After a season actually starts, the next planned start is recalculated from that **actual start**, not an outdated target date.

Admins can pause automatic scheduling, resume it, or postpone the next start, with an audited reason. Postponements never advance a start and require at least seven days' notice. Resuming also adds at least seven days before a start can occur. Pausing does not cancel existing games or erase registrations. The public schedule shows planned dates, not a promise that unresolved games or insufficient registrations will be bypassed.

## Recognition

Profiles show small, flat chips, using the same styling and game pictogram as ordinary rankings. Each boardgame has five separate badge identities:

- **Current division** (`#2`): the actual division in the latest started season, including a completed season until the next starts. Skipping the next season removes only this badge.
- **Best division** (`Best #2`): the highest division ever played. D1 is highest; registrations and projected promotions never count.
- **Group winner**: bronze at **1**, silver at **3**, gold at **10** group wins, following the contribution-badge thresholds. D1 wins count too. Duplicate group-winner/champion ledger records count as one win, not two.
- **Champion**: the D1 winner of the latest **completed** season. Starting a new season does not remove the title; the next champion is determined only when that season completes. The first D1/rank-1 row in the saved standings is the deterministic winner.
- **Past champion**: a previous champion who is not the current champion. Repeat winners retain Champion, never both titles at once.

The chips have short labels and link to the existing badge glossary; there are no league badge dialogs or history panels. All five identities can be selected with the existing featured-badge picker. The catalog keeps them alongside rankings.

Season results and the original award ledger remain the source of truth, without destructive migration. Organiser is a league role, not a badge. Badges grant no permissions. Only actual frozen seats in public, started seasons qualify; draft or registration-only seasons, missing records, and private games cannot create public claims. Deleted accounts receive no badges and do not appear in directories. Historical results remain, and deleting a champion does not promote a replacement.

Appearances derive badges in batches. League directory eligibility and counts are checked live in MongoDB before pagination, with full histories loaded only for the returned page.
