Hybrid servers: Forge/NeoForge mods and Bukkit plugins together
Updated · MCJarHub
Hybrids implement the Bukkit plugin API on top of a mod loader, so a modpack server can also use permission, economy or protection plugins. They work, but they are the least stable option: always test your exact mods and plugins together.
Hybrid servers on MCJarHub (live data)
Minecraft versions each hybrid covers
| Hybrid | Versions on MCJarHub | Latest build id |
|---|---|---|
| Mohist | 1.20.2 1.20.1 1.20 1.19.4 1.19.2 1.18.2 1.16.5 1.12.2 1.7.10 | 1.20.2-2371352a |
| Arclight | 26.1.2 1.21.11 1.21.1 1.21 1.20.4 1.20.2 1.20.1 1.20 1.19.4 1.19.2 1.18.2 1.17.1 1.16.5 | 1.0.0-SNAPSHOT-f98b864-fabric |
| Magma | 1.21.1 1.21 1.20.1 1.19.3 1.18.2 1.12.2 | 21.1.70-beta |
Arclight build ids end in the mod loader they target (-forge, -neoforge or -fabric). These hybrid files currently come from the mcjars.app community mirror and are labelled as such on each page.
How hybrids work — and why they break
A hybrid implements the Bukkit/Spigot plugin API on top of a mod loader: Arclight describes itself as "a Bukkit server implementation on common mod loaders". Plugins then run next to Forge or NeoForge (or, for some Arclight builds, Fabric) mods.
The catch: plugins were written for Spigot or Paper, not for a world full of modded blocks and entities. Plugins that use server internals (NMS), protection plugins that don't know modded blocks, and some anti-cheat plugins are the usual problems. Updates also arrive later than for the underlying loader.
Before you choose a hybrid
- Check whether a mod can do the job instead — many permission, claim and utility features exist as Forge/NeoForge/Fabric mods.
- Match the hybrid to your modpack's Minecraft and loader version.
- Test your exact mod and plugin list on a copy of the world before going live, and keep backups.
Related: modded servers · plugin servers · best server software for your use case.