A modpack server can be the best way to bring a friend group back to Minecraft. New dimensions, tech lines, magic, bosses, quests, and shared goals give everyone a reason to come back the next night. It is also the type of server most likely to crash before the first player joins.
Most of the time, the host is not the real problem. The issue is usually the wrong file bundle, an undersized plan, or players joining with a different version. This guide explains what to check before launch and how to set up a modpack server so the first session is about playing, not reading crash logs.
A client pack is not a server pack
CurseForge and similar launchers primarily install the client pack. That belongs on the player's computer and may include things a server cannot use: minimaps, shaders, graphics optimizers, menu changes, voice-chat clients, or cosmetic mods.
A server pack is a separate bundle prepared by the modpack author for server hosting. It usually includes the right loader, configs, server-side mods, scripts, and files needed for first startup. The server pack is why some modpacks boot on the first try while others fail before the world is created.
If a modpack server crashes immediately, the first question should be: "Are we actually using the server pack?"
How to choose a modpack for a group
Before you pay for anything or invite players, check four things:
- Loader and Minecraft version. Forge, Fabric, and NeoForge are not interchangeable. Players need the same combination as the server.
- Pack size. A small Fabric pack behaves very differently from All the Mods with several hundred mods.
- Server pack availability. If the author does not provide a server pack, it may still be possible, but expect more manual work and testing.
- Play style. Quest-driven RPG packs work well for groups that want shared objectives. Sandbox kitchen-sink packs are better for players who split up and build their own projects.
For ideas, see our list of modpacks to play with friends. It is not just a popularity list; each pack has a different reason it works in multiplayer.
How much RAM does a modpack server need?
RAM matters more for modpacks than for vanilla. Not because each player uses a huge amount of memory, but because hundreds of mods load before the first player connects.
As a rough starting point:
- lighter Fabric packs: 6 to 8 GB,
- medium Forge or NeoForge packs: 8 to 10 GB,
- large kitchen-sink modpacks: 10 to 16 GB,
- very heavy packs with custom worldgen and more players: plan higher.
RAM is not the only factor. High view distance, chunk loaders, large automation builds, and extra dimensions can all cause problems. If the server starts fine but gets laggy after hours or days of play, the world may simply be doing much more work than it did on day one.
The VoxelRun flow
VoxelRun is designed to avoid the most common modpack-hosting mistake: uploading the client pack to the server.
- Choose a pack from modpack hosting or during server creation.
- VoxelRun tries to find the author's server pack and uses that instead of client files.
- For known packs, you get a recommended plan based on the pack's server files and size.
- Let the first startup finish. Large packs may spend a few minutes downloading files and generating configs.
- Send players the modpack name, version, and server address. Without the same version, they will not join.
If a pack has no server pack, you can still use a custom server ZIP, but test it before the night everyone is waiting to play.
What to send players before they join
Most modpack problems happen on player machines, not on the server. Send this to the group chat:
- exact modpack name,
- modpack version,
- launcher to install it with,
- server address,
- whether whitelist is enabled,
- recommended client RAM in the launcher, if needed.
For large packs, it is normal for the client to need 6 to 10 GB RAM on the player's computer. That is separate from server RAM. If someone's game crashes while loading the main menu, the server may not be involved at all.
Common errors and what they usually mean
The server crashes immediately. The pack probably contains a client-only mod, a missing dependency, or the wrong loader version. Confirm that you are using the server pack.
A player sees a missing-mod error. The client and server do not have the same modpack version. Have the player reinstall the exact pack version.
The server runs, but the world loads slowly. Lower view distance, check world pregeneration, and watch for extra dimensions or chunk loaders.
Lag appears after a few days. Look at entities, automation, mob farms, and permanently loaded chunks. Adding RAM alone may not fix it.
Forge, Fabric, or NeoForge?
You usually do not choose the loader freely; the modpack chooses it for you. Older large packs often use Forge, modern 1.20+ packs increasingly use NeoForge, and lighter or optimization-focused packs are often on Fabric.
The important thing is not to mix them. A Forge pack will not run as a Fabric server, and the reverse is also true. With a server pack, the author has already handled the loader choice, which is another reason to use it.
When to choose a bigger plan
Choose a bigger plan if:
- the modpack has hundreds of mods,
- more than 5 or 6 players join at once,
- the world generates many structures or dimensions,
- the group uses chunk loaders and tech automation,
- logs show frequent GC pauses or "Can't keep up" messages even with few players online.
With pay-as-you-go pricing, a bigger plan is not automatically a big monthly commitment. If you play a few evenings a week, the difference between plans is often less painful than losing the whole evening to lag.
Bottom line
Modpack hosting is most reliable when you follow three rules: use the server pack, size the plan for the pack, and send players the exact version. Most "mysterious" crashes trace back to one of those.
Once the server is running, a modpack is just another Minecraft world: start it when the group plays, stop it after the session, and keep the world ready for the next night.