ProxyBanSystem

# ProxyBanSystem Cross-platform MySQL ban and punishment system for Minecraft servers and networks. ProxyBanSystem is a cross-platform ban and punishment plugin for Minecraft networks. The same built JAR can run on proxy platforms and server platforms, while all active bans, lookup data, and registered player names are stored in one shared MySQL database. **PacketEvents only for Console Errors needed!** (https://modrinth.com/plugin/packetevents) ## Compatibility One JAR is designed to run on: - Velocity - BungeeCord - Waterfall - Spigot - Paper - Purpur - Folia - Leaf - Sponge Waterfall uses the BungeeCord loader. Spigot, Paper, Purpur, Folia, Leaf, and Bukkit-compatible forks use the Bukkit/Spigot loader. Folia support is marked with `folia-supported: true` in `plugin.yml`. ### Supported Minecraft Versions For non-proxy Bukkit-based servers, the plugin is built for one shared JAR across: - Minecraft Java `1.20.x` - Minecraft Java `1.21.x` - Minecraft Java `26.1.x` The Bukkit loader declares `api-version: '1.20'` and the project compiles against Spigot API `1.20.1-R0.1-SNAPSHOT`. This keeps the Bukkit-side API baseline low while still allowing newer Bukkit-compatible platforms such as Paper, Purpur, Folia, and Leaf to load the same JAR. Sponge support is provided through SpongeAPI `14.0.0`; use a Sponge server version that matches that API line. ## Features - Ban players by name or UUID - Unban players by name or UUID - Automatic login check for banned players - Automatic kick when an online player gets banned - Temporary and permanent bans - Fully configurable ban reasons with custom durations - Fallback ban reason for unknown/custom reasons - Customizable ban screen through `messages.yml` - Customizable plugin messages and formats - Built-in language switch with English as the default and German as an optional preset - Ban and unban broadcasts for staff members - Lookup system for ban status, UUID, ban count, unban count, reasons, executors, and history - Remove single ban reasons from a player's lookup history - Remove the full lookup history of a player - List all active bans - Whitelist players so they cannot be banned - MySQL player registry for offline lookups and tab completion - Local `bannedplayers.json` for additional stored history/display data - Reload commands for config and messages - Tab completion for players, ban reasons, and admin subcommands - Shared core logic for all supported platforms ## Installation 1. Build the project: ```powershell mvn clean package ``` 2. Put `target/proxybansystem-4.4.jar` into the correct plugin folder: - Velocity: proxy `plugins` folder - BungeeCord/Waterfall: proxy `plugins` folder - Spigot/Paper/Purpur/Folia/Leaf/Bukkit-compatible forks: server `plugins` folder - Sponge: Sponge `plugins` folder 3. Start the server or proxy once to generate the files. 4. Open `config.yml` and enter your MySQL connection data. 5. Restart the server/proxy or run `/adminpunish reload`. ## Requirements - Java 17 or newer bytecode support - Maven for building from source - MySQL database - A server or proxy running one of the supported platforms Use the Java runtime required by your server software. The plugin itself is compiled for Java 17 bytecode so it can also load on older 1.20.x server lines that still run on Java 17, while newer server versions can run it on their newer Java runtime. Minecraft Java 26.1.x servers require Java 25; the plugin can run on that newer runtime because Java runtimes are backward-compatible with Java 17 bytecode. The plugin automatically creates these MySQL tables when the connection works: - `bans` - `punishment_history` - `player_registry` ## Files ### `config.yml` Contains technical settings: - Prefix and ban title - Ban/unban broadcast prefixes - MySQL host, port, database, user, password, and JDBC parameters Default generated prefixes use the `»` separator and are written as UTF-8: ```yaml settings: prefix: "&8 &8» " ban-broadcast-prefix: "&c&lBAN &8» " unban-broadcast-prefix: "&a&lUNBAN &8» " ``` If an older generated config still uses the previous `>` separator for these exact default prefixes, the plugin normalizes it back to the `»` style at runtime. ### `messages.yml` Contains all user-facing and gameplay settings: - Active language selection - Command names - Subcommand names - Messages - Lookup formats - Ban screen format - Broadcast formats - Duration labels - Ban reasons - Whitelist Language is selected at the top of `messages.yml`: ```yaml settings: language: "en" ``` Available built-in values: - `en` for English - `de` for German English is the default. The language presets are stored under the `languages:` section, so server owners can edit both English and German text in one file. ### `bannedplayers.json` Stores additional local ban history/display data in the plugin data folder. Active bans are still stored in MySQL. ## Commands Command names c