OPs, whitelist, bans

Admin permissions and access control.

Quick reference for the admin-side commands.

Making someone an operator (OP)

From the panel console (or in-game with /op if you're already OP):

code
op PlayerName

OPs can run admin commands. To revoke:

code
deop PlayerName

OP levels (1–4) can be set in server.properties (op-permission-level). Default is 4 (full).

Whitelist

A whitelist makes the server private — only listed players can join.

Enable:

CSHARP
whitelist on

Add players:

CSHARP
whitelist add PlayerName

Remove:

ARDUINO
whitelist remove PlayerName

Show the list:

code
whitelist list

Disable entirely:

VBNET
whitelist off

Bans

Ban a player by name:

ARDUINO
ban PlayerName Reason text here

Pardon (unban):

code
pardon PlayerName

IP-level ban:

code
ban-ip 198.51.100.42

Kick (temporary)

ARDUINO
kick PlayerName Cool down a bit

Player is disconnected. Can rejoin immediately.

Online mode

server.properties:

  • online-mode=true — requires Mojang authentication (default; recommended)
  • online-mode=false — allows cracked clients (only use this if you really mean to)

Cracked servers are a magnet for griefers and stolen accounts. Don't do it unless you have a specific reason and a tight whitelist.

Per-player permissions

For finer control than OP/non-OP, install LuckPerms (a permissions plugin). Lets you create groups (admin, mod, vip, default) with specific permissions, assign players to groups, and grant/revoke individual permissions.