Minecraft Modpack Installation

Install a modpack on your Minecraft server using the built-in Modpack Manager, or upload your own pack manually.

Using the Modpack Manager

The Modpack Manager is the easiest way to install modpacks on your server. It pulls data directly from CurseForge and lets you search, browse, and install thousands of modpacks in a few clicks.

Where to Find It

1. Open your server in the Game Panel
2. Click Tools in the navigation menu
3. Select Modpack Manager

You’ll see a searchable list of CurseForge modpacks. Browse or search for the pack you want.

Installing a Modpack

1. Find the modpack you want to install
2. Click the Install button next to it
3. Choose an install option:
   • Install Only: installs the modpack files without touching your existing data
   • Format Server: wipes all server data and installs a clean copy of the modpack

4. Wait for the installation to complete
5. Check that the Server Jar File in your Startup Parameters matches the Forge jar that was installed (e.g. forge-*.jar or server.jar)
6. Start your server

Feed the Beast (FTB) Modpacks

FTB modpacks are no longer updated on CurseForge. The versions in the Modpack Manager may be outdated. For the latest FTB packs, download the server files directly from the FTB website and follow the Manual Modpack Installation guide.

Installing Your Own Modpack

If the modpack you want isn’t on CurseForge, or the Modpack Manager isn’t working for your pack, you can install it manually.

There are two approaches depending on your situation:

CurseForge Pack (Manual)

If the pack is on CurseForge but the automatic installer didn’t work:

1. Download the server files from the pack’s CurseForge page
2. Upload them to your server via SFTP
3. Install the correct version of Forge if it wasn’t included

See Manual Modpack Installation for detailed step-by-step instructions.

Custom Pack

If you’ve built your own modpack or are using a pack from another source:

1. Install the correct version of Forge or Fabric on your server
2. Upload your mods to the mods/ folder via SFTP or the File Manager
3. Upload any required config files to the config/ folder
4. Update the Server Jar File to point to the correct Forge/Fabric jar
5. Start your server

Common Issues

Client-Side Mods Crashing the Server

Some mods only work on the client (your PC) and will crash the server if installed there. This is the most common reason a modded server won’t start after installing a new pack.

What it looks like:

[main/FATAL] [ne.mi.fm.lo.RuntimeDistCleaner/DISTXFORM]: Attempted to load class
net/example/mod/mixin/SomeClientMixin for invalid dist DEDICATED_SERVER

The key phrase is for invalid dist DEDICATED_SERVER. This means the mod tried to load code that only exists on the client.

How to fix it:

1. Check the error for the mod name. It’s usually visible in the class path (e.g. fallingleaves in de/cheaterpaul/fallingleaves/mixin/...)
2. Remove that mod from the server’s mods/ folder
3. Repeat for any other client-only mods

Common client-only mods that will crash a server:

• Shader loaders: Oculus, Iris, OptiFine, Embeddium (rendering)
• Performance/rendering: Dynamic FPS, Better Fps, Entity Culling
• HUD/UI: AppleSkin (client-only version), Jade, WTHIT, Xaero’s Minimap
• Visual effects: Falling Leaves, Particle Rain, Sound Physics

Server Starts as Vanilla Instead of Forge

Your Server Jar File is set to the wrong file. Make sure it’s set to forge-*.jar or server.jar, not minecraft_server.*.jar (that’s the Vanilla jar).

Error: Unable to Access Jarfile

The server can’t find the jar file specified in your Startup Parameters. Either:

• The Forge jar wasn’t included with the modpack. Install Forge yourself.
• The jar has a different name than what’s configured. Update the Server Jar File to match.

Wrong Java Version

If your server crashes on startup with obscure errors, you may be running the wrong Java version for your modpack.

• Minecraft 1.12–1.16 modpacks often require Java 8
• Minecraft 1.17–1.20 modpacks typically need Java 17
• Minecraft 1.21+ modpacks require Java 21

See Java Version Selection to change your server’s Java version.

Can’t Connect After Installing a Modpack

1. Check server.properties and confirm server-port matches your server’s assigned port (found under Management → Allocations)
2. Restart your server if you’ve changed this value
3. Make sure your client is running the same modpack version as the server

Connection Timeouts on Large Modpacks

Large modpacks can take a long time to sync data to connecting players. If players are getting kicked before they finish loading, the server’s login timeout may be too short.

Mods like RandomPatches (Forge 1.12–1.19) or Packet Fixer (Forge/NeoForge/Fabric 1.15–1.21+) can increase the connection timeout and packet size limits. Install the mod on the server only. Players don’t need it on their client.