Install a Minecraft modpack (FTB, CurseForge)

A modpack is a coherent set of preconfigured mods (FTB Revelation, All The Mods, etc.). The server install comes down to installing the right loader (Forge, Fabric, or NeoForge) and then dropping the mods into /mods.

Cause / The problem

A modpack requires a specific loader version and a specific Minecraft version. If the server runs Forge while the modpack is for Fabric, or if even one mod is missing, the server refuses to start or crashes in a loop.

Solution

1. Check the modpack version: Minecraft 1.20.1? Forge, Fabric, or NeoForge? CurseForge or FTB? This info is on the modpack page. A version mismatch = crash.
2. Install the right loader via the Pelican panel: under Settings → Server Type / Egg, pick Forge, Fabric, NeoForge, or FTB depending on the modpack. The panel installs the correct version.
3. Download the server version of the modpack:
   • CurseForge: modpack page → Files → Server Pack (a “server” zip without the client).
   • FTB: FTB Server tool or export via the FTB app.
4. Unzip the server pack and drop its contents into /serverfiles over SFTP: the mod .jar files go in /mods, configs in /config, KubeJS scripts in /kubejs, etc.
5. Check the mods: they must all be .jar files and compatible with the Minecraft version and the loader. Don’t mix Forge and Fabric mods.
6. Allocate enough RAM in the panel Variables (-Xmx/-Xms). An average modpack needs 4-6 GB, a heavy one (ATM, FTB Interactions) wants 8-10 GB.
7. Restart and watch the console. On first boot, Forge/Fabric prepares the mods and then starts the world. Crashes show the name of the offending mod.
8. On the client side, players must install the exact same modpack (CurseForge App or FTB App) on the same version.

If the server crashes, remove the last mod mentioned in the stack trace and check its compatibility. Many modpacks publish updates: re-run the up-to-date server pack if a mod breaks after a Minecraft patch.