Skip to main content
Each rank in Rep is defined by a score threshold in config.yml. When a player’s reputation score changes, Rep compares the new score against every threshold and assigns the matching rank.

What score-threshold means

Under ranks, each tier has three fields:
plugins/Rep/config.yml
The score-threshold is not a range. It is a boundary Rep uses to decide which single rank a player belongs to.

Assignment rules

Rep uses different logic for negative and non-negative scores: Scores 0 or higher: the player gets the highest rank whose threshold they meet (score >= threshold). Think of each positive threshold as the minimum score to enter that tier. Scores below 0: the player gets the smallest threshold T where score <= T. Think of each negative threshold as the upper bound of that negative band.

Worked examples

With the default rank ladder:

Default config example

plugins/Rep/config.yml

Rules for admins

  • List thresholds in ascending order (lowest to highest). Rep logs a warning if they are out of order.
  • You can add as many ranks as you need.
  • When a player crosses into a new rank, Rep can notify them, play sounds and particles, run rank reward commands, and refresh their chat/tab prefix.
  • Configure rank rewards under rank-rewards in Configuration.

What happens when a threshold is crossed

Where players see ranks and thresholds

Rank thresholds vs compact score formatting

placeholders.compact.thresholds in config controls number formatting for placeholders like %rep_score_compact% (when to show 1k, 1m, etc.). It does not affect rank assignment. Only ranks.*.score-threshold controls which rank a player has.

Next steps

  • Tune thresholds and prefixes in Configuration
  • Set up rank reward commands for tier changes
  • Use Placeholders to show rank and score in other plugins