Skip to main content
Modpacks transform Minecraft into an entirely different game: tech, magic, exploration, skyblock, and everything in between. This guide explains how mods and modpacks differ from plugins, how to install popular packs on your Wasabi Hosting server, and how to size your server’s RAM correctly.

​
Mods vs. Modpacks vs. Plugins

If you want players to join with an unmodified client, you want plugins instead. Mods and plugins generally cannot run on the same server software.

​
Mod Loaders

Every modpack is built for a specific mod loader:
  • Forge: the classic loader; most large packs up to 1.20 use it.
  • NeoForge: the community continuation of Forge; most modern packs (1.20.4+) use it.
  • Fabric: lightweight and fast-updating; used by packs like Prominence II and many performance-focused packs.
The modpack’s page (on CurseForge, FTB, or Modrinth) always states the loader and Minecraft version it needs. Your server must use exactly that combination.

​
Before You Start: Take a Backup

Installing a modpack usually replaces your server files and generates a new world. Create a backup from the panel’s Backups tab first so you can restore your current setup at any time. See Backups.

​
Installing a Modpack

The fastest route when your pack is available in the panel:
1

Open the Version Changer

In the Game Panel, open your server and go to the Version Changer.
2

Pick your loader or pack

Select the modpack directly if it’s listed, or install the matching Forge / NeoForge / Fabric version the pack requires.
3

Install and start

Run the install (enable the wipe option if you’re replacing an old setup), then start the server. The first boot of a large pack can take several minutes.

​
Matching Client and Server

Players must run the same modpack and version as the server:
  • CurseForge packs: install via the CurseForge App, select the exact same pack version.
  • FTB packs: install via the FTB App.
  • Modrinth packs: install via the Modrinth App.
A version mismatch (even a minor one, e.g. pack 1.9.2 vs 1.9.3) commonly causes registry/handshake errors on join. When you update the server pack, tell your players to update too.

​
How Much RAM Do You Need?

Modpacks are far hungrier than vanilla. Rough guidance: These are starting points, since player count, world size, and chunk generation all add up. If you see long GC pauses or OutOfMemoryError crashes, upgrade your plan; upgrades at Wasabi Hosting keep all your files.

​
Common Startup Errors

Normal for big packs, since first boot can take 5–15 minutes while mods initialize and the world generates. Watch the console; as long as new log lines appear, it’s still loading.
The crash report (in /crash-reports) names the offending mod near the top. Common causes: a client-only mod in the server’s mods folder (delete it server-side), or a missing dependency mod (install it).
The pack needs more RAM than your plan provides. See the sizing table above and upgrade if needed.
Client and server pack versions don’t match. Have players reinstall the exact server version of the pack.
Modern packs (1.18+) need Java 17+, and 1.20.5+ needs Java 21, while very old packs (1.12.2) need Java 8. If the console shows UnsupportedClassVersionError, the Java runtime doesn’t match, so contact support or adjust the server’s Java version if your plan’s panel offers it.
Still stuck? Check the general Troubleshooting guide or send us the crash report via Discord or a ticket.

Run your modpack on Wasabi Hosting

Minecraft server hosting from €2.99/month with NVMe storage and DDR5 RAM. Modpacks load fast, and you can upgrade RAM anytime without losing files.