Update a modpack without losing your world
A modpack update only costs you your world if you run it blind. If your pack stays on the same Minecraft version — All the Mods 10 runs on Minecraft 1.21.1 with NeoForge — updating is usually safe. If the pack jumps to a newer Minecraft version, or mods are dropped from it, the blocks and items belonging to those mods disappear from your saved world for good. Three things make the difference: a backup you have checked yourself, a changelog read with removed mods in mind, and a trial run of the update on a copy of your server.
What actually breaks during an update?
Your world is not a snapshot of your base but a pile of region files full of references. Every block is stored as a registry name, such as minecraft:stone or thermal:machine_frame, and those names only mean anything because the mods loaded at save time gave them meaning. Remove one of those mods and the reference stays behind with nothing left to draw it or use it.
On top of that, every chunk — the 16 by 16 block column the world is stored in — records a data version: a number for the format it was last written in. Load an old world in a newer Minecraft version and the game converts those chunks the moment they come into view, and that is a one-way street. Now that Minecraft uses year-based version numbers — 26.1 "Tiny Takeover" in March 2026, 26.2 "Chaos Cubed" in June 2026 — it comes up more often: every pack that follows a new base version touches your world files. Forwards happens by itself, backwards not at all.
Why isn't your host's automatic backup enough?
Automatic backups come as standard with every MC-Node plan, and with most serious hosts too. Even so, "there's an automatic backup running somewhere" is not a plan. It goes wrong on three fronts: the last backup predates your last play session, the retention window is shorter than you thought so the broken state overwrites the good one, or nobody has ever tested whether restoring actually works.
Here is how you build a backup you can genuinely trust:
- Shut the server down cleanly with
stopor through the panel. A hard kill leaves chunks sitting in memory and your backup ends up with half-written data. - Then make a manual backup with a name you will recognise, for example
2026-08-04-before-update. In the Pterodactyl panel that takes five seconds. - Download that copy to your own PC or to separate storage. A copy that only exists on the server you are about to tinker with is not a backup.
- Unpack the file locally and check that
level.dat, theregionfolder andplayerdatareally are in there. - Take
config,defaultconfigsandkubejsalong as well. Config files are regularly overwritten during updates, and your own settings go with them.
Patch update or major update: what's the difference?
Modpack authors rarely stick to strict version numbering, so the number on its own tells you very little. What counts is this: do the Minecraft version and the mod loader stay the same, and have any mods been pulled out of the pack?
| Type of update | Example | What changes | Risk to your world |
|---|---|---|---|
| Patch or hotfix | Better MC (BMC4) from v58 to a following hotfix on the same Minecraft version | Bug fixes, recipes, config values, sometimes one mod version | Low: make a backup and carry on |
| Minor update | Same Minecraft version and mod loader, but mods added or removed | New blocks and items, missing mods, altered world generation | Medium: read the changelog, run it on a copy first |
| Major update | The pack moves to a newer Minecraft version, or from Forge to NeoForge | Mod loader, Java version, registries, world generation | High: expect to need a new world |
A major update changes the surroundings as well. All the Mods 10 requires Java 21; on Java 17 the pack simply will not start. And if you are running 8 GB while your pack moves towards the requirements of ATM10 — 10 GB minimum, 12 GB for a small group, 14 to 16 GB with five or more players — you will hit memory errors that have nothing to do with your world but turn up at exactly the same moment.
What happens to blocks from a removed mod?
Forge and NeoForge show a screen at startup listing missing registry entries and asking whether you want to continue. Click through and those entries are stripped from your world: blocks turn to air, items in chests and inventories vanish without dropping, machines leave none of their contents behind. Dimensions from a removed mod no longer exist, and a player who logged out in one cannot log back in until you edit their playerdata.
Clicking through the missing registry entries screen cannot be undone. Never do it on your live server before you know which mods are involved.
That is why you actively hunt through the changelog for a removed mods heading, for the phrase "requires a new world" and for changes to world generation. New biomes and ores only appear in chunks that have not been generated yet: nothing changes in your existing area, and along the border between old and new you will see seams in the landscape. Packs with progression systems of their own, such as the quests and skill tree in Prominence II: Hasturian Era or the Vaults in Vault Hunters 3rd Edition, may reset your progress in them.
One category is almost always safe: mods that add no blocks of their own. Optimisation mods such as FerriteCore, Canary and ModernFix can usually be swapped without consequence; at worst you lose the 30 to 40 percent memory saving from FerriteCore, and your world will not notice a thing.
How do you test an update on a copy of your server?
This is the step that gets skipped as a matter of routine, and it is the one that prevents the misery.
- Stop the server, make the backup described in the previous section and download the world folder.
- Set up a second environment: locally on your own PC if you have the memory to spare, or on a temporary server. Minecraft hosting at MC-Node starts at EUR 1.10 per GB of RAM per month on the budget line.
- Install the new pack version clean, not on top of the old one. Leftover jars from the previous version are a classic cause of crashes that get wrongly blamed on the world.
- Only then put your world folder back and start up with the console open. Be patient: a big pack like ATM10 takes 2 to 3 minutes on an NVMe SSD, and 10 minutes or more on an ordinary hard disk.
- Read the log for missing registry entries and config migration. Then fly over your base in spectator, open chests and check machines and the quest book.
- Leave it running for half an hour and watch your TPS — ticks per second, the server's heartbeat — with spark. There is more on that in our article on optimising your Minecraft server.
- If everything checks out, run exactly the same steps on the live server.
Do the client and server have to update together?
Yes, and with mods that is not up for negotiation. Mods load on both sides and have to run in the same version; otherwise the player is refused on connect with a message about missing or incompatible mods. Plugins work differently — they run purely server-side, so players do not have to install anything — and ViaVersion is no help here either: it bridges differences in the vanilla protocol, not in mod lists. There is more on that in our article on what a modpack is and how to install one.
So announce an update with a date and a time, and update the server and the launcher profile within the same window. Warn players not to open their local copy of the world in a newer client either: that upgrades the chunks in the copy, and there is no putting it back.
When are you better off starting a fresh world?
Sometimes carrying on costs more than starting over. Go for a new world if the pack moves to a different Minecraft version, if the changelog advises a world reset, if the mods being dropped were the core of your progression, or if your world is still young. If you want to see new biomes, such as the "dappled forest" biome from the 26.3 snapshots, carrying on makes little sense: they only appear in new chunks.
You do not have to throw everything away. Copy your base as a schematic with WorldEdit, or keep the old world as a second world on the same server; whether that fits depends on your specs, and the groundwork for that is in our step-by-step guide to making a Minecraft server. If your pack has sat stable on the same base version for years, as RLCraft has on Minecraft 1.12.2, there is often no reason to update at all. A world everybody actually plays in is worth more than the newest version number.
Frequently asked questions
Can I roll my world back to an older Minecraft version? No. Once chunks have been converted to the newer data format that is a one-way street, and the older version no longer reads them correctly. The only way back is the backup you made and downloaded before the update.
How much RAM do I need after updating to a big pack? That varies per pack. All the Mods 10 asks for 10 GB minimum, 12 GB for a small group and 14 to 16 GB with five or more players or heavy automation. Cobblemon packs often run fine on 4 to 8 GB.
Do players get a message if their client does not match the server? Yes. If the mod list or a mod version differs, the connection is refused with a message about missing or incompatible mods. Client and server have to run the same pack version; there is no middle ground.
Is my host's automatic backup enough? Only if you check it. At MC-Node automatic backups come as standard with every plan, but by definition they capture a moment in the past and newer backups can push them out. Make an extra copy yourself just before an update and download it.
Can I test for free without renting a second server? Yes. Run the updated pack with your world copy locally on your own PC, provided you have enough memory free. If your machine cannot cope, a temporary test server on the budget line at EUR 1.10 per GB of RAM per month is the alternative.