Björn Stabel

@unknown If you don't want to stop your server without saving your changes, use SIGKILL(forcekill).
This causes the OS to simply remove the server from memory without giving it a chance to save the map.

That being said, this is a narrow special case which should not endanger the maps of the 99% of players who want their changes saved.

@unknown I must disagree.
/stop, SIGINT(Ctrl-C) and SIGTERM need to save the world or people will lose changes.

Don't force people to go through this. There is no need to.

Contrary to what the issue state suggests, as of 1.10.2, this problem is not fixed or it is in regression.
Since the fix version is a 1.9 snapshot, I think a mistake was made.

We just lost about a week of game play on our server because of it.
This almost dissolved our group.

This was before we added a backup system.
Btw, I notice that most backup tools do something like save-off && save-all && create archive && save-on.
If the server is /stopped during the "create archive" phase, all changes since the save-all will be lost.
If the backup takes a while, this could mean losing many changes.

Please make /stop save the map unconditionally.
That is the behaviour everyone expects until they figure it out the hard way.

EDIT: I just remembered the server got a SIGTERM, not a /stop.
Maybe there is a difference, but I doubt so.