Custom Modpacks on Minecraft Servers: Why Most Hosts Make It Hard (And How We Don't)

If you've ever tried to run a custom modpack on a Minecraft server, you already know the feeling.

You've spent hours building the perfect pack - exactly the mods your group wants, nothing you don't. You upload it to your host. Something breaks immediately. You open a support ticket. Three days later someone tells you to check the logs. You check the logs. You have no idea what you're looking at.

This is the standard experience. It doesn't have to be.

Why custom modpacks are harder than pre-made ones

Pre-made modpacks (ATM10, Better Minecraft, RLCraft) are tested. Someone has already figured out which mods conflict, which Forge version works, which server software is compatible. When you install one on a host, you're installing something that has been debugged by thousands of players before you. If that's what you're after, our guide to the best modded Minecraft hosting for small friend groups covers the pre-made pack side in detail.

Custom modpacks have none of that. Every combination is new. And the things that go wrong are not obvious:

Client-side mods on the server. Mods like shaders, minimap clients, and inventory tweaks are designed to run on the player's computer, not the server. Install them server-side and the server either crashes on startup or throws errors that look completely unrelated to the actual problem. Finding them in a 200-mod pack without knowing what to look for takes hours.

Incompatible mod versions. Mod A requires Library X version 1.4. Mod B requires Library X version 1.6. They cannot coexist. The error message usually doesn't tell you which two mods are fighting - it tells you something broke in the library, and you have to work backwards. We've written up one nasty version of this - a custom modpack maxing out RAM with zero players online - if you want to see what the debugging actually looks like.

Wrong server software. Forge mods don't run on Fabric. Fabric mods don't run on Forge. Some mods require NeoForge specifically. Some mods have versions for multiple loaders but they're not interchangeable. Getting this wrong means the server never starts.

World corruption when changing mods mid-playthrough. Removing a mod that generated blocks or dimensions in your world doesn't remove those blocks - it removes the code that knows what they are. Chunks that contain them corrupt. This is the hardest failure to recover from and the one most players don't anticipate until it happens.

Why most hosts can't actually help with this

Most hosting companies aren't built around modded Minecraft specifically. They're built around infrastructure - give the customer a server, let the customer figure out what runs on it. Their support teams are trained to handle billing questions, panel navigation, and basic connectivity issues.

When you open a ticket saying "my custom modpack won't start," you get one of two responses: a link to a generic troubleshooting guide, or a request to share your logs with no further guidance on what to look for in them. That gap is exactly what we cover in our Piggo vs Nitrado comparison and Piggo vs Exaroton comparison - and if you're weighing options more broadly, we've also put together 5 better Minecraft server hosting alternatives.

Exaroton specifically has another problem: on their pre-made modpack installs, the mods folder is locked. You can use overrides to modify configs, but you can't directly add or remove mods from the pack. If you want a custom pack, you have to build it from scratch in their custom software - which means you can't start from an existing pack and modify it. For groups who want to take something like ATM10 and strip out the mods they don't want, that's a meaningful limitation. We walk through a real migration in moving a 254-mod Forge server off Exaroton.

How Piggo handles custom modpack installs

When a customer comes to us with a custom modpack, the process is straightforward.

If the pack is on CurseForge, send us the share code link - we download it directly. If the pack is a folder of mods you've assembled yourself, send us the mods and we handle the rest. If you're not sure what you have, tell us what you're trying to play and we'll figure it out together.

From there we handle the install, identify any client-side mods that need to come out, check for version conflicts before they cause problems, and verify the server starts cleanly before we hand it back to you. If something breaks - a conflict we didn't catch, a compatibility issue that only shows up when all players are online, a world generation problem after adding a new mod mid-playthrough - we fix it.

You don't need to read a crash log. You don't need to know the difference between Forge and NeoForge. You don't need to spend an evening in a support ticket queue explaining what happened. You describe the problem in Discord and we sort it.

Full file access is included on every plan. No locked folders, no restrictions on what you can install.

What to send us when you set up your custom modpack

The fastest way to get your custom server running:

• A CurseForge pack share link, OR a folder/zip of your mods
• The Minecraft version your pack is built for
• The mod loader (Forge, NeoForge, Fabric, Quilt - if you're not sure, tell us what mods you're using and we'll identify it)
• Whether this is a fresh world or an existing world you want to migrate

That's everything we need to get started. Most custom pack installs are running within a few hours of receiving the files.

FAQ

Can you install a custom modpack I built myself?

Yes. Send us the mods folder or a CurseForge share code and we'll handle the installation.

What if my modpack has conflicts?

We identify and resolve conflicts as part of the install process. Client-side mods, incompatible versions, and server software mismatches are the most common issues - we check for all of them before handing the server back.

Can I add or remove mods after the server is running?

Yes. Full file access means you can modify the modpack at any time. We recommend letting us know before making major changes mid-playthrough to avoid world corruption from removing mods that generated content in your world.

What Minecraft versions do you support?

Any version. We support Forge, NeoForge, Fabric, and Quilt across all major Minecraft releases.

How long does a custom modpack install take?

Most installs are complete within a few hours. Complex packs with many mods or known conflict-prone combinations may take longer - we'll keep you updated throughout.

Can I migrate my existing world from another host?

Yes. Send us your world files and we'll import them. If you're moving from Exaroton or another host with file access restrictions, we can walk you through exporting your world - and our Exaroton migration guide covers a full 254-mod Forge move step by step.

What if something breaks after we start playing?

Message us in Discord. Crash logs, mod conflicts that appear mid-playthrough, world issues - we handle all of it. That's what the support is for.

Related reading

• Best modded Minecraft hosting for small friend groups (2026)
• 5 better Minecraft server hosting alternatives
• Piggo vs Exaroton: an honest comparison
• Piggo vs Nitrado: an honest comparison
• Exaroton migration: 254-mod Forge server
• Custom modpack maxing RAM with zero players - the fix
• How to build a Minecraft public server players come back to
• Why friend groups stop playing Minecraft

Ready to run your custom modpack?

If you have a custom modpack ready to go - or a rough idea of what you want to build - start with our free 48-hour trial. 8GB RAM, no card required. Tell us what you're running and we'll have it set up for you.

---

*Written by Maks, founder of Piggo. I've been setting up modded Minecraft servers for friend groups since before Piggo existed - first for my own groups, now for paying customers across Europe. Every install I describe here is something I've handled personally.*

*Last updated: July 2026*