Using the console without breaking anything

Panel & Files Reviewed September 6, 2026 2 min read

Anything you type into the console runs with the server's own authority — above any player, above any operator. That is useful, and it is also why a typo here matters more than a typo in chat.

Console commands do not take a slash

In game you type /stop. In the console you type stop. Some servers accept the slash and quietly ignore it; others treat it as an unknown command. Leaving it off always works.

Commands worth knowing

CommandWhat it does
stopSaves and shuts down properly. The correct way to stop a server.
save-allWrites the world to disk right now, without stopping.
op <name>Grants operator. Do this from the console, never from a player asking nicely.
whitelist add <name>Adds someone to the allowlist without them being online.
listWho is connected right now.
reloadReloads configs. See the warning below before using it.
reload is a trap, not a shortcut

It re-reads plugin configs without restarting, which sounds ideal and frequently leaves plugins half-initialised — duplicate scheduled tasks, listeners registered twice, memory that never comes back. Most plugin developers ask people not to use it. Restart instead; it takes thirty seconds and it actually works.

Run save-all before anything risky

Before a restart, a plugin change, or an experiment, save-all means the last thing written to disk is the world as it is now. It costs a second and it is the difference between «we lost nothing» and «we lost the last twenty minutes».

Reading it when something breaks

Errors scroll past fast during startup. The useful part is almost always the first Caused by: line, not the last line on screen — everything below it is the failure propagating outward.

If the console is moving too fast to read, stop the server and start it again while watching. Startup is where most problems announce themselves.