How to install a modpack on your server

A modpack is a mod loader, a list of mods and their configs. On FadeHost a pack installs in one click; a pack that is not on the platforms takes a few manual steps.

From the panel

Resources, Modpacks. Search CurseForge and Modrinth.
Press Install. The server pack is fetched, the loader and Java are set, and the client-only mods that crash dedicated servers are left out.
Start. The first boot registers every mod and can take several minutes. Wait for the Done line.

A server can also be created straight from a pack: at creation, choose A modpack as the source. Every pack we list has a page with its RAM table and hosting notes: modpacks.

Update the pack

The Installed view in Resources shows the pack’s version and when a new one exists. Take a backup, then update; the world stays, mods are replaced with the new release.

A pack that is not listed

Open Server Software in the header and set the pack’s loader and Minecraft version. Save.
Get the pack’s server pack from its author (not the client zip, which has no mod jars). Upload it in Files and Unzip, or upload over SFTP.
The unzipped mods, config and any kubejs or defaultconfigs folders go in the server folder. Remove shaders and other client-only mods from mods if the author shipped them.
Start and watch the console.

Players

Everyone needs the same pack, same version, in their launcher (CurseForge, Modrinth or Prism). A client on a newer version is refused or misses content. Pin the version for the group and update together.

Good to know

Packs are heavy. 6 GB is a floor for most; the pack page says what the pack really uses. See Allocate RAM.
Pregenerate the area your group will explore (Chunky is in most packs, or install it) before launch night. Fresh chunk generation is the biggest lag source in modded Minecraft.
A pack’s blocks vanish from the world if the pack is removed or a mod is dropped; back up before changing anything.