Skip to main content
This page covers how Rep Core behaves in gameplay. For config keys, see Configuration. For rank tier logic, see Ranks & thresholds.
Rep Pro adds evidence, anti-farm, and trust tiers on top of everything below. Redis, seasons, and an optional dashboard are secondary. See Rep Pro and Core vs Pro.

Giving and receiving reputation

Players give reputation through:
  • Profile GUI — open with /rep or /rep <player>, then use the plus/minus buttons
  • Commands/rep <player> plus or /rep <player> minus
  • Feeding — right-click another player while holding food (when feeding.enabled is true)
Receivers get notifications when notifications.notify-receiver-on-plus or notify-receiver-on-minus is enabled. Sounds and particles can play on give/receive and on rank changes. Cooldowns limit how often players can give rep:
  • cooldowns.global-command-cooldown — between any /rep use
  • cooldowns.player-specific-cooldown — before giving to the same target again
  • cooldowns.max-rep-per-day — daily cap on rep given (0 = unlimited)

Automatic reputation from events

Rep adjusts scores when players perform configured actions. Examples from the default config: Set any event to 0 to disable it. Full list is under event-changes in Configuration.

Per-mob reputation

mob-changes lets you reward or penalize hitting or killing specific mobs. Use Paper EntityType names:
mob-changes excerpt
hit-default and kill-default apply when a mob is not listed individually.

Feeding mechanic

When enabled, a player can right-click another player while holding food to transfer reputation:
feeding

Leaderboard

/rep top opens a paginated GUI for players showing the highest reputation scores. Console gets plain text output. The number of entries comes from general.leaderboard-size.

Rank rewards viewer

/rep rewards opens a GUI listing every rank, the score required to reach it, and whether the viewing player has unlocked it. Locked ranks show how many points are still needed.

Rank rewards on tier change

When rank-rewards.enabled is true, Rep runs console commands and optional server broadcasts when a player moves up or down a rank:
rank-rewards excerpt
Use {player} for the player name and {uuid} for their UUID. rankdown-commands runs on demotion — useful for LuckPerms group sync without re-granting item rewards.

Chat and tab display

Enable rank prefixes in chat and the tab list:
general
When enabled, the rank’s chat-prefix appears after the player name in chat or in the tab list.

Multi-language messages

Rep ships translations in plugins/Rep/lang/:
language
Available locales include en_US, es_ES, de_DE, fr_FR, zh_CN, ja_JP, pt_BR, and ru_RU.

Shared MySQL for multi-server setups

Rep Core supports MySQL storage so multiple servers can share one reputation database. Set storage.method: mysql on each instance and point them at the same database. See Installation for connection settings. Shared MySQL keeps reputation data consistent across backends. Each server still caches player records locally, so a score change on one server may not show on another until that cache refreshes (storage.mysql.cache-ttl-seconds). For cache-safe live sync — instant invalidation when any server mutates a score — use Rep Pro Redis sync. See Pro Redis sync.

GUIs

Rep includes profile, leaderboard, help, and rewards GUIs. Customize titles, border materials, items, and pagination under the gui section in Configuration.

Rep Pro features

Evidence

Who changed whom, when, and why — /rep history.

Anti-farm

Reciprocal +/+ block and hourly unique-receiver cap.

Trust tiers

Score bands with console commands on enter.

Rep Pro overview

License, pricing, Redis, seasons, optional dashboard.