Unhacked

Paper plugin that detects client sided mods using sign components, then optionally kicks or bans the player.

How it works

Each mod check maps to a resource-pack translation key rendered on a sign sent only to the checked player. The client's response responds whether the mod's client-side key overrides the sign text. A mismatch means the mod is present.

Requirements

• Paper 1.21.x server, Java 21
• packetevents
• PacketBlocks

Commands

All under /unhacked (permission unhacked.use):

Command	Permission	Description
/unhacked check <player> [mod1 mod2 ...]	unhacked.check	Run a check on a player. Remove mods to use default-check-mods.
/unhacked reload	unhacked.reload	Reload config.yml.
/unhacked loglevel [level]	unhacked.loglevel	View/set your own log verbosity.

unhacked.echo-results (default: op) gates who receives detection notifications.

Configuration

See src/main/resources/config.yml:

• mods - registry of checkable mods: display-name, key, mode, and per-result execute-on console commands (supports {player}/{mod} placeholders; run your ban/kick command here).
• default-check-mods - mods used when /unhacked check <player> is run with no mod list.
• join-check - auto-check players on join (enabled, only-first-join, delay in ticks, mods).
• timeout - ticks to wait for a client's sign packet response before marking the check as skipped (and executing the punishment).
• messages - all messages a user might see.