SignCommand — Command Signs with Confirmation GUI

Write a command on a sign, and players run it with a single Shift + Left Click. Before anything happens, a GUI shows them exactly which command is about to run — one click to confirm, one to cancel.

Every command runs with the clicking player's own permissions, never the console's. No privilege escalation, no hidden commands, no database, no dependencies. Drop the jar in and it works.

✨ Features

• Shift + Left Click to run — any sign with a line starting with / becomes a command sign. Normal left/right clicks keep their vanilla behavior, and signs without a command are never touched.
• Confirmation GUI — the full command is displayed before execution with clear Run / Cancel buttons.
• Runs as the player — commands execute with the player's own permissions. If they can't type it, they can't sign-click it.
• Respects other plugins — sign commands go through the same pre-process event as typed commands, so combat-tag blocking, jails, WorldGuard blocked-cmds and similar restrictions apply exactly as usual.
• Long commands — lines after the first are joined together until an empty line, so long commands wrap across the sign.
• Both sign sides — on 1.20+ the side the player is looking at is read.
• Snapshot execution — the command is captured when the GUI opens; editing the sign while the GUI is open changes nothing.
• Anti-disguise — color codes, zero-width and control characters are stripped, so what the GUI shows is always what runs.
• Creation permission — only players with the create permission can write signs starting with /. Everyone else is blocked at sign edit time.
• Blacklist — commands that must never run from a sign (op, stop, reload, ...) are configurable.
• Cooldown — per-player cooldown against macro spam, with a bypass permission.
• Execution log — who ran what from which sign, to console and/or a daily log file. Fully switchable.
• Language system — English & Korean bundled; every message and GUI label is editable, and you can add your own language file.
• Lightweight — no database, no external libraries, no commands to register. Event-driven only.

Writing a Command Sign

Any player with the create permission (default: OP) writes the command on the sign:

Long command? Keep writing on the next line — lines are joined as-is until an empty line:

Lines after the empty line are free text and are ignored by the plugin.

✅ Confirmation GUI

1. The player sneaks and left-clicks the sign.
2. A GUI opens showing the exact command that will run.
3. Run (green) executes it with the player's permissions. Cancel (red) or ESC aborts.

Permissions

• dotori.signcmd.use — run command signs (default: true)
• dotori.signcmd.create — create command signs (default: op)
• dotori.signcmd.bypass — bypass the cooldown (default: op)

There are no commands to learn — the plugin works entirely through signs.

Security Notes

• Commands are dispatched as the clicking player. The plugin never uses console or elevated permissions.
• The command permission is checked before the GUI opens, and the pre-process event is fired before execution, so any plugin that restricts typed commands restricts sign commands too.
• The blacklist is an extra safety net for admins clicking signs — keep it populated.
• Only players with the create permission can place signs starting with /. Consider waxing important signs with a honeycomb so they can't be edited.

Language & Customization

Set the language option in the config ( en by default, ko bundled). Language files are extracted to the plugin's lang folder — edit any message or GUI label, or create your own file (e.g. lang/de.yml). Missing keys fall back to English.

Compatibility

• Server: Paper and Paper forks (Purpur, Pufferfish, ...) — 1.19 to latest (recommended: 1.21.x). Plain Spigot is not supported (the plugin uses Paper's text component API).
• Java: 17+
• Dependencies: none — fully standalone, no database
• On 1.19 only the front side of a sign is read; everything else works the same.

Installation

1. Drop the jar into your plugins folder and restart.
2. Write a sign starting with / as an OP (or grant the create permission).
3. Done — tweak the config if you want (cooldown, blacklist, logging, language).

Questions or issues? Please use the discussion thread before leaving a review — I'm happy to help!