Direct answer

A modded server backup is incomplete if it contains only the world. Keep the world and dimensions together with the matching mod list, configs and server-loader version.

Recommended procedure

  1. Schedule a maintenance stop or use a backup mechanism that guarantees a consistent snapshot; wait for the Minecraft process to exit before copying live world data.
  2. Copy world/dimension folders, mods/, config/, loader/server JAR details, scripts and allowlist/permission files where relevant.
  3. Store an inventory of exact mod versions and the required Java runtime alongside the backup, because a later mod update may no longer open the same save.
  4. Keep backups off-host as well as local and check the archive is readable. Never include authentication tokens in publicly accessible archives.
java -version
# Record your exact loader, Minecraft and mod versions before restoring

Why this matters

Modded worlds may contain registry data and custom blocks that are lost when mods are removed. Restoring an old world into a mismatched modpack can irreversibly change data.

How to verify the result

Restore to a separate test server with the original mod and loader versions. Confirm custom items, dimensions, entities, inventories and player data before declaring the backup usable.

Version and compatibility notes

Fabric, Forge and NeoForge have different file structures and dependency rules. Follow the exact modpack/server-pack documentation and never assume a Paper plugin backup recipe is sufficient.

Official references

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000