How to Install a Modpack on Your Minecraft Server

Install CurseForge, ATLauncher, and custom modpacks on your Minecraft Java server, including how to set the right Java version.

Modpacks bundle dozens or hundreds of mods together for a curated experience — Better Minecraft, RLCraft, All the Mods, FTB packs, ATM packs, etc. Most modpacks include a "server pack" you can drop into your server folder.

Install a CurseForge Modpack

Find the modpack on CurseForge

Browse to CurseForge Modpacks and find the modpack you want.

Download the server pack

On the modpack page, click the Files tab. Look for "Server Files" or a download labeled "Server Pack". This is different from the regular client pack.

Some modpacks don't have a separate server pack — in that case, follow the Manual Install tab.

Stop your server

In the XGamingServer Panel, go to Console and stop your server.

Back up the existing world

Go to Backups and create a backup before wiping the existing server.

Delete existing server files

In Files, select all current files and delete them. (Or do a fresh Reinstall Server from the Dashboard.)

Upload the server pack

Upload the server pack .zip to the server root, then Unarchive it. The contents should include mods/, config/, a startup script, and the loader's .jar file.

Set the Java version

Most modern modpacks require Java 17 or Java 21. In Startup, select the matching Java version. See Java Version.

Start the server

Start from Console. The first start can take several minutes as mods initialize and generate config files.

Identify the mod loader

Check whether the modpack uses Forge, NeoForge, or Fabric (usually in the modpack description).

Switch to the correct server type

In Startup, select the matching loader. Reinstall the server with that loader.

Download the modpack files

Download all the modpack's .jar files manually from CurseForge or Modrinth (or extract them from a client pack zip).

Upload mods

In Files, navigate to mods/ and upload all the mod .jar files.

Upload configs

If the modpack has custom configs, upload them to config/.

Players Need the Same Pack

Every player connecting to a modded server needs the same modpack installed locally. The easiest way:

LauncherNotes
CurseForge AppBest for CurseForge packs — auto-installs the entire pack
ATLauncherCross-platform, supports CurseForge + ATLauncher packs
Prism LauncherOpen-source launcher with great modpack support
MultiMCOriginal modpack-friendly launcher (less actively maintained)

Tell your players: "Install [Modpack Name] from [launcher]. Connect to <your IP>."

Update a Modpack

Back up everything

Go to Backups and save your current state. Modpack updates can break worlds.

Download the new server pack

Get the new version from CurseForge.

Delete old mods

In Files, delete the contents of mods/ (but keep your world/ folder).

Upload new mods

Upload the new pack's mods to mods/. Replace any updated configs as well.

Start the server

If something breaks, restore from your backup.

Warning: Modpack updates that remove mods can corrupt your world if those mods added blocks/items players have placed/collected. Always back up before updating, and test in a separate world if possible.

Common Issues

ProblemFix
Server runs out of memoryModpacks are RAM-hungry. Increase RAM allocation in Startup. See How Much RAM
Wrong Java versionModern modpacks need Java 17/21. Set in Startup
Crash on startupCheck Console for the failing mod. Remove or update it
Players can't connectThey don't have the same modpack installed. Send them the launcher link
No server pack availableUse the manual install method, or try downloading a client pack and removing client-only mods

How is this guide?

40% Off — Limited TimeGet your Minecraft server todayInstant setup, DDoS protection, and 24/7 support included.
Get a Server

On this page