Content generated with AI — it may contain mistakes.

ExyliaPracticeCore/How it worksUpdated in v1.4.0

Seasons

What a new season resets and keeps, how to start one from the admin menu, and the server restart that follows.

Page 18 of 355 min read

A season is a numbered period that every stat is stamped with. Starting a new one gives everybody a clean ladder at the starting rating, while lifetime stats and match history stay. It takes a moment, however many players you have, and nothing is deleted.

What a new season changes#

Kind of dataAfter a new season
Season stats (kills, wins, ratings, ladders, sidebars, placeholders)Start empty. Every rating starts again at elo.starting-mmr
Lifetime statsNever reset
Match historyKept; each match remembers the season it was played in
ELO boostsAll personal and server-wide boosts are cancelled, because a boost belongs to the season that granted it
Kit loadouts, arenas, kits, settingsUntouched

The previous season's rows stay in the database under their season number, so old standings are still there for the web and for season selectors.

Start a new season#

Only players with exyliapractice.admin can do this, and there is no command for it.

  1. Run /epc, click Data management, then New season. The button shows the current season and the next number.
  2. A confirmation screen opens. Click Confirm (or Cancel).

The menu closes and you get a message that the new season is starting. During the next moments the queue is locked: players who try to queue are told matchmaking is temporarily blocked. A second rotation started while one is running is refused.

What happens, in order:

  1. The queue is locked.
  2. The active season is closed with an end time and the next number is opened as the active one.
  3. Online players switch to the new season straight away, without reconnecting.
  4. Boosts are cancelled.
  5. The web is told about the rotation. This is best effort: if the web is down, the notice is kept and sent later, and seasons are identified by number so a late or repeated notice has the same result.
The confirmation text can be misleading

The confirmation screen of the language files that ship with 1.4.0 still says stats and history are archived to the web and the local database is emptied, and the "season complete" message says local match history was reset. That describes the old reset. The 1.4.0 rotation does not copy or delete anything, as described above. You can reword those texts in messages.yml of your language (see Messages and languages).

If the rotation fails, the queue is unlocked again and you are told the error. Nothing was changed except what had already been written, so you can retry.

The restart after a rotation#

By default the server restarts itself once the new season is open, so every player reconnects onto the new season with a clean in-memory state.

SettingDefaultWhat it does
season.restart-after-rotationtrueRestart the server after a rotation
season.restart-delay-seconds15Countdown players are warned with (0 to 300)

Change both in /epc → Settings → Seasons & replays (the entries Seasons ▸ Restart and Seasons ▸ Restart warning), or in config.yml.

With the restart on:

  1. The plugin delivers the web outbox, trying up to three times. If rows are still waiting, you get a message with the count; they are stored and sent after the restart.
  2. You get the "season complete" message and everybody online is warned, with the countdown.
  3. The queue stays locked during the countdown so nobody starts a match the restart would cut off.
  4. When the countdown ends, the plugin asks Spigot to restart, or stops the server if that is not available.

With the restart off, the queue opens again as soon as the new season is written and play continues on the new season, without any restart.

Bringing the server back is up to your host

restart only relaunches the server when restart-script in spigot.yml points at a working start script. Otherwise the server stops cleanly, and something outside Minecraft (your panel, systemd, a container supervisor) has to start it again.

Check that it works#

  1. Look at the current season in Data management → New season, then run the rotation.
  2. After the restart, join and open your stats: counts are zero and the rating is the starting one. The lifetime stats and match history still show your old matches.
  3. The next time you open New season, it offers the season after.

Going further#

  • To wipe only the current season's numbers without opening a new season, use Clear all stats (or Clear kit stats) in Data management. That deletes rows and cannot be undone: see Stats.
  • To only reset ratings, use Reset all ELO or Reset kit ELO in the same menu: see ELO and ranks.
Technical details

Stat tables:

TierTableAfter a rotation
Seasonpractice_player_season_statsNew season starts with no rows
Lifetimepractice_player_lifetime_statsKept
Match historypractice_match_historyKept, with the season number

A rotation writes three things, in this order: the closed season row, the new season row, and the mirror of the current season number in the shared settings row. A crash between them is repaired on the next boot.

Repair on boot. The plugin resolves the active season on every start:

  • No season at all (fresh install): season 1 is created.
  • Several marked active (a rotation cut off half way): the highest number wins and the others are closed, with a warning in the console naming each.
  • Every season closed (a rotation that stopped between closing and opening): the newest is reopened instead of inventing a number.

Stats are not written until the season is known, so nothing is stamped with a guess. Data from before seasons existed is moved into season 1 once, on first boot.

The web notice goes to /api/ingest/season/rotate through the outbox. A pre-restart delivery that cannot finish is not fatal: the outbox is durable and retries after the restart.

effects.season-progress-bossbar exists in the language's messages.yml with %phase% and %percent%, but the 1.4.0 rotation does not show it, because nothing runs long enough to need a progress bar.

Something missing on this page? Tell us on Discord