Somebody wants land claims. Somebody else wants a mod that adds dragons. And the person setting up the server has been staring at a list of software names for ten minutes.
Start with what the group wants to play. That usually settles the software question much faster than a comparison of logos.
For plugins, start with Paper. For a modpack, follow the pack.
Paper is a sensible choice for homes, claims and permissions. A modpack will tell you whether it needs Fabric, Forge or NeoForge, including the version. Use that combination. Vanilla is still an option if you want the official server without a plugin or mod loader.
Minecraft Java EditionThe feature list makes the decision
Pick two or three things the server needs. Then find the plugins or mods that provide them. A small survival world with a /home command is a different project from a world with factories and three new dimensions.
For a published modpack, most of this work is already done. Look for its server files and installation notes. Don't switch loaders because somebody online says another one is faster; it still has to run your pack.
| What you want | Start here |
|---|---|
| The official game without add-ons | Vanilla |
| Claims, homes, permissions and plugins | Paper |
| A particular mod or modpack | Its required Fabric, Forge or NeoForge build |
Paper makes sense for a lot of friend servers
Compatible plugins go in the plugins folder. Restart the server, then check the startup log to see whether they loaded. A missing dependency or the wrong Minecraft version is usually a better lead than trying the same restart five more times.
Many Paper setups let players join with an ordinary compatible Java client. Check the plugins you choose: some features use resource packs or ask for extra client software.
There is one catch worth knowing before you move a technical world. Paper changes some vanilla behavior. If the group has spent a month perfecting a very particular farm, test it on a copy first.
Let the mods pick their loader
Fabric, Forge and NeoForge are separate targets. A mod might offer several downloads, but you still need the one for your loader and Minecraft version. Check its dependencies while you're there; some Fabric mods also need Fabric API.
Whether players need the same mods depends on what those mods do. Some utilities run only on the server. Content mods often need matching files on each player's computer. For a pack, send everyone the exact pack release, not just its name.
This is also why updating every individual mod to its newest release can make a working pack stop working. The pack author chose a set of versions that belong together.
Already have a world? Make a copy first.
Changing software is a migration. A world containing modded blocks needs the software and mods that understand them. Replacing the server file with Paper does not turn those blocks into supported content.
Back up the world, configuration and add-ons together. Follow the migration instructions for your starting and destination versions; world folder layouts can differ.
On the test copy, check the main base, other dimensions, inventories and the farms people care about. Once that works, write down what players need to change and pick a time for the move. Keep the original backup.
A couple more questions
Can I use Paper plugins and Forge mods together?
They are different systems. Start with the software your must-have content supports. Combining ecosystems needs a separate compatibility review; it is not something Paper provides by itself.
Which one is fastest?
There is no useful winner when the content and settings are different. Choose software that runs your game, then measure it with your players online.
Sources & useful links
The technical details behind this guide, if you want to dig further.
Keep reading
Sculk Hosting
Stuck on your own setup?
Send us the game version and what happens when you try. A log or error message helps.