Running a modpack on a server

0. Is there a server pack?

First, check to see if the modpack provides a “server pack”. On CurseForge, they can be found under “Additional Files”. Here’s an example.

Download the server pack and unzip it to a new folder on your Minecraft server. Follow the instructions inside the server pack, if any were provided. Otherwise, if a start script is provided (some kind of .bat or .sh), run that; if there’s no script, there will be a jar you can run with java -jar.

If there is no server pack, you’ll need to create one yourself.

1. Download the modpack with a launcher

If you try to download a modpack from CurseForge with the “download” button, you will find a zip containing manifest.json and an overrides folder. You can’t do anything with these files directly. These files are for your modded Minecraft launcher. Just open the CurseForge launcher, or Prism Launcher, or Modrinth, or whatever and download the modpack normally through its interface, as if you were going to play singleplayer.

Your launcher will download all the files mentioned in manifest.json and assemble a copy of the modpack on your computer.

2. Make sure Java is installed on your server

On your dedicated server, make sure the appropriate version of Java is available.

3. Create a clean Fabric/Neoforge installation on your server

On your dedicated server, create a folder dedicated to your Minecraft server.

You probably don’t have to grab exactly the same version of Fabric/Neoforge/etc that the modpack uses, but it won’t hurt.

Now, run the server once. On Fabric, this is when you’d run the Minecraft Server Launcher with java -jar. On NeoForge, after running the installer you’ll have a .bat or .sh script you can use.

Why start the server now?

4. Copy the modpack from your client to the server

Go back to your launcher, and copypaste all of the modpack’s files from your client to the dedicated server.

You’ll want to merge them together. For example, the contents of the mods folder on your client should get placed in the mods folder on the server.

When in doubt, just copy it to the server. In the past, you may have been required to comb through and delete any client-only mods from the server’s mods folder, because they would crash when launched on the server. This shouldn’t be a problem with well-coded client mods nowadays.

5. Start the server again

Start the modded Minecraft server using the same command you used in step 3. If all goes well, you should see a lot more log messages as all of the mods initialize, and you should be able to connect from your modded client.

More things to explore

TODO: test these out to see how much easier/harder they are

See also comp500’s “big list of modpack things”, although most of these are for modpack authors as well