Modding Your Minecraft Server: Forge, Fabric, Paper, and What to Pick

The first time someone tries to add anything to a Minecraft server, they hit a wall of confusing terminology: Plugins. Mods. Modpacks. Forge. Fabric. NeoForge. Paper. Spigot. Bukkit. Quilt. Half of these words mean similar things and half mean completely different things, and there’s no universal “best” option — each serves a real purpose.

This post explains what each of those terms actually is, the practical differences, and how to pick the right one for what you’re trying to do.

The two big questions

Before any of the names matter, you have to answer two questions:

1. Do my players need to install something on their client to connect?

• No → You’re looking at plugins (server-side only). Players connect with vanilla Minecraft.
• Yes → You’re looking at mods (client + server, both have to match). Players install the same mod loader you do.

2. Do you want a moderate, focused enhancement (custom commands, anti-cheat, economy)?

• Yes → Plugins. Use Paper.
• Or do you want a deep gameplay overhaul (new blocks, items, dimensions, mechanics)?
• Yes → Mods. Use Forge or Fabric.

Almost every “should I use X or Y” question reduces to those two. Let’s go through the actual options.

Server flavours: plugin route

These are server software variants designed for plugins. Players connect with vanilla Minecraft — no client mods needed.

Vanilla

The reference Minecraft server software, distributed by Mojang. No plugins, no extensibility — what you get out of the box is what the game does.

Use vanilla when you genuinely don’t need any customisation. It’s the simplest, most stable option.

Spigot

A historical fork of vanilla that added plugin support via the Bukkit API. Active for years; mostly superseded by Paper now. Use Spigot only if you have a specific plugin that won’t run on Paper (rare). For new projects, prefer Paper.

Paper

The modern standard for plugin-based servers. Drop-in replacement for vanilla — better performance, fixed bugs, plugin support. Plugins built for Bukkit/Spigot/Paper all generally work.

Paper is the right default for almost any plugin-based Minecraft server in 2026. Lower tick lag than vanilla, better mob/AI behaviour, exposes more performance toggles, and the developer community is active.

Purpur, Pufferfish, Folia

Forks of Paper with various performance or feature additions:

• Purpur — Paper + extra customisation knobs (per-block tick speeds, mob behaviour overrides, etc.). Useful for niche control.
• Pufferfish — Paper with additional performance optimisations.
• Folia — Paper rewritten for multi-threaded ticking. Big performance gains for very large servers (100+ players, lots of regions). Trade-off: not all plugins work with it yet.

For most servers, plain Paper is the right pick. Branch out only if you specifically need what these forks offer.

Server flavours: mod route

These require both server and client to install the same loader and mod set. Without it, players can’t connect.

Forge

The original Minecraft mod loader. Massive ecosystem — most large modpacks (RLCraft, FTB packs, ATM packs, Vault Hunters, etc.) are Forge-based.

Strengths:

• Largest mod library
• Most popular gameplay-overhaul packs are here
• Well-established tooling

Weaknesses:

• Heavier than Fabric (more memory, slower startup)
• Slower to update for new MC versions
• Mods written for one MC version often don’t run on another without manual updates

Forge’s leadership had a falling-out in 2023 and a community fork called NeoForge has taken over for MC 1.20.2+ in many parts of the ecosystem. NeoForge is API-compatible with Forge for most mods, so users mostly don’t notice the split. For 1.20.2+ modded servers, expect to use NeoForge.

Fabric

A lightweight, minimal mod loader. Started as the modern alternative to Forge, focused on being:

• Faster to launch
• Lower memory overhead
• Quicker to support new MC versions (often within hours of release)

Strengths:

• Lighter and faster than Forge
• Better compatibility with the latest MC versions
• Active dev community
• Several major modpacks now use Fabric (Distant Horizons, ATM Fabric variants, performance-focused packs)

Weaknesses:

• Smaller mod library than Forge (though growing fast)
• Many gameplay-overhaul mods still don’t have Fabric versions

Fabric is the right choice for performance-focused or vanilla-plus servers. If you just want to add Sodium for FPS or Distant Horizons for view distance, Fabric is the cleaner path.

Quilt

A community fork of Fabric that started over governance disputes in 2022. API-compatible with Fabric for most mods. In practice, the ecosystem mostly stayed with Fabric, but Quilt is still around for projects that prefer its philosophy.

For most users, Fabric and Quilt are interchangeable. Pick whichever your modpack uses.

Sponge

A different mod-loader-with-plugin-API hybrid. Less popular than Forge or Fabric. Use it only if a specific mod or plugin you need is Sponge-exclusive (rare in 2026).

So when do I pick what?

A practical decision tree:

Do you want players to connect with vanilla Minecraft (no client mods)?
├── Yes → Plugin route → Paper
│    ├── Tiny server, no performance concerns? → Vanilla works too
│    └── Heavy traffic, lots of automation, performance matters? → Pufferfish or Folia
│
└── No, players will install mods → Mod route
     ├── You want a big modpack (RLCraft, ATM, Create-themed, etc.)
     │    └── Forge or NeoForge (depends on the modpack's MC version)
     │
     └── You want a vanilla-plus experience (Sodium, Distant Horizons, optimisations only)
          └── Fabric

Special cases:

• Hybrid setups (plugins + a few mods on one server): a few projects like Mohist or Magma try to bridge plugins and mods on a single Forge server. These work, but stability is shaky and you lose the simplicity of either pure approach. Avoid unless you have a strong reason.

• Crossplay (Java + Bedrock): this is a separate question — solved by GeyserMC + Floodgate, which run as plugins on Paper or Fabric/Forge mods. See the crossplay setup doc.

How Witchly handles loaders

Witchly’s deploy wizard supports all the common server flavours. Pick Minecraft in the deploy wizard and you’ll see options for vanilla, Paper, Fabric, Forge, and others.

If you’re installing a modpack, the 1-click modpack installer (available on Reactor and Mainframe-tier Minecraft plans) handles loader-and-mod-version matching automatically. You pick the modpack, the installer downloads the right loader and the right mods at the right MC version, and your server is ready.

For custom mod sets:

1. Deploy with the loader you want (Fabric, Forge, NeoForge)
2. Use the dashboard’s Plugin Installer for mods available on Modrinth, Hangar, or CurseForge
3. Or upload .jar files directly via the File Manager or SFTP into your server’s /mods directory
4. Restart the server — mods are loaded at startup

Plugins explained briefly

Plugins are server-side .jar files that extend a Paper/Spigot server. They live in the /plugins folder and load automatically on server start.

Common things plugins do:

• WorldEdit, WorldGuard — terrain editing and region protection
• EssentialsX — basic admin commands (/home, /spawn, etc.)
• Vault — economy/permissions integration layer (other plugins depend on it)
• LuckPerms — modern permissions management
• CoreProtect — block-history logging (catch grief, roll back damage)
• GeyserMC + Floodgate — Java/Bedrock crossplay
• Anti-Cheat (NoCheatPlus, Vulcan, Matrix) — server-side cheat detection
• Custom games (BedWars, Skywars, MiniaturePixel) — entire game-modes wrapped as plugins

The vast majority of small-to-mid Minecraft servers (think under 100 players, no modpacks) run on Paper with 5-20 plugins. That’s the boring, stable, “just works” pattern.

Mods explained briefly

Mods modify the game itself. Both client and server need the same mods installed (and at the same versions, in most cases — mismatches throw errors at connect time).

Common categories:

• Tech mods — Industrial Foregoing, Mekanism, Applied Energistics 2 (automation, factories)
• Magic mods — Botania, Blood Magic, Astral Sorcery
• Adventure mods — Twilight Forest, Aether, dimensions and bosses
• Performance mods — Sodium, Iris, Lithium (Fabric); Embeddium, Oculus (Forge)
• QoL mods — JEI/REI (recipe lookup), Just Enough Items
• Worldgen — Biomes O’ Plenty, Terralith

Modpacks bundle dozens of mods into a curated experience. Major modpacks ship with their own configs and a recommended MC + loader version pair.

Plugin vs mod: a worked example

You want to give players home-warps. Two paths:

Plugin path (Paper)

1. Install EssentialsX on your Paper server
2. Players use /sethome, /home, /tpa — all built into the plugin
3. Players connect with vanilla Minecraft. Done.

This is the simplest possible solution. 99% of “I want X feature on my server” requests are solvable with a plugin.

Mod path (Forge)

1. Install a homes mod (e.g., FTB Utilities or RFTools Utility) on your Forge server
2. Same homes feature, but mod-driven
3. Every player must install the same mod on their client

For “homes,” the plugin path is dramatically easier. Mods make sense when you want gameplay-altering features (new blocks, items, dimensions) — not for QoL admin commands.

Common mistakes when picking

”I want a plugin, but the modpack I like is Forge”

Modpacks lock you into the mod path. If you want a plugin-only server, you can’t run a plugin-only modpack — pick one or the other. (Or use a hybrid loader like Mohist, knowing it’s flaky.)

”I’m going to install Paper plugins on my Forge server”

Doesn’t work. Paper plugins target the Bukkit API, which Forge doesn’t expose. Forge has its own mod system; the two ecosystems are separate.

”I’ll just add this Forge mod alongside my Fabric ones”

Doesn’t work. Forge and Fabric are different loaders — a mod is built for one or the other, not both. Some mods have separate Forge and Fabric ports; check the mod’s download page for the right version.

Picking a popular modpack without checking your hosting plan

Big modpacks demand RAM. ATM10, RLCraft, Vault Hunters all want 6-8 GB allocated to the JVM minimum. If you’re on a 2 GB plan, you can’t run them no matter how clever you are with config. Match plan size to modpack requirements first.

Wrapping up

The whole modding ecosystem is less confusing once you internalise: plugins are server-only, mods require client install, and Paper/Fabric/Forge are different runtime targets that don’t mix.

For 80% of Minecraft servers (small-to-medium, no modpack), Paper plus 10-20 plugins is the answer. For modpacks, follow the loader the pack expects. For vanilla-plus performance setups, Fabric is the lightest option.

For Witchly-specific walkthroughs:

• Installing modpacks — 1-click installer flow
• Installing mods and plugins — manual install via dashboard
• Choosing a Minecraft server plan — which RAM tier fits which modpack