How to Update Modpack Without Losing World
Learn how to update a modpack without losing your world data, covering backup procedures, file diffing, mod migration, and rollback strategies.
The Risk of Modpack Updates
Modpack updates are necessary. They fix bugs, patch exploits, add content, and keep your server compatible with the latest launcher versions. But every update carries a risk: if a mod changes how it stores data, updates its block registry, or gets removed entirely, your world can lose blocks, items, or entire builds. Learning how to update modpack without losing world data is one of the most important server admin skills.
Step 1: Full Backup
Before any update, create a complete backup of your server directory. This includes the world folder, configs, mods, and any plugin data. If you want to update modpack without losing world files and something goes wrong, this backup is your lifeline.
On a hosting panel, use the built-in backup feature. On a VPS, run tar -czf backup-$(date +%Y%m%d).tar.gz /path/to/server/. Store the backup somewhere separate from the server itself.
Step 2: Read the Changelog
Every modpack update should include a changelog listing added, removed, and updated mods. Read it carefully. Pay special attention to:
- Removed mods. If a mod is removed and you have its blocks placed in the world, those blocks will become "missing" entries. Depending on the mod, they may vanish or turn into error blocks.
- Major version jumps. A mod going from 4.x to 5.x often means internal data format changes. These can break existing machines, inventories, or stored items.
- Config resets. Some updates ship new default configs that override your custom settings.
Step 3: Apply the Update
Download the new server pack version. To update modpack without losing world saves, do not simply overwrite everything. Instead, follow this process:
- Extract the new server pack to a temporary directory.
- Replace the
mods/folder on your server with the new one. Do not merge, replace entirely. - Merge the
config/folder carefully. If you have custom config changes (spawn rates, difficulty settings, recipe tweaks), compare your old configs with the new defaults and re-apply your changes to the new files. A diff tool makes this much easier. - Keep your existing
world/folder untouched. - Update the Forge/NeoForge jar if the pack requires a newer loader version.
Step 4: Test Before Opening
Start the server and watch the console. Look for warnings about missing block registries or unknown mod entries. Join the server yourself and inspect key areas of your world, especially bases with machines, pipes, and complex mod interactions.
If you spot missing blocks, check whether the responsible mod was removed or updated with breaking changes. Sometimes you can restore those blocks by temporarily re-adding the old mod version, breaking the blocks manually, and then removing the old jar.
Rollback Strategy
If the update causes widespread issues, restore your backup and wait for a hotfix from the pack author. Trying to update modpack without losing world progress sometimes means accepting that a particular update is not safe yet. Check the pack's issue tracker or Discord for known problems before committing.
For related tasks, see our guides on adding mods to existing servers and importing singleplayer worlds.
Host your modpack on Astroworld Hosting, NVMe SSDs, full panel access, 24/7 support.