Install modpacks

Modpacks are in your Minecraft server's Modpacks tab. At the top you choose the source: Modrinth or Own package. From Modrinth, packs for Fabric, Quilt, Forge and NeoForge work. Packs straight from CurseForge cannot be searched here; you can upload their server pack as your own package, though.

Install a modpack from Modrinth

1. 1

   Choose Modrinth, search for the pack, say “Cobblemon”, and open Versions. Each version says which loader it is for.

2. 2

   Pick the version and press Install.

3. 3

   Leave Create a backup first switched on. Without a backup you confirm by holding.

4. 4

   The portal shows the steps: download and check the modpack, backup, stop the server, Java version, install the loader, download mods, apply the modpack's settings, start.

Fabric comes as a ready server file. For Quilt, Forge and NeoForge the portal downloads the loader's installer, checks it against its publisher's checksum and runs it once on your server; that takes a minute or two. Every mod is checked against the checksum in the modpack before it is uploaded.

Mods that only belong in the game are left off the server. Your players need the same modpack in the same version on their PC, for example through the Modrinth launcher.

Install your own package

1. 1

   Choose Own package and upload the file: a server pack as a .zip (with the mods folder) or a Modrinth modpack as a .mrpack. Put files larger than the limit shown into the main folder via SFTP; they then appear in the list.

2. 2

   The portal reads the file and shows what it recognised: the loader, the Minecraft version and where it knows that from, for example the installer in the package, variables.txt, the start script or the libraries folder.

3. 3

   If that is right, press Install.

If a package does not name the loader or the Minecraft version clearly, or its details contradict each other, the portal installs nothing and says why. A CurseForge pack list (only manifest.json, no mods) does not work; download the modpack's “Server Files” instead. If the package names no version of the loader, the recommended one for that Minecraft version is used; this is shown with it.

From a server pack the portal takes the mods, settings and other folders. It leaves out start scripts, the installer, libraries, the eula.txt and the player lists (ops.json, whitelist.json and the ban lists): the portal installs the loader itself, and your server's players stay as they are.

What happens

• Afterwards the server runs the pack's loader, in the pack's Minecraft version.
• Your current mods are moved to a folder mods-vorher-…; nothing is deleted.
• The pack's files replace files of the same name, for example under config. If a pack brings its own world, your previous one is beside it afterwards as world-vorher-….
• Otherwise your world stays as it is.
• If something goes wrong on the way, the portal restores the previous state: the files, the start command, the Java version and the version settings. If the server was running before, it starts again. What an installer put into the libraries folder stays there; it does no harm.

Updating

When Modrinth has a newer version of the installed pack for the same Minecraft version and loader, the tab shows Update to ….

Limits

• Modrinth packs up to 256 MB and at most 600 files.
• Forge packs from Minecraft 1.17 on; before that Forge started in a different way.
• Uploading in the tab up to the limit shown; larger packages via SFTP.
• When all backup slots are in use, no backup first is possible; delete an old one first.
• While an installation, a software switch or an instance is already running, a second one cannot start.