How to Use Crucible for Modded Minecraft Servers

Want to run a Minecraft 1.7.10 server with both Forge mods and Bukkit plugins? That used to be impossible. Crucible changes that, letting you load them side by side on the same server without constant conflicts.

What's Crucible and Why Does It Matter

Crucible is a 1.7.10 server implementation that bridges two normally incompatible worlds. Forge handles mods. Bukkit handles plugins. Usually you pick one. With Crucible, you get both running simultaneously on the same server instance.

The project started as an improved fork of Thermos, which itself was trying to solve this problem back when 1.7.10 was current. But Thermos development stalled. Crucible picked it up and kept going, adding bug fixes, performance improvements, and modern Java support (Java 8 through 21). If you're still on 1.7.10 and frustrated by the mod-or-plugin choice, Crucible is probably your only real option.

Why does that matter in 2026? Because 1.7.10 never actually died. Not in the way newer versions did.

Why Minecraft 1.7.10 Still Exists (And Thrives)

1.7.10 came out in 2014. Honestly, by modern standards, that's ancient. But it became the golden age for a specific kind of server: the heavily modded survival experience where plugins could manage the ecosystem and gameplay mechanics Forge mods couldn't touch.

Modpacks from that era still have active communities. SkyFactory, Infinity Evolved, Project Ozone, GT New Horizons. These are thousands-hour time investments for dedicated players. Some servers have been running the same 1.7.10 world continuously since 2015. Migrating to 1.20+ means losing years of progress, custom builds, and specialized mods that never got ported forward.

Is it nostalgia? Sure. But it's also practical. If your player base loves 1.7.10 and you need both mods and plugins, Crucible is the path of least resistance.

Installing and Building Crucible

Crucible is a build-from-source project, which sounds intimidating but isn't bad once you know the steps. You need Java 8 JDK minimum, and JAVA_HOME set in your system environment.

Clone the repository and set up the workspace:

git clone https://github.com/CrucibleMC/Crucible.git
cd Crucible./gradlew setupCrucible

That setupCrucible command patches the Bukkit and Forge source trees, which takes a few minutes depending on your machine. Once it finishes, build the distribution packages:

./gradlew buildPackages

Your compiled server jar appears in build/distributions/. The file size is substantial (it's a standalone jar with all dependencies bundled), but that's intentional. You don't have to manage a separate libraries folder manually.

Drop it in your server directory, give it the usual startup memory flags, and you're running. One jar. Both mods and plugins. Actually that simple, once the build completes.

What Works

The headline feature is obvious: mods and plugins coexist. But the real story is stability and Java 9+ support, which old Thermos installations seriously lacked.

Java 8-21 Compatibility. Modern hosting doesn't offer Java 8. Most default to Java 11 or 17. Crucible uses an integrated version of lwjgl3ify to handle the version jump without rewriting mod code. Your 2014-era mods run on 2025-era Java. It's not magic, but it's close enough.

TimingsV2 Implementation. Ever run a massive modded server and wondered where your TPS is actually going? Thermos had no built-in profiler. Crucible includes TimingsV2, the same per-tick performance breakdown that Paper popularized. You get granular visibility into what's eating your CPU: Is it that one mod? A specific plugin? One player's chunk loaders?

Updated Libraries. Thermos locked in old Bukkit/Spigot libraries from 2014. Plugins written for later Bukkit APIs would crash immediately. Crucible backports newer Bukkit APIs to 1.7.10, so modern plugins have a fighting chance. Not everything will work (1.7.10 still has 1.7.10 limitations), but the compatibility surface is way broader.

Standalone Jar. The latest releases ship as a single executable jar with a library manager. So it auto-verifies and sets up dependencies on first run, just like modern Bukkit servers do. No more manual library installation.

Common Pitfalls and What Trips People Up

Mods and plugins don't always play nice, even on Crucible. Here's what breaks things:

First: some mods hook into Minecraft's rendering or networking layers in ways that conflict with Bukkit's packet handling. If a plugin that manipulates player movement meets a mod that does the same, you get inconsistency. The server disagrees with the client about where things are. Test your mod-plugin combinations in a dev server before committing them to production.

Second, the NecroTempus companion mod. Some Crucible features require it. If you skip installing NecroTempus and expect certain APIs to work, they won't. The project's documentation lists which features need it, but it's easy to miss.

Third: plugin developers sometimes assume certain Bukkit behavior that 1.7.10 doesn't support. You might find a plugin that claims 1.7.10 compatibility but silently fails to do half its job. Test your key plugins in a staging environment first. The Crucible Discord channel is pretty responsive if something's broken and you're not sure why.

Building, Patching, and Contributing

Crucible uses a patch-based workflow. If you fork the project and make local changes, you can generate patch files:

./gradlew genPatches

This is useful if you're customizing Crucible for a specific server need without maintaining a permanent fork. Generate patches, share them, or apply them later.

The project is actively maintained, with releases roughly every few months fixing reported issues. Recent builds fixed VerifyError crashes in coremods and added the library manager. If you find a bug, the project welcomes reports on GitHub and the Discord community.

Better Than Thermos, Not Perfect

Crucible solves a real problem that Thermos abandoned. Stability is better. Performance is better. Java support is better. But it's not a modern server like Paper or Purpur; it's a 1.7.10-first implementation with plugins bolted on.

If you actually need Minecraft 1.20+, use a current version. If you're maintaining a legacy 1.7.10 server for modpacks or established player bases, Crucible is the practical choice. It's been refined enough that I'd trust it for a permanent server, especially with TimingsV2 to catch performance regressions early.

Want to organize your Minecraft worlds or test plugin functionality before deploying? The Minecraft Block Search and Minecraft Whitelist Creator tools on minecraft.how can help manage your server setup alongside Crucible.

Alternatives Worth Knowing

If 1.7.10 isn't your target version, other hybrid approaches exist. Mohist supports newer versions (1.12+) with mod and plugin support, but it's a different codebase with different maturity. For pure modding, Forge dominates. For pure plugins, Paper or Spigot on any version. Crucible's only real competitor is an old Thermos installation, and Crucible wins that comparison clearly.