Minecraft Server on an Old Version (1.8, 1.12.2, 1.16.5, 1.20.1): Why and How

Why people still play on old versions

1.8 (on servers, 1.8.8): the last one before 1.9, which changed combat in February 2016. Since 1.9 every hit has a cooldown; in 1.8 you hit as fast as you can click. That's why PvP and minigame servers stay on it. All 1.8.x versions speak the same language: you join a 1.8.8 server with 1.8.9 from the launcher.

1.12.2 (2017): the version of the legendary Forge modpacks, like RLCraft. Many mods from that era never moved past it, and their modpacks still have a community.

1.16.5 (2021): the last one that runs on Java 8, and the version of many classic Forge modpacks that people still play.

1.20.1 (2023): the version with the most mods and big modpacks of recent years, on both Forge and Fabric.

1.21.1 (2024): the most played NeoForge version, and the one for Cobblemon.

What you lose on an old version

Security fixes. Paper only maintains recent versions: in its API, only 26.2 and 26.3 are listed as maintained today; everything else is marked unsupported. An old server gets no fixes, so lock it down with the whitelist if it isn't public, and make backups.

New plugins. Many plugins no longer publish builds for 1.8 or 1.12.2: look on their page for the last release that supported your version.

Modern Java. Up to 1.16.5, the server runs on Java 8 (the Java table), and current plugins ask for more: ViaVersion needs Java 17 since its version 5; Geyser, Java 21. Their current releases won't load on a server running Java 8.

Bedrock players. Geyser, the plugin that lets Bedrock players in, only works on Paper 1.20.5 or later: its documentation says so. Don't turn it on for an older server.

Letting in players on other versions. On 1.20.1 or 1.21.1 with Paper, ViaVersion and ViaBackwards work as usual. On Java 8, the last ViaVersion that loads (4.10.2) only knows clients up to 1.20.6; its authors publish separate Java 8 builds, unsupported. The practical option: everyone joins with the server's version.

How to play on an old version on NapNodes

1. Move the world aside if there is one

   A new server creates its world on the latest version, and the panel won't let you go down a version with that world in place (it would break it). With the server stopped, in “Files”, rename the world folder, for example to world-nuevo. Nothing gets deleted.

2. Choose the type and version

   “Mods & plugins” → “Server type” tab. Paper if you'll use plugins (1.8.8, 1.12.2, 1.16.5…); Forge, Fabric or NeoForge if you'll use mods. Pick the version and press “Change”.

3. Let it finish

   The panel sets the right Java for that version (Java 8 up to 1.16.5), installs it and starts it. A new world is created on that version.

4. For a modpack, use “Modpacks” instead

   In the “Modpacks” tab of “Mods & plugins”, the modpack brings its own version and loader: the panel sets them for you.

5. Have your friends pick the version

   In the launcher, “Installations” → “New installation” → the server's version. With mods, the same modpack on the same version.

If you want to update one day

Going up works: the world is converted when it starts on the new version. With mods, anything added by a mod that doesn't exist on the new version disappears from the world, so check first that they're all there.

Going down doesn't: a world opened on a newer version won't go back to an older one. So before any change, make a backup in “Backups” (why you can't downgrade). The steps are in the guide to updating the server version.

Frequently asked questions