Minecraft OP Commands Guide (2026)

OP (operator) status gives players admin powers on a Minecraft server. There are four permission levels, each granting different commands.
How to OP a Player
From Console
op PlayerName
In-Game (as OP)
/op PlayerName
De-OP
/deop PlayerName
Permission Levels
| Level | Can Do | Example Role |
|---|---|---|
| 1 | Bypass spawn protection | Moderator (light) |
| 2 | Use cheat commands (gamemode, give, tp) | Moderator |
| 3 | Use server management (/ban, /kick, /op) | Admin |
| 4 | Use /stop, /save-all, full access | Owner |
Set the default OP level in server.properties:
op-permission-level=4
Essential Admin Commands
Player Management
| Command | Level | Description |
|---|---|---|
| /kick Player reason | 3 | Kick a player |
| /ban Player reason | 3 | Permanently ban |
| /ban-ip IP | 3 | Ban by IP address |
| /pardon Player | 3 | Unban a player |
| /whitelist add Player | 3 | Add to whitelist |
| /whitelist remove Player | 3 | Remove from whitelist |
Gameplay Commands
| Command | Level | Description |
|---|---|---|
| /gamemode survival Player | 2 | Change player gamemode |
| /give Player item count | 2 | Give items |
| /tp Player1 Player2 | 2 | Teleport players |
| /time set day | 2 | Change time |
| /weather clear | 2 | Change weather |
| /gamerule keepInventory true | 2 | Change game rules |
| /effect give Player effect | 2 | Apply potion effects |
| /enchant Player enchantment level | 2 | Enchant held item |
Server Management
| Command | Level | Description |
|---|---|---|
| /stop | 4 | Shut down server |
| /save-all | 4 | Force world save |
| /save-off | 4 | Disable auto-save |
| /save-on | 4 | Enable auto-save |
| /reload | 3 | Reload data packs |
| /seed | 2 | Show world seed |
ops.json
OP status is stored in ops.json in the server root:
[
{
"uuid": "player-uuid",
"name": "PlayerName",
"level": 4,
"bypassesPlayerLimit": false
}
]
You can edit this file directly to set specific permission levels per player.
Best Practices
- Give yourself level 4 (full access)
- Give trusted admins level 3
- Give moderators level 2
- Avoid giving OP to regular players
- Use a permissions plugin (LuckPerms) for fine-grained control instead of OP
- OP is all-or-nothing per level. Permissions plugins let you grant specific commands
Admin your server. View Minecraft Hosting Plans
Quick 2026 Answer
Minecraft OP Commands Guide (2026) should be treated as a practical server setup problem, not only a settings page. Start with a small test server, change one setting at a time, and write down what changed before inviting players. That makes it much easier to fix lag, crashes or player complaints later.
Setup Checklist
- Match the Minecraft version, loader and plugin versions before testing.
- Keep a backup of the world and config folder before each change.
- Test with two or three players before opening the server to everyone.
- Watch console warnings for five minutes after startup.
- Keep view distance, simulation distance and plugin count sensible for the plan.
- Move to stronger hosting only after you know which part is actually limiting the server.
Common Beginner Mistakes
The most common mistake is changing too many things at once. A plugin update, a new datapack, a view distance change and a Java flag change can all cause different symptoms. If the server gets worse, you will not know which change caused it.
Another mistake is looking only at RAM. Minecraft also needs fast single core CPU speed and quick storage. A server with plenty of RAM can still lag if one thread is busy with entities, redstone, chunk loading or a heavy plugin.
Where to Go Next
For sizing and plan choice, use Minecraft hosting, Minecraft server requirements, Minecraft lag fixes. If this page helps, the best supporting screenshot is a before and after view of the setting being changed, plus a console or Spark screenshot showing that the server stayed stable after the change.
Real Test Routine
The easiest way to prove Minecraft OP Commands Guide (2026) is working is to test it on a copy before changing the live server. Make one controlled change, restart, join the server and watch the console. If the setting helps, write it down. If it makes the server worse, roll back immediately and try a smaller change.
Use a simple test loop. First, start the server with the old settings and note the player count, TPS, RAM use and console warnings. Second, change only one setting. Third, restart and repeat the same activity, such as flying through new chunks, loading a busy base or running the plugin command that normally causes trouble. This gives you a fair comparison instead of a guess.
For most small servers, the best first fixes are lower simulation distance, fewer heavy plugins, clean backups and enough CPU headroom. RAM helps when the server is genuinely running out of memory, but it will not fix a plugin that runs slow code every tick.
When to Move to Better Hosting
Move hosting only when the test shows the server is limited by CPU, disk or network instead of a bad config. Signs include TPS drops during normal play, slow chunk generation on an optimized server, console warnings under light load and players in one region getting constant ping spikes. If the same world runs fine on a local test but struggles online, hosting quality is likely part of the problem.
Screenshot or Generated Image Target
A useful supporting image for this page should show the actual setting, console, panel or workflow being discussed. Avoid a generic stock image if possible. A simple generated diagram is fine when it explains the flow better than a screenshot.
- Capture the main settings screen or config file.
- Add one close crop of the important value.
- Add one result screenshot after the fix or setup is working.
- Keep private IPs, tokens, emails and customer names hidden.
