Player management
op and deop grant and revoke administrative status; whitelist add and remove control the guest list; kick, ban, and pardon handle problem players. gamemode and tp are the commands you will use most once a group starts playing together.
These are the commands to learn first, because they are the ones you reach for while players are waiting.
World and time control
time set, weather clear, difficulty, and gamerule let you shape the world without editing files. gamerule is the quiet powerhouse: keepInventory for a friendly server, doDaylightCycle to freeze time during a build event.
Save your choices in server.properties where possible, so they survive a world reset and are visible to the next person who reads the config.
Diagnostics
list shows who is online; seed reveals the world seed; save-all forces a world write before a backup; and tps or the panel graph tells you how loaded the server is. On vanilla, deeper diagnostics come from /debug rather than a built-in profiler.
Running save-all immediately before a manual backup is the habit that turns a risky copy into a safe one.
Commands to treat with care
stop ends the server cleanly and is the only correct way to shut down. kill wipes entities, including named mobs players care about. fill and clone can rewrite large regions instantly, and a mistyped coordinate has no undo.
At level 4 the dangerous set is larger, which is the argument for keeping most staff at level 3. Nothing here is recoverable without a backup.
FAQ
Common questions
What is the difference between a command and a gamerule?
Commands are one-off actions such as teleporting or banning. Gamerules are persistent world settings that change how the game behaves, like whether mobs can grief blocks, and they stay in effect until changed.
Do I need to be an operator to use commands?
For vanilla administrative commands, yes — each one requires a specific operator level. Plugin servers use permission nodes instead, so players can be given a single command without becoming operators at all.
