How to shut down a Minecraft server safely

The right way

From the console, with no slash:

stop

In game, as an operator with level 4:

/stop

The server then disconnects everyone with a message, saves every loaded chunk, writes player data, flushes plugin databases, calls each plugin's disable handler and exits. On a large world that can take anywhere from a second to a minute. Wait for the process to exit on its own.

Why killing the process is different

Minecraft holds chunks in memory and writes them back in batches. Everything since the last autosave lives only in RAM. Killing the process throws that away, which at best loses a few minutes of building and at worst leaves a region file half written and unreadable.

Plugins make it worse. An economy plugin that flushes balances on shutdown never gets to, so the last session of transactions is gone and players notice immediately.

If you must force it, run save-all flush first and wait for it to report finished. That gets the world to disk even if the plugins do not get their turn.

Warning players first

Sudden disconnects cost you players. Give a countdown, either by hand or with a restart plugin that broadcasts one automatically:

say Restarting in 60 seconds
save-all
stop

Running save-all before stop is not strictly required, since stop saves anyway. It is useful because it does the slow part while people are still connected, so the actual stop is quicker and the window where something can go wrong is shorter.

Scheduled restarts

Most servers restart daily. It clears memory that has fragmented, resets anything that has slowly leaked, and gives you a predictable window for backups. Pick the quietest hour, announce it in the message of the day, and keep it at the same time so regulars plan around it.

Run the restart from a wrapper script or your host's scheduler rather than a plugin that calls /stop and hopes something starts it again. If the server exits and nothing brings it back, you find out from your players.

Take the backup after the stop and before the start, when nothing is holding files open. Our world reset guide covers the backup command itself.

Checking it really stopped

A stopped server should leave no process and no listening port. If your panel says stopped but players can still connect, you have two copies running, which will corrupt the world quickly as both write to it.

The status checker tells you whether an address is still answering from outside, which is the quickest way to confirm a shutdown actually took.