The /systemproxy command family (reload, status, test, help) with its two permission nodes — the complete command surface of the plugin.
System Velocity keeps its command surface deliberately small: one command family with four subcommands, guarded by one admin permission, plus one non-command permission for alert recipients. There are no player-facing commands at all — everything here is proxy administration. Commands execute on the proxy, so they are available from the Velocity console and to connected players who hold the permission.
| Command | Permission | What it does |
|---|---|---|
/systemproxy (aliases /sp, /sysproxy) — no args | systemproxy.admin | Prints the help header, lines and footer |
/systemproxy reload | systemproxy.admin | Atomically reloads config.yml + messages.yml, reschedules the daily restart and refreshes the log-cleaner schedule. An active restart countdown is preserved, never cancelled |
/systemproxy status | systemproxy.admin | Shows the enabled/disabled state of all five filters, the max message length, the daily restart time and timezone, and the log-cleaner state |
/systemproxy test | systemproxy.admin | Runs the built-in self-tests: six Log4Shell cases and four Unicode cases with per-case PASS/FAIL and a summary |
/systemproxy help | systemproxy.admin | Prints the help output (same as running the root command with no arguments) |
| *(receive alerts)* | systemproxy.alerts | Not a command: players with this permission receive the broadcast alert when alerts.broadcast is enabled |
${} obfuscations) and four Unicode cases run through the real pipeline, with {pass}/{fail} counts at the end.systemproxy.admin so the command family is invisible to everyone else.Two permission nodes cover everything. systemproxy.admin governs all subcommands including tab completion; systemproxy.alerts marks the recipients of violation broadcast alerts and nothing else. Both default to console-only unless a permissions plugin grants them — a player without the node never even sees the commands exist, because permission checks happen at the Velocity layer. Grant systemproxy.admin only to proxy administrators; systemproxy.alerts can go to any staff member who should watch the alert stream.
Warning:A manual restart command is deliberately absent from the plugin: the managed restart path belongs to the daily scheduler and the proxy's own restart tooling. /systemproxy reload is the only state-changing command — and it cannot cancel a countdown that is already running.
Tip:Make /systemproxy test part of your change routine: after any edit to filter thresholds or kick settings, run it and expect a clean six-plus-four PASS summary before you consider the change deployed.