Minecraft Server Ops and Permissions Guide
Vanilla op is four distinct permission levels, not a single on/off toggle — and knowing which level to grant matters more than most people realize.
Vanilla op — four levels, not a toggle
- Level 1: bypass spawn protection.
- Level 2: use most cheat commands (/gamemode, /give, /tp) and command blocks.
- Level 3: use /op, /deop, /ban, /whitelist — manage other players.
- Level 4: use /stop and other server-level admin commands.
- /op <name> grants level 4 by default; edit ops.json directly to set a lower level for a trusted-but-not-full-admin player.
Where op falls short
Vanilla op is all-or-nothing in practice — there's no 'can build in this region but can't kick players' granularity. The moment you want role-based access (moderator vs admin vs builder) you need a permissions plugin.
- LuckPerms (Paper/Spigot/Fabric) is the standard choice — group-based permissions, per-world overrides, a web editor.
- Permissions plugins require Paper, Spigot or Fabric, not vanilla, and typically also need a permission-aware plugin set to actually gate commands.
FAQ
What's the difference between op level 2 and 4?+
Level 2 covers most building and cheat commands; level 4 adds the ability to stop the server and manage bans, whitelist and other ops. Most 'trusted helper' players should get level 2, not full op.
Can I deop myself by accident?+
Yes — /deop <yourname> removes your own access immediately with no confirmation. Keep server or console access as a fallback.
Do I need a permissions plugin for a small friend server?+
Usually not — vanilla op levels are enough for a handful of trusted players. LuckPerms becomes worth it once you have public sign-ups or a staff hierarchy.
Manage ops and players from a panel, not the console
CoalHost's Players page handles op levels and whitelisting with a click.
View Minecraft Hosting →