Whitelist, ban and op: the server commands that behave differently than you expect
Whitelisting does not kick players already online, /ban needs a reason to be useful, and op level matters more than the op list. The details that bite server owners.
The admin commands look simple and mostly are. The failures come from three behaviours that are not obvious from the syntax.
Whitelist does not remove who is already in
/whitelist on starts enforcing the list from that moment. Anyone already connected stays connected, even if they are not on the list. The command that closes the gap:
/whitelist reloadreload re-reads whitelist.json and kicks connected players who are not on it. Turning the whitelist on and walking away is the classic mistake.
Two more details:
/whitelist add <name>resolves the name against Mojang's API, so it needs the server
to be online-mode and connected. Offline servers must edit whitelist.json by hand with the correct UUID.
- Operators bypass the whitelist by default, which is why your own account never
proves the whitelist works. Test with a second account.
/ban wants a reason, and /ban-ip is a different list
/ban <player> [reason]
/ban-ip <address|player> [reason]The reason is optional, and omitting it is a mistake — it is what the banned player sees, and it is what future-you reads in /banlist trying to remember why. Without one the entry just says "Banned by an operator".
/ban and /ban-ip write to separate files (banned-players.json, banned-ips.json). Pardoning one does not clear the other, which is the usual reason a "pardoned" player still cannot connect. Use /pardon and /pardon-ip both.
Op levels, not just the op list
/op grants level 4 by default, which is full access including /stop. The four levels are real and settable in server.properties via op-permission-level:
| Level | Grants |
|---|---|
| 1 | Bypass spawn protection |
| 2 | Most cheat commands, command blocks |
| 3 | Player management — kick, ban, op |
| 4 | Everything, including /stop |
Moderators who need /kick and /ban want level 3, not 4. Handing out level 4 to everyone who helps moderate is how servers get wiped by a compromised account.
function-permission-level is separate and controls what datapack functions may run — leaving it at 2 while op level is 4 is a common source of "my function does nothing".
The list commands
/banlist players, /banlist ips and plain /banlist all exist and print to console rather than chat if run from the server terminal. /whitelist list shows names only, not UUIDs — read whitelist.json when you need to check identity.
Build any of these with the arguments in the right order in the Server Admin Command Builder, which covers ban, ban-ip, pardon, kick, op, deop and whitelist from one form.