Installation & Deployment
Deploying SecurityX is a fully automated process. Each network receives its own per-platform JAR with an embedded RSA license — no manual API keys required.
1 · Pick a platform
Spigot/Paper for game servers, Velocity or BungeeCord for your proxy. A single download covers the whole stack.
2 · Signed license
Each JAR carries a unique RSA signature (license.sx) injected at build time. Tampering disables the plugin instantly.
3 · Drop & forget
Place the JAR in /plugins. No manual key entry — the license is verified automatically on first boot.
How to get your JAR
Log in to the Dashboard → Servers, register your network and press Download Shielded JAR. You can also regenerate the license from here (24h cooldown between regenerations).
Proxy layer
Place the Velocity or BungeeCord build in the proxy's /plugins folder. This is the recommended spot to enable global bans.
Game nodes
Place the Spigot/Paper build on each backend server for local reporting and full sanction enforcement.
Once booted, the plugin sends a license-handshake to the API and starts a heartbeat every 5 minutes. A live ban-check runs every 20 seconds against all synced servers.
[SecurityX] SecurityX Spigot has been enabled with SecurityX Shield!
[SecurityX] Heartbeat: Active · Session token issued
To report players or enjoy same-network privileges, link your Minecraft account to your SecurityX profile. Two ways:
- A
In-game /sync
Run/syncinside the game (aliases:/link,/verify). The plugin prints a short sync code. - B
Enter the code on the web
Opensecurityx.sbs/sync, type the code and confirm. Codes are 6 characters, expire in 5 minutes and are single-use.
Bot-protection included
The link flow is protected by our anti-bot layer. The site may ask you to complete a quick math challenge or verify via the Discord Verify Account button before allowing the link.
License revoked?
Check the JAR is the exact one downloaded from the dashboard. Edited or renamed files with missing signatures are rejected.
License expired?
Regenerate your license from Dashboard → Servers (24h cooldown) and restart the server.