Loading...
Change your Minecraft server version with the GaleniusNodes version changer. Learn how to back up your world, choose compatible server software, and fix common startup errors.
Stop your Minecraft server, create a backup, open the Version Changer in the GaleniusNodes game panel, select the server software and Minecraft version you need, and start the server. Verify that your world, plugins, mods, and player clients are compatible before allowing players to reconnect.
Changing a Minecraft server version can be necessary when updating for new features, matching a modpack, restoring an older setup, or moving between server software such as Vanilla, Paper, Purpur, Forge, NeoForge, and Fabric. The version number and server software are separate choices, and both affect compatibility.
Never change versions without a backup. Downgrading a world is especially dangerous because older server versions may not understand newer blocks, entities, or save data.
Record the current Minecraft version, server software, Java version, plugins, mods, and world name. Then check whether each part supports the version you plan to install.
| Server software | Use it for | Compatibility requirement |
|---|---|---|
| Vanilla | Official Minecraft gameplay | Clients normally use the same Minecraft version |
| Paper | Plugins and improved performance | Plugins must support the selected Minecraft and Paper API version |
| Purpur | Paper plugins with extra gameplay settings | Use plugins and settings compatible with its Paper base |
| Forge | Forge mods and modpacks | Server and client need matching Forge-compatible mods |
| NeoForge | Modern NeoForge mods | Use NeoForge builds made for the exact Minecraft version |
| Fabric | Fabric mods and lightweight setups | Use matching Fabric Loader, Fabric API, and mod versions |
Keep the backup until the new version has started successfully and the world, inventories, plugins, and mods have been tested.
Choose the server software first, then select the exact Minecraft release required by your players, plugins, mods, or modpack. Do not select the newest version automatically when your extensions have not been updated for it.
After the server reaches its ready state, verify the installed version in the console and test the server before inviting players back.
versionThe version change is complete when the server reaches the ready state, the expected world loads, and a compatible client can join without extension errors.
Upgrading is generally safer than downgrading, but plugins, mods, datapacks, and configuration formats can still break. Update extensions only from trusted sources and read their release notes before starting the upgraded server.
Do not open a world created or saved by a newer Minecraft version in an older server unless the world is disposable. Restore a backup from the older version or create a separate world for the downgrade.
| Symptom | Likely cause | What to do |
|---|---|---|
| Server stops during startup | Incompatible plugin, mod, dependency, or Java version | Read the first console error and update or remove the named component |
| World will not load | The world was saved by a newer or incompatible version | Stop the server and restore the compatible backup |
| Plugins are disabled | The plugin build does not support the selected server version | Install compatible releases and required dependencies |
| Mod channel mismatch | Client and server loaders or mods differ | Match the Minecraft version, loader, and shared mod versions |
| Players see incompatible client | Their Minecraft version does not match the server | Launch a compatible profile or configure a supported protocol plugin |
| Version Changer option is unavailable | The server is running, installing, or the panel session is stale | Stop the server, wait for active tasks, refresh the panel, and try again |
When requesting support, include the old and new Minecraft versions, selected server software, whether you upgraded or downgraded, and the first relevant console error.
Changing the server version should not intentionally delete the world, but upgrades, downgrades, and software changes can alter or corrupt world data. Always create and verify a backup before changing versions.
Downgrading is risky because newer worlds can contain blocks, entities, and data formats that older versions cannot understand. The safest option is to restore a backup created on the older version or generate a separate world.
Only when the plugin release supports the new Minecraft version and server software. Update incompatible plugins and their dependencies before normal play resumes.
Mods must match the Minecraft version and loader family. Forge, NeoForge, and Fabric mods are not interchangeable, and shared client mods must also match the server.
Common causes include an incompatible plugin or mod, the wrong Java version, a missing dependency, invalid startup settings, or world data that cannot be loaded by the selected version. Read the first meaningful console error.
Normally, players need a compatible client version. Plugin-based compatibility tools such as ViaVersion can support some version differences on Paper-compatible servers, but they do not make every feature or mod compatible.
Choose Vanilla for the official unmodified experience, Paper or Purpur for plugins and improved performance, and Forge, NeoForge, or Fabric when your server requires mods built for that loader.
How to Use Chunky to Pre-Generate a Minecraft World
Install and use Chunky to pre-generate Minecraft chunks, reduce exploration lag, set a world, center, shape, and radius, and monitor or pause generation.
Read guideHow to Use SFTP on a Minecraft Server
Connect to your Minecraft server with SFTP and FileZilla. Learn where to find GaleniusNodes credentials, upload worlds and server files, and fix connection errors.
Read guideHow to Install Plugins on a Minecraft Server
Install Minecraft plugins with the GaleniusNodes plugin installer or manually on Paper, Purpur, and Spigot. Includes compatibility checks and troubleshooting.
Read guideInclude your Minecraft version, server software or loader, plugin or mod URL, and the first console error.