Requirements (Velocity 3.3.0+, Java 21, nothing else), where the filter sits on your network, and the 1:1 build install with license activation.
SystemProxy-Velocity is the proxy-side member of the System family: a security and maintenance plugin for Velocity proxies. It filters malicious chat payloads before they reach your backend servers — including the Anti-Log4Shell filter that flattens nested obfuscation up to four levels deep — schedules automated daily restarts, and manages log file growth. One payment of EUR 5.00 unlocks the full proxy plugin with a permanent license, delivered as a personal 1:1 build.
| Requirement | Details |
|---|---|
| Java | Java 21 or newer |
| Proxy platform | Velocity 3.3.0 or newer |
| Runtime dependencies | None — no database, no Redis, no message channels; the only bundled library is a shaded, relocated YAML parser |
| Backend servers | Nothing to install — the chat pipeline acts on the proxy before traffic is forwarded |
The plugin runs on the Velocity proxy itself, in front of every backend server. That placement is the point of the product: hostile chat payloads are filtered at the proxy layer, so they never touch a backend at all; the daily restart scheduler keeps the proxy itself stable; and log rotation stops weeks of uptime from quietly filling the disk. The plugin handles exactly two player events — chat and disconnect — which is also a precise statement of its scope: it is a chat-security and maintenance tool, not a login, session or server-switching layer.
plugins/ folder of your Velocity proxy — not a backend server.plugins/systemproxy/ and copies config.yml and messages.yml into it; license verification happens at the Velocity proxy layer./systemproxy reload./systemproxy status — then prove the filters behave with /systemproxy test.Note:The plugin runs standalone on any Velocity 3.3.0+ proxy — no backend plugin of any kind is required. The security filter, restart scheduler and log management work whether your backends run System, something else, or nothing at all.
Warning:The license is bound per proxy with IP and hardware limits — the same protection story as every Nerotek product. If your proxy's IP or hardware changes, request a license reset through your DM (see the platform page Requesting a License Reset) instead of working around the binding.
Tip:First-boot checklist: /systemproxy status should list all five filters with their state, the restart time and timezone, and the log cleaner; /systemproxy test should end with six Log4Shell and four Unicode cases passed. That is the entire acceptance test.