Skip to main content
Reputation seasons let you run timed competitive periods with their own leaderboards. This is network proof, not the Pro hero feature. Evidence, anti-farm, and trust tiers are the reason to buy. Requires Rep Pro with a valid license and pro-settings.seasons-enabled: true (off by default).

Configuration

plugins/Rep/config.yml

Wipe vs carry-over

Wipe — every player’s reputation resets to start-score when the season ends. Best for clean competitive resets. Carry-over — each player keeps carry-over-percent of their current score (rounded), then the season restarts. Use this for softer resets where veterans retain some standing. Example with carry-over-percent: 25 and start-score: 0: a player with 400 rep ends the season with 100 rep.

Season lifecycle

  1. Start — a season is created with a unique ID and display name. auto-start: true begins the first season on boot; admins can also run /rep season start.
  2. Active play — all reputation changes count toward both the player’s overall score and their season score.
  3. End — when duration-days elapses or an admin runs /rep season end, Rep applies wipe or carry-over, archives results, and optionally sends a Discord webhook.
  4. Archive — season standings are stored for history. Admins can archive without immediately starting the next season via /rep season archive.
  5. Next season — after end (or manual start), a new season begins with a fresh ID and timer.

Commands

See Commands for the full command reference.

PlaceholderAPI

Season placeholders are available when seasons are enabled:
See Placeholders for the full list.

Discord webhook

When seasons.discord-webhook is set, Rep sends an embed to Discord when a season ends. The message typically includes the season name, duration, and top players. Leave the webhook URL empty to disable Discord notifications.