Repository navigation
Minecraft Updates
Players' Minecraft updates itself. A server on an older version then turns them away, with a message about the version.
The menu checks for a new Minecraft once a day. When one is out, the top of the menu says so.
Press u:
- The world is backed up.
- The server stops, the new version is downloaded (and checked against Mojang's checksum), and the server starts again.
Anyone playing is disconnected for about a minute.
If something isn't right after an update, open Settings and choose Go back to Minecraft (the previous version). Players' games must match the server's version to join.
If the latest Minecraft has a problem - say, players' screens look wrong - option 18 in the menu (Specify server version) switches the server to another version, for example 26.2.
- Everyone's game must use the same version. In the Minecraft Launcher: Installations → New installation, pick the version, and play that installation.
-
Going back to an older version than your world was last played on can damage the world. Minecraft doesn't support it: chests, furnaces and the like can lose what is in them, and parts of the world can be lost - and going forward again does not repair it. So the menu asks:
- Start a new world for that version (recommended). Your world is set aside untouched, and comes back when you return to the latest version.
- Use my world anyway. Your world is backed up first, so you can restore it from Backups and Restore if things go wrong.
- While you're on a version you chose, the menu doesn't push updates. Option 1 goes back to the latest version - and to your original world, if you started a new one.
The snap updates itself automatically, like other snaps. When it does, the server stops cleanly - the world is saved first - and comes straight back.