How do I install a modpack that's not in the list, or a custom/self-made pack?
If the pack you want isn't in the Modpacks tab — or it's a custom pack you built yourself — you can still get it running by uploading the pack's server files directly. The key is using the server pack, not the client pack.
Server files, not client files
Custom and unlisted packs are installed manually from their server files. CurseForge packs usually offer a dedicated "Server Pack" download, and for a self-made pack you export your own. These files include the mods, configs, and the loader the server needs.
Step-by-step
- Get the pack's server files — download the "Server Pack" for CurseForge packs, or export your custom pack.
- Stop the server and, ideally, wipe the old server files first so nothing conflicts.
- Upload the server-pack contents to the server root via SFTP (mods, config, and the loader).
- Set the correct Forge/Fabric build in the Versions/Startup tab if needed, then start from the Console.
Tip: Always use the server pack, not the client pack. The client pack includes client-only mods (like minimaps and shaders) that will crash a server.
Frequently asked questions
Where's the "Server Pack" download? On CurseForge, it's usually listed under the pack's Files section as a separate server download. If a pack has none, you may need to build the server files from the client pack by removing client-only mods.
How do I know which loader build to set? The pack's page lists its exact Minecraft and Forge/Fabric version. Match that build in the Versions or Startup tab.
It crashes on start — what's wrong? Most often a client-only mod slipped in, a loader version mismatch, or too little RAM. Read the Console/crash report and share it via mclo.gs if you're stuck.