Minecraft Server Admin Guide: Op, Permissions and Essential Commands
On this page
Once your server is running, the difference between a smooth community and a chaotic one is knowing the admin tools. This is the practical reference: how to make yourself an operator, the commands you will actually use, how to control who joins, and how to hand out staff powers without giving everyone the keys.
It covers vanilla admin (op and commands, which work on any server) and the step up to real permission ranks on Paper with LuckPerms — plus how a hosting panel turns most of this into a click.
Make yourself an operator (op)
An operator (op) is a full admin — they can run every command. On a fresh server you op yourself first, from the console (which always has admin rights), not from in-game:
- Open the server console. Self-hosted, that is the window running the server; on hosting, the web console in your panel.
- Op your account. Type
op YourUsername. The player is added toops.jsonand can now use admin commands in-game. - Remove op when needed.
deop YourUsernametakes it away again.
The essential admin commands
These are the commands you will reach for constantly. Run them from the console (no slash) or in-game as an op (with the slash):
| Command | Does |
|---|---|
/gamemode survival|creative|spectator <player> | Change a player's game mode |
/tp <player> <target> | Teleport a player to another player or coordinates |
/give <player> <item> <count> | Give items |
/time set day|night | Set the time of day |
/weather clear|rain | Change the weather |
/difficulty peaceful|easy|normal|hard | Set difficulty |
/gamerule <rule> <value> | Toggle rules (keepInventory, doDaylightCycle, mobGriefing…) |
/whitelist on|add|remove | Control who may join (see below) |
/save-all | Force-save the world (before risky changes) |
/stop | Cleanly shut the server down (console) |
/gamerule keepInventory true stops players dropping their items on death — a popular quality-of-life setting for friendly servers.Run every command from a live web console — a HytHost Minecraft server makes op, whitelist and backups one click.
See Minecraft plansWhitelisting and op permission levels
Whitelisting is the single best protection for a private server — only listed players can join:
- Turn it on:
/whitelist on(or setwhite-list=trueinserver.properties). - Add players:
/whitelist add TheirUsername; remove with/whitelist remove. - Keep
online-mode=trueso usernames are verified against real accounts — turning it off lets anyone impersonate your players and admins.
Op itself has four levels, set by op-permission-level in server.properties (default 4):
- Level 1 — bypass spawn protection.
- Level 2 — most cheat commands (
/gamemode,/give,/tp) and command blocks. - Level 3 — player management (
/ban,/kick,/op). - Level 4 — everything, including
/stop.
Real staff ranks: permissions beyond op
For anything public, op is too blunt — you do not want a helper able to /stop the server. The answer is a permissions plugin, which needs a Paper or Spigot server (see best Minecraft server software).
LuckPerms is the standard. It lets you create ranks (Helper, Mod, Admin) and grant each exactly the commands and permissions it should have — nothing more. Install it like any plugin (see installing plugins), then define groups and assign players. Most other plugins hook into it, so a permission you grant in LuckPerms controls protection, chat, homes and the rest from one place.
The rule of thumb: op for yourself, LuckPerms for your staff. That keeps the server safe while still delegating day-to-day moderation.
Moderation: kicks, bans and spawn protection
The tools for keeping order:
- Kick —
/kick <player> <reason>removes someone for now; they can rejoin. - Ban —
/ban <player> <reason>blocks the account;/ban-ipblocks the address for ban-evaders. Reverse either with/pardon(and/pardon-ip). Bans live inbanned-players.json. - Spawn protection —
spawn-protectioninserver.propertiessets a radius around spawn that only ops can build in; set it to0to disable. - Keep an eye on the log. The console and log files record joins, chat and commands — invaluable when working out who did what.
On a public server, pair these with a protection plugin (like a claim or anti-grief plugin) so players can secure their own builds without an admin refereeing every dispute.
Admin the easy way on hosting
A hosting panel turns most of this into point-and-click. On a HytHost Minecraft server you get a live web console to run any command, one-click whitelist and player management, editable server.properties and ops.json, scheduled restarts and one-click backups before you experiment, and sub-user logins so your staff manage the server without your account password. The commands above still work exactly the same — you just have a friendlier way to run them, from anywhere, with the server online at a target of 99.9% uptime.
Frequently asked questions
From the server console (self-hosted: the server window; hosted: the panel's web console), type op YourUsername. That adds you to ops.json and gives you full admin commands in-game. Remove op later with deop YourUsername. You op the first admin from the console because the console always has admin rights.
There are four, set by op-permission-level in server.properties (default 4): level 1 bypasses spawn protection; level 2 adds cheat commands and command blocks; level 3 adds player management like /ban and /kick; level 4 grants everything, including /stop.
Op is all-or-nothing — an operator can run every command, including stopping the server. A permissions plugin like LuckPerms (on Paper or Spigot) lets you create ranks and grant each one only the specific commands it needs. Use op for yourself and trusted co-owners; use LuckPerms for staff so a helper cannot do more than moderate.
Turn it on with /whitelist on (or white-list=true in server.properties), then add players with /whitelist add TheirUsername and remove them with /whitelist remove. Keep online-mode=true so usernames are verified — otherwise the whitelist can be bypassed by impersonation.
Kick removes someone temporarily: /kick <player> <reason>. Ban blocks the account: /ban <player> <reason>, or /ban-ip to block the address of a repeat evader. Undo either with /pardon (or /pardon-ip). Bans are stored in banned-players.json.
Run /gamerule keepInventory true. It is the most popular gamerule for friendly servers — players keep their inventory and XP on death. Game rules are toggled the same way for many behaviours (doDaylightCycle, mobGriefing, and more).
Admin your server from one panel
A HytHost Minecraft server gives you a live console, one-click whitelist and backups, editable configs and staff sub-users — every command in this guide, made point-and-click.
Live chat 8 AM – 11 PM (Chișinău time) · tickets answered during business hours
