What you need
BungeeCord, Waterfall or a BungeeCord fork with API 1.16 or newer, and Java 21 or newer. If the proxy runs on an older Java, the console shows UnsupportedClassVersionError at startup.
Kordon goes on the proxy only. The Spigot or Paper servers behind it need nothing. The plugin recognises Bedrock players from Geyser and Floodgate by itself.
Installation
- Create an account and add your server in the panel.
- On the server's Plugin page, download
Kordon.jar. It already contains your server key. - Put the file into the proxy's
pluginsfolder, next to itsconfig.yml. - Restart the proxy.
The console prints a connection line, and within a minute the panel shows "Plugin is online":
Kordon connected to server "My Server". Mode: monitoring only. If Kordon is unavailable: let nobody in.The generic Kordon.jar from SpigotMC or Hangar is linked with a command in the proxy console, without a restart:
/kordon link <key>The server key works like a password. If the file or the key gets into the wrong hands, issue a new key in the panel and the old one stops working at once.
Command permissions
Without LuckPerms, permissions are set in BungeeCord's config.yml: the groups section puts a player into a group, and the permissions section lists what each group may do.
groups:
Steve:
- moderator
permissions:
moderator:
- kordon.command
- kordon.command.whitelist
- kordon.command.lookup
- kordon.notifyWith LuckPerms you do the same with a command:
/lpb user Steve permission set kordon.command trueEach command has its own permission: kordon.command.whitelist, kordon.command.blacklist, kordon.command.lookup, kordon.command.reload. The kordon.notify permission turns on Kordon's staff messages in chat. /kordon link is not part of the general permission, and it is best left to the owner. The long commands have short forms: /kordon wl and /kordon bl.
Several proxies
If your network has several BungeeCord instances, install the plugin on each one with the same file. The proxies show up in the panel by themselves, on the "Proxies" tab of the "Plugin" section. How many proxies are checked depends on your plan. Kordon does not serve proxies over the limit, and the panel shows this. The plugin there follows the "If the check is unavailable" setting, which by default does not let players in.
Moving to Velocity
PaperMC no longer develops Waterfall and recommends moving to Velocity. Kordon does not need to change when you move: put the same Kordon.jar into the new proxy's plugins folder. All settings, lists and the login log are stored in the panel and stay where they are.
If you linked the plugin with a command, also copy the plugins/Kordon folder with the key file, or run /kordon link again on the new proxy. While both proxies are running, each one counts toward your plan's limit. On a plan with one proxy the second one will be over the limit, so shut the old proxy down before you move players, or choose in the panel which proxy counts. For permissions on Velocity, see the Velocity guide.