Installing mods (Forge / Fabric)

Mods (unlike plugins) change actual game content. They run on both the server AND the player's client — both have to have the same mods at the same versions.

Getting mods

CurseForge and Modrinth are the main sources. Filter by mod loader (Forge / Fabric / NeoForge) and Minecraft version.

Installing on the server

1. Set your server type to Forge or Fabric (see Server types).
2. Stop the server.
3. Panel → Files → open /mods/.
4. Upload the mod .jar files (multiple at once is fine).
5. Start the server. Watch the console for load errors.

On the client

Players install the same mod loader on their game (Forge installer or Fabric installer), then drop the same mods into their local mods/ folder. The launcher's "installations" feature manages mod profiles per Minecraft version.

Modpacks

For pre-built packs (FTB, CurseForge packs, ATLauncher packs):

1. Download the server pack (not the client pack).
2. Stop the server.
3. Wipe /mods/ (or back it up) so packs don't conflict.
4. Upload the server pack, extract via the file manager.
5. The pack usually includes a startup script — if so, set it as the server's startup command (or ping us on chat to set it).
6. Start.

Players need the matching client pack from the same launcher.

Java memory

Big modpacks need RAM. Allocate generously — many modpacks recommend 6–8GB for ~10 players. Tier needs to match. If you're hitting OutOfMemoryError consistently, upgrade.

A mod broke the server

Look for the last entries before the crash in the console — they usually name the mod. Remove or rename it to .jar.disabled, restart, and the server boots without it.