How to Update a Modpack Without Losing Your World

You just saw the notification. Your favorite modpack dropped a new version with a bunch of fixes and cool new content. Your players are already asking when you're going to update. So you swap in the new files, start the server, and half your builds are gone. Blocks from a removed mod turned into air. Config changes wiped your custom settings. Players are furious.

I've been there. More than once. Updating a modpack on a live server is one of those things that seems simple until it destroys 200 hours of player progress. This guide covers how to do it properly so you keep your world, your builds, and your sanity.

Why modpack updates are risky

A modpack is not just Minecraft with extra stuff. It's a carefully assembled set of mods, configs, and scripts that all depend on each other. When the pack author releases a new version, any of the following can happen:

• Mods get removed. Any blocks or items from that mod vanish from your world. They turn into air or "unknown block" entries. There is no undo.
• Block/item IDs change. This is rarer on modern Forge/NeoForge/Fabric but still happens. When IDs shift, blocks can transform into completely different blocks.
• Configs get reset. The new version ships with fresh config files. If you just overwrite everything, your custom ore gen rates, mob spawning tweaks, and difficulty settings are gone.
• Mod version conflicts. One mod updated to a version that now requires a different library version. The server crashes on startup and you're reading a 500 line stacktrace.

The risk scales with the size of the update. A minor bugfix release (1.4.1 to 1.4.2) is usually safe. A major version jump (1.4 to 2.0) can be a completely different pack under the hood.

Before you do anything: back up everything

I cannot stress this enough. Back up your entire server directory before touching anything. Not just the world folder. Everything.

Here's what you need to preserve:

• /world (or whatever your level name is) including all dimension folders
• /mods folder (so you can revert if needed)
• /config folder
• server.properties
• Any custom scripts, datapacks, or plugin configs
• whitelist.json, ops.json, banned-players.json

If you're on a managed host, most panels let you create a full backup with one click. On Space-Node, you can trigger a backup directly from the panel before making any changes. If you're running a dedicated server or VPS, just zip or tar the entire server directory.

tar -czf server-backup-$(date +%Y%m%d).tar.gz /path/to/your/server/

Do not skip this step. Every server admin who has ever lost a world skipped this step and thought "it'll be fine."

Read the changelog first

Before downloading anything, go to the modpack page on CurseForge or Modrinth and read the changelog for the new version. You're looking for three things:

1. Mods that were removed. If a mod got dropped from the pack, any blocks or items from that mod in your world will be affected. You need to know this before updating so you can warn players or deal with it.
2. Mods that were added. New mods usually don't cause problems, but sometimes a new mod conflicts with server side plugins or custom configs you've set up.
3. Minecraft version changes. If the modpack jumped from 1.20.1 to 1.21, that is not a simple update. That is a potential world reset situation. More on this later.

Also check if the modloader version changed. Going from Forge 47.2 to 47.3 is no big deal. Going from Forge to NeoForge is a different story and requires more careful handling.

The safe update process, step by step

Step 1: Stop the server

Shut down the server cleanly. Use the stop command in the console. Do not just kill the process because that can leave chunks in a corrupted state.

Step 2: Back up the entire server directory

Yes, I already said this above. Doing it again here because this is the step people skip when following a numbered list.

Step 3: Download the new server pack

Go to CurseForge or Modrinth and download the server pack for the new version. Not the client pack. The server pack. They contain different files and mixing them up causes problems.

If the modpack doesn't provide a separate server pack, you'll need to extract the server files yourself. Most modern packs include a server pack download though.

Step 4: Extract into a temporary folder

Do not extract the new files directly into your server directory. Put them in a separate folder so you can compare and selectively copy things over.

Step 5: Replace the mods folder

Delete your old /mods folder and replace it entirely with the one from the new server pack. Do not try to merge mod folders by hand. You will miss something and end up with version conflicts.

Important: If you have any server side mods that you added yourself (performance mods like Spark, or admin tools), copy those back into the new mods folder after replacing. The modpack doesn't know about your extra mods.

Step 6: Handle config files carefully

This is where most people mess up. You have two types of config files:

Configs you should replace: Anything mod specific that the pack author tuned for balance. Recipe changes, worldgen configs, mod integration settings. Take the new versions.

Configs you should keep: Your server.properties, ops.json, whitelist.json, banned-players.json, and any configs where you made intentional server specific changes (custom difficulty settings, chunk loading limits, etc.).

A good approach: replace the entire /config folder with the new one, then manually copy back any files where you had custom changes. If you kept notes on what you changed (you did keep notes, right?), this is much easier.

Step 7: Keep your world folder

Do not replace your world folder. The new server pack usually ships with a fresh world or no world at all. Your existing world stays exactly where it is.

Also keep server.properties since it contains your level name, seed, and server settings.

Step 8: Start the server and watch the logs

Start the server and keep the console open. You're watching for:

• ERROR or FATAL messages that indicate a crash
• Warnings about missing blocks or unknown block states (this means removed mods left orphaned blocks)
• Mod loading errors or dependency issues
• Any message about world conversion or data fixing

If the server starts cleanly, connect with a test account before announcing the update to everyone.

Dealing with removed mods

When a mod gets removed from a pack, here's what happens to its content in your world:

• Blocks from that mod either turn into air (they just disappear) or become "unknown" placeholder blocks depending on the modloader
• Items in player inventories from that mod usually become broken/unknown items
• NBT data warnings will flood your server logs. The server is telling you it found data for things it doesn't recognize anymore
• Entities (mobs, machines, etc.) from that mod are simply gone

There is no easy way to prevent this. If a major building mod is getting removed and your players have used it extensively, you might want to skip that update or give players time to rebuild using other materials first.

Some mods handle removal more gracefully than others. Tech mods that store a lot of tile entity data tend to produce the most log warnings. Decorative mods that only add simple blocks are usually cleaner to remove.

Config files: merge vs replace

Here's a practical rule for deciding what to do with each config file:

Always replace:

• Mod specific configs that control recipes, worldgen, or progression (the pack author balanced these)
• Any config the changelog specifically mentions was changed
• KubeJS or CraftTweaker scripts that the pack uses for custom recipes

Always keep yours:

• server.properties
• ops.json, whitelist.json, banned-players.json
• Performance configs you've tuned (view distance, simulation distance, chunk loading)
• Any config for mods you added yourself

Merge carefully:

• Configs where you changed one or two values but the pack author also updated the file. Open both versions, compare them, and apply your changes on top of the new file.

If you use a diff tool (like diff on Linux, or something like WinMerge on Windows), you can compare old and new configs quickly.

When you should NOT update mid-world

Sometimes the right call is to not update. Here are the situations where updating will almost certainly cause problems:

• The modpack changed Minecraft versions. Going from 1.20.1 to 1.21 is not a modpack update. It's essentially a new world. World formats, block states, and biome data all change between Minecraft versions. You will get chunk borders, missing blocks, and potentially corrupted data.
• Major version jumps with big mod swaps. If the new version removed 20 mods and added 15 different ones, your world is going to have a lot of holes in it.
• The changelog says "not save compatible." Some pack authors are honest and tell you directly. Listen to them.
• You're running a public server with months of player builds. The risk to reward ratio just isn't worth it for a few new features. Wait until your players are ready for a fresh start or a new season.

Testing the update on a copy first

If you have an important world with a lot of player investment, do not update your production server first. Test it.

1. Copy your entire server directory to a separate location
2. Apply the update to the copy
3. Start the copy on a different port
4. Connect and check the world. Walk around. Open machines. Check inventories. Look for missing blocks.
5. If everything looks good, apply the same changes to your production server

This takes an extra 30 minutes but can save you from a catastrophe. On Space-Node, you can spin up a second server instance to test on without affecting your live server.

Rollback plan if things go wrong

If you start the updated server and things are broken, here's the rollback procedure:

1. Stop the server immediately. The longer a corrupted world runs, the more data it writes in its broken state.
2. Do not panic delete things. You have a backup (you made the backup, right?).
3. Restore from your backup. Replace the entire server directory with your backup copy.
4. Start the old version. Everything should be exactly as it was before.

If you forgot to back up (please don't be this person), you might still be able to recover partial data from the world folder, but it won't be fun. Some blocks will be permanently gone.

The key lesson: backups are not optional. They are the entire foundation of a safe update process.

Frequently asked questions

"Can I update the modpack without resetting the world?"

Yes, in most cases. As long as the Minecraft version stays the same and no critical mods were removed, your world will survive the update. Follow the steps in this guide and always back up first.

"What happens to blocks from mods that were removed?"

They either turn into air (disappear entirely) or become invisible/unknown placeholder blocks. Items from removed mods in player inventories become broken items. There is no way to recover them after the fact without a backup.

"Do I need to update the modloader (Forge/NeoForge/Fabric) too?"

Check the modpack's server pack. It usually includes the correct modloader version. If the changelog says "updated to NeoForge 21.1.x" then yes, you need to update the modloader to match. Running mods built for one loader version on a different version can cause crashes.

"My server crashes after updating. What do I do?"

Read the crash log. Look for the first Caused by: line. Common causes are: a missing dependency (a new mod needs a library that wasn't included), a version mismatch (wrong modloader version), or a mod conflict. If you can't figure it out, restore your backup and try again more carefully.

"Can I skip versions? Like go from 1.2.0 directly to 1.5.0?"

Technically yes, but the more versions you skip, the higher the risk. Each version may have added or removed mods. All those changes stack. If possible, read the changelogs for every version in between so you understand the full scope of changes.

"Should I tell my players to update their client before or after I update the server?"

After. Update the server first, verify it works, then tell players to update their client to the matching version. If you tell them to update first and then the server update fails, they can't connect to the old server either.

"I'm on a managed hosting panel. Is the process different?"

The core process is the same: back up, replace mods, keep your world. The difference is that managed panels give you file managers and one click backup tools instead of command line access. Some hosts also offer one click modpack installers that handle the file replacement for you while preserving your world data.

"The update changed configs I had customized. How do I get my settings back?"

If you followed this guide, you kept a copy of your old configs. Open both the old and new versions of the config file, compare them, and re-apply your custom changes to the new file. Do not just copy the old config file over because it may be missing new settings that the updated mods need.