Staff Deck: your moderators can't punish each other.

Two of your moderators are on the same rank. Which one can punish the other?

With Staff Deck: neither. Every staff member gets one level number, and that number decides who can punish or freeze whom, including other staff.

176 assertions · 0 failures · Paper + Purpur · no network calls, ever · no licence key · one jar, no dependencies

Your hierarchy actually holds

• A staff member may never punish or freeze an equal or higher level. Two moderators on level 10 cannot touch each other. Set punishments.allow-equal-level: true for the looser behaviour; it ships off.
• A vanished staff member is visible only to equal or higher levels, in the roster and in /list. A junior moderator gets the same answer a stranger does.
• Demote someone while they are in staff mode and staff mode ends immediately, with their own things returned. They do not have to be online for it to take.

The console is never subject to the hierarchy.

Vanish that also empties your slot

Vanish hides a staff member from /list, from join and quit messages, from the staff roster, and from the server-list player count. No sound is suppressed under vanish; footsteps and other movement sound still reach other clients because this plugin does not rewrite packets.

Punishments you do not have to babysit

A duration on ban and mute; a reason on all four. Mutes and warnings are written to disk and survive a restart, and a mute whose time has run out reads back as expired rather than as never set. /history <player> prints a player's punishment record.

Configuration, without a text editor

Configuration appears at plugins/StaffDeck/config.yml and plugins/StaffDeck/lang_*.yml after the first start.

config.yml is generated from the code that reads it, so there is no setting in the file that nothing acts on and no setting in the plugin that is missing from the file.

Change anything with /staffdeck set <setting> <value>. It edits config.yml in place and validates through the same loader that reads the file. /staffdeck reload re-reads everything without restarting the server.

A bad value is reported by its key and its line number and the default is used instead. The plugin never refuses to start over a typo, because that would take your moderation offline.

Any module can be switched off without removing the jar: modules.vanish, modules.punishments, modules.staffmode, modules.roster, modules.staffchat, modules.freeze, modules.invsee.

What it does

• /vanish [player]
• /staffmode (/sm) swaps inventory, armour, XP, location, game mode, flight and hunger for the staff loadout, and gives all of it back on the way out.
• /staff, the staff roster window: who is staff, who is online, who is hidden, who is in staff mode.
• /staffchat <msg> (/sc), a line to staff only. With no message it toggles, and everything typed goes to staff chat.
• /freeze <player>
• /invsee <player>
• /ban <player> [10m|2h|7d|perm] [reason], /mute the same. A duration is optional. /kick <player> [reason] and /warn <player> [reason] take no duration. /unban and /unmute.
• /history <player>, a player's punishment record.
• /staffdeck: version, the server build this jar was tested on, the configuration state, and which modules are on.

Per-staff languages

lang_en.yml ships complete; lang_es.yml and lang_de.yml ship with the lines a staff member actually sees translated. This is in the base price.

Tested before it goes out

Every release is compiled and run against a real server before it goes out. This build: 176 assertions passed, 0 failures. That is 88 on Paper 26.3 build 175 and 88 on Purpur 26.3 build 2647. /staffdeck prints the build it was tested on, so the claim can be checked without taking anyone's word for it.

What that number is and is not: every assertion is a service-level call over synthetic UUIDs, a real Bukkit event fired into a production listener, or a console dispatch. No client connects to the test server, so what a client renders is outside the claim: the tab list, the roster window on screen, a restored inventory on a live player, what a frozen player can and cannot do. /staffdeck lang <code> ships and is not among the 176: it needs a connected player and the test server has none.

Rebuilt from commit fc773dab with the same JDK and the same dependency jars, release/StaffDeck.jar comes out byte for byte identical; its sha256 is below.

What it does not do

Named here rather than discovered after the purchase.

• No Folia, no BungeeCord or Velocity proxy, no Geyser or Bedrock. Paper and Purpur are tested. Spigot is untested, so it is not claimed.
• No punishment GUI, no analytics, no Discord webhook, no alt detection, no cheat detection.
• No licence key, no account, no paid extras, and no network call: no key server, no obfuscation, no database, no protocol library, no economy hook, and no companion plugin. The jar never contacts anything, including us.
• Nothing client-side. No resource pack, and nothing for players to install.

Requirements

• Paper or Purpur. Tested on Paper 26.3 build 175 and Purpur 26.3 build 2647; the manifest declares api-version: 1.21, which is the floor it will load on rather than a version it was tested on.
• Java 25
• No other plugin, library or service

The file

StaffDeck.jar: 103,438 bytes
sha256 ae6d6b8107090ed29dfdeaa769c38e2f308a2a118a4a2aa913d6d31cd3b1f7b3

$2.99, one payment. Pay on this page and itch.io hands you StaffDeck.jar immediately — stop the server, drop the jar into plugins/, start it.

Staff Deck is not an official Minecraft product. It is not approved by or associated with Mojang or Microsoft.