Install or change a Minecraft modpack safely

Choose the exact modpack release before changing your server. A pack can require a particular Minecraft version, mod loader, Java runtime and server configuration. Uploading a collection of mods over an existing installation can leave incompatible files behind.

Check compatibility first

• Record the pack name, release number, Minecraft version and loader, such as Fabric, Forge or NeoForge.
• Read the author's server instructions and look for the matching server pack. A client export or manifest may need a pack installer and may not contain usable server files.
• Check the required Java version and the pack's RAM and storage guidance. Leave space for extraction and a recovery copy.
• Confirm that players can install the matching client release. A matching Minecraft number alone does not prove matching mods.

Use the author's project or official distribution page. Keep the release link in your notes so support can identify the same files. Paper plugins and loader-based mods use different systems; placing Fabric mods in Paper's plugins folder will not install a Fabric server.

Protect the current installation

1. Tell players about the maintenance window and stop the server in Console. Wait for saving to finish.
2. Take and verify a complete backup, then keep a copy outside the game server. Export any external databases used by the current installation.
3. Record the current startup settings, loader, Java image and world directory. Keep the previous pack files together as a matching recovery set.
4. For an unrelated pack, use a separate test installation or ask support to arrange one. Do not merge its files into your only world.

Prepare the new files

Follow the pack author's server instructions. A server pack commonly includes mods, configuration and sometimes scripts or other data folders. Keep that structure intact. Do not upload your entire client profile or add client-only graphics mods to the server.

Ask support to confirm the supported loader and startup method if the current service is configured for Paper or a different loader. Do not press Reinstall to change packs until you understand what that operation replaces. An uploaded Windows batch file will not automatically become the startup command on a Linux game container.

Where you upload an archive through Files or SFTP, check its extracted location before starting. Avoid an extra enclosing folder that leaves the actual server files one level below the startup directory. Preserve the assigned network settings rather than copying another host's address or port.

Test the first startup

Start the server and read the loader's complete output. For a missing dependency, obtain the named compatible dependency from its developer; do not disable dependency checks. For a client-only mod error, compare the installation with the author's server pack before removing anything.

Join using the matching client pack. Check world selection, inventories and pack features. Changing or removing content mods can remove blocks or items from an existing world. Keep that world stopped until the author confirms the migration path. To roll back, restore the matching pre-change files and databases rather than swapping only the loader JAR.

Further reading: CurseForge server packs, Fabric mod compatibility and Fabric installation. For startup failures, collect the relevant logs.