What a modpack is
A modpack is a ready-made set of mods with their configs, put together by one author and published as a single file. Instead of installing twenty mods and tuning them yourself, you pick a modpack and we build your server around it.
We pull modpacks from Modrinth and CurseForge, and only show the ones that run on a server. Switch between the two sources above the search box.
Install one
In the Modpacks tab, search for the one you want and press install.
We take a backup first, then:
- We switch your server type and version to what the pack needs, so a Fabric pack makes your server Fabric
- We remove only the files the previous pack put there, and leave everything you added alone
- We download every mod in the pack and lay its configs down in their place
- We start your server again
The install takes one to ten minutes depending on the pack's size. You can watch every step on screen.
The mods that can't run on a server
Plenty of modpacks ship mods that only work in the player's own game, such as shaders, minimaps, rendering tweaks and menus. Those do nothing on a server, and some of them stop it from starting at all.
We leave them out during the install: we ask Modrinth, mod by mod, whether it runs on a server, and back that with our own list of names known to be player-only. Anything another kept mod depends on is protected, so we never break a working mod on the way. Shaderpacks and resourcepacks never reach your server in the first place.
CurseForge
Some CurseForge mod authors block downloads outside their own site. When a pack carries one of those, we look for it elsewhere: first on Modrinth, then inside the server packs the pack's own author publishes on CurseForge, because those files ship those mods on purpose. Find it in either place and the install carries on without you.
If neither has it, we don't install the pack half-finished and we don't start your server on a missing mod. The install finishes, your server waits, and a Files needed page opens on your server listing every file we still need. Each one carries a link to its page on CurseForge and an upload box right beside it. Download the file in your browser, drop it in, and we check that it's the exact one the pack asks for. Once every file is in place, your server starts.
After the install
The modpack becomes your server's identity: it decides the server type, the Minecraft version and the loader build. The Version tab shows the pack at the top: its logo, the release you're on, the Minecraft version and loader, how many mods it laid down, how much space they take, when it was installed and who made it, with a link to its page. Update modpack and Remove live right there, and a button takes you to the Modpacks tab to browse for another one.
The type and version switcher stays below it. Applying any change there removes the pack in the same step, and the warning above the switcher says so before you touch anything.
Mods still install on top from the Mods tab, and they run on the pack's own loader.
Your server address doesn't change:
your server address appears here
Update it
When the pack publishes a new release, an Update available badge appears on the Version tab and an Outdated badge next to its name in the Modpacks tab. Press update in either place and we run the same steps with the new release, with a backup first.
Remove it
Press Remove on the Version tab, or the delete icon in the Modpacks tab. We take a backup first, then remove the pack and the mods and configs we put there. Anything you installed yourself stays. The world you built on the pack is kept under a new name, such as world-rlcraft-old, and your server goes back to the same type and version without a modpack, with a fresh world.
Changing your server type or version while a pack is applied removes it the same way: the pack and its mods go, the world is kept under a new name, and your server comes back on the type and version you picked.
When that happens, or when an install never finished, the pack keeps showing on the Version tab with a Not installed yet badge, and in the Modpacks tab with an Outdated badge, so you know your server isn't on it. Press Remove to clear it for good.
Limits
- The modpack file itself must be under 256MB
- Each file inside the pack must be under 512MB
- The pack must list fewer than 1024 files
Most modpacks are far smaller than that. If a pack goes over a limit, you get a clear reason and your server is left as it was.
Modpacks and crossplay
Crossplay works with modpacks on Fabric and NeoForge. We reinstall Geyser and Floodgate on the first start after a modpack install, so there is no need to turn crossplay off and on again.
Choose the release before installing
Select a modpack release in the catalog and check its Minecraft version and loader in the preview. Available files are downloaded and verified before replacing the previous installation. Restricted CurseForge files still require your upload before the server can start.
The Modpacks tab shows the exact pack release players need on their computers. Ask friends to install the same release before joining.
Did this guide help you?
Improve this guide
Guides are open source. Found a fix or an addition? Open a pull request on github.com/serverkgg/minecraft-java