Installation

Requires Java 21 or newer and the supplied WrongPunish plugin JAR.

1. Place the JAR in each backend's plugins folder. Use Paper, Purpur or Folia 1.21.11. Older 1.21 releases are not certified.
2. Optionally install the same JAR on Velocity 3.4+ or BungeeCord 1.21. Each platform reads its own entry point.
3. Start once to generate config.yml, templates.yml, webhooks.yml, locale/EN.yml and ten files under guis/.
4. Set a unique network.server-name per node. Use the proxy's actual backend names for scopes and groups. For a network, configure the same MySQL/MariaDB database and table prefix on every node.
5. Configure staff permissions, preferably with LuckPerms. Backend operators receive command, bundled-template and notification permissions by default. Ordinary players can inspect their own /warnings. The wildcard and punishment exemptions/bypasses require explicit grants. An explicit LuckPerms denial overrides an individual operator default; console is highest authority.
6. Restart for initial setup. /wrongpunish reload validates the main configuration, templates, webhooks, selected locale and every GUI file before applying changes. Open GUIs close on a successful reload. Database pools are reused when their settings are unchanged.

SQLite is for a standalone server. Do not share SQLite files over a network filesystem. MySQL/MariaDB tables use InnoDB and utf8mb4.

The plugin uses platform-authenticated UUIDs and platform-provided addresses. It does not decode its own forwarding protocol. Configure Velocity modern forwarding (opens in a new tab) and protect backend access. Bungee forwarding likewise requires protected backend ports. Leave online-mode: true for a properly authenticated proxy network even though backend server.properties may use offline mode.

Install the backend adapter on every backend for normal chat and backend command mutes. Modern signed chat must be cancelled at the backend. The proxy adapters enforce login/transfer bans, kicks, lockdown and proxy commands. They intentionally do not cancel signed normal chat at the proxy. broadcasts.delivery: BACKEND prevents duplicate broadcasts and warning messages when both adapters are installed. Use PROXY for proxy-delivered notices, or ALL to explicitly allow both.

Setup checklist

• Verify Java 21+ on every node.
• Install the supplied WrongPunish JAR.
• Confirm every backend generates its configuration.
• Assign unique node names and shared MySQL settings for networks.
• Test a mute from a non-exempt player account.
• Follow the staging checklist before deployment.