BetterPunish¶
Moderation for Paper servers
BetterPunish brings punishments, evidence, reports, chat protection, staff investigation, and moderation logs into one plugin. It works with local YAML storage out of the box and can optionally synchronize selected data with Supabase, LuckPerms, Vulcan, and a Discord companion service.
Version requirements
Stable support covers Paper 1.21.11, 26.1, and 26.2. Use Java 21 for Paper 1.21.11 and Java 25 for Paper 26.1 or newer. Paper 26.3 has passed preview startup testing on an alpha build but is not yet a stable support claim. Spigot is not supported.
-
Punishment management
Apply bans, mutes, shadowmutes, warnings, and kicks; revoke active sanctions; retain searchable history; and attach evidence.
-
Moderator dashboard
Browse active, recent, expired, revoked, and type-specific records. Search players, inspect details, edit records, and confirm removals.
-
Reports and investigations
Process player reports, freeze online players, keep staff notes, inspect player profiles, find linked accounts, and review Vulcan signals.
-
Chat protection
Block configured patterns after normalization, detect duplicate-message spam, review flags in a GUI, and enforce mute and shadowmute behavior.
-
Moderation logging
Store player commands and recognized private-message commands locally, query recent entries, or monitor them live in game.
-
Optional integrations
Synchronize selected records with Supabase, mirror regular mute state to LuckPerms, consume Vulcan flags, or send events to a Discord companion endpoint.
Start here¶
- Installation — requirements, compatibility, and first startup.
- Compatibility — stable versions, Java requirements, and exact verification scope.
- Quick start — apply a first punishment and open the dashboard.
- Configuration — the options that materially change behavior.
- Commands — complete command syntax and aliases.
- Permissions — command and runtime permission nodes.
Sensitive moderation data
BetterPunish can store private messages, command text, staff notes, reports, and IP-derived account links. Restrict access to the plugin data directory, Supabase project, console logs, and logging commands. Define a retention and disclosure policy that fits your community and local law.