How to Update Your ATM10 Server (2026)

All The Mods 10 receives frequent updates that add content, fix bugs, and update mod versions. Updating your server correctly is critical because a version mismatch between client and server means players cannot connect. Here is how to update safely.

Before you update

1. Back up your world. Copy the entire server folder or use your panel's backup feature. If the update breaks something, you need this backup to roll back. Recent ATM10 release notes all end with the same reminder: ALWAYS REMEMBER TO BACKUP BEFORE UPDATING. Also save any configs and kubejs scripts you changed, because the update replaces those folders.
2. Check the changelog. Read the ATM10 changelog on CurseForge or GitHub to see if any mods were added or removed. Removed mods can delete blocks from your world. For example, 8.0 removed Reap Mod and changed the Dimensional Seed recipe, an ingredient for the ATM Star.
3. Match versions. Your server and all clients must run the exact same ATM10 version. Coordinate with your players before updating. ATM10 includes Better Compatibility Checker, which shows a tick in the server list when a player's pack version matches the server and an X when it does not.

Step-by-step update process

This follows the official ATM server guide.

1. Stop the server completely.
2. Download the new ATM10 server files from CurseForge. They are listed under Additional Files on the file page of the new version, for example ServerFiles-8.2.zip.
3. Delete the mods, config, defaultconfigs and kubejs folders on your server.
4. Extract the same four folders from the new server files into your server folder.
5. Check whether the NeoForge version changed. If it did, also delete the libraries folder and copy in the new startserver.sh or startserver.bat and the new NeoForge installer. The next start installs the new NeoForge. This was needed from 8.1 to 8.2, which moved from NeoForge 21.1.249 to 21.1.251.
6. Re-apply your own config and kubejs changes by hand. Copy only the files you changed, never a whole old config folder.
7. Start the server and watch the console for errors.
8. Have one player test the connection before announcing the update.

These steps leave your world folder, server.properties and eula.txt where they are.

The official guide also gives a second method: extract the new server files into an empty folder, then copy over world, local, server.properties and eula.txt (and journeymap if you have it), plus the config and kubejs files you changed. Copy whitelist.json and ops.json too if you use them. In that case you also get the new user_jvm_args.txt, which sets -Xms4G -Xmx8G, so raise -Xmx to fit your plan again.

Common update errors

• Mismatched mod versions: a mod on the server is a different version than on the client. Check the error message for the exact mod name and version.
• Missing mods: a new mod was added in the update but you did not copy it. Delete the mods folder and extract it again from the new server files. Do not use your client mods folder: the server files leave out client-side mods such as Sodium and Iris on purpose.
• World corruption warning: if a mod was removed that placed blocks in your world, the server may log warnings. These blocks become unknown blocks but usually do not crash the server.
• Java version mismatch: ATM10 requires Java 21. If you updated NeoForge, make sure Java 21 is still the active runtime.

On managed hosting

On a managed host like Space-Node, you can do the same steps through the control panel:

1. Stop the server.
2. In the file manager, delete mods, config, defaultconfigs and kubejs (and libraries if NeoForge changed).
3. Upload the new folders over SFTP. If NeoForge changed, also upload the new startserver.sh and the new NeoForge installer, so the next start installs the new NeoForge. Then re-apply your own config and kubejs changes.
4. Start the server and watch the live console.

If your server starts through user_jvm_args.txt, check that -Xmx still fits your plan after the update.

The short answer

Back up first, delete and re-extract mods, config, defaultconfigs and kubejs, delete libraries if NeoForge changed, and make sure all clients update to the same version. Test with one player before opening to everyone.

Space-Node Minecraft plans let you pick the Java version and startup parameters yourself in the panel's Startup tab. For ATM10, see our All The Mods 10 server hosting plans: 12GB for 1 to 5 players, 16GB for 5 to 15 and 32GB for 15 or more.