Cardboard: Running Bukkit Plugins on Fabric Servers

What Cardboard Does (and Doesn't)

Cardboard is a Java project that lets you install Bukkit plugins on a Fabric server. That's the pitch. If you've ever wanted to run the Fabric mod ecosystem alongside Bukkit's decade-old plugin library, Cardboard bridges that gap. With 1161 stars on GitHub, it's got a solid community behind it, but it's worth understanding what you're actually getting before setting up a production server.

Here's the real appeal: Fabric mods and Bukkit plugins solve different problems. Fabric gives you low-level mod development with tight integration into the game engine. Bukkit plugins are lighter-weight, run in a sandboxed environment, and dominate the plugin ecosystem for admin tools, permissions systems, and game mechanics. Cardboard lets you have both on one server.

Why You'd Actually Want This

Think about what a typical community server needs. You want grief protection (Bukkit plugin). Anyone want visual enhancements or mod-based mechanics (Fabric mods). Anyone want permission management and rank systems (Bukkit plugins). Anyone want performance optimizations that only exist as Fabric mods. Normally, you'd have to choose.

If you've run a Spigot or Paper server before, the appeal is obvious. Cardboard lets you reuse all that knowledge and all those plugins you've already configured, while also running Fabric mods that don't exist as Bukkit plugins. The alternative is either maintaining two completely separate servers or rewriting plugins from scratch as Fabric mods (which is... a lot of work).

The catch is compatibility.

Current Version Support and Reality Check

Cardboard currently supports Fabric 1.21.8 (active development), 1.21.4 (low support), and 1.21.1 (low support). Versions 1.20 and below are no longer supported. If you're on an older version, you'll need to update your server first.

"Low support" means bug fixes and feature additions happen mainly for 1.21.8. If you report an issue on 1.21.1, don't expect the same response time. This is a volunteer-driven project with limited resources, so they're focusing on the latest version.

Not every Bukkit plugin will work perfectly. Cardboard implements the Bukkit API on top of Fabric. That means it has to translate between two fundamentally different architectures. Some plugins depend heavily on Spigot's internal code (called NMS, or net.minecraft.server). Cardboard can remap these classes automatically, but as the developers note, the system "is far from perfect."

How to Set It Up

Installation isn't as simple as dropping a JAR into your plugins folder because Cardboard IS your server. Here's the process:

1. Download the Cardboard build for your Minecraft version from cardboardpowered.org.
2. Create a fresh server directory and place the Cardboard JAR there.
3. Run the server once to generate server.properties and other config files.
4. Stop the server and drop your Bukkit plugins into the plugins folder (just like you would on any Bukkit server).
5. Start the server again and configure your plugins as needed.

For testing before you commit to production, grab a free subdomain using the Free Minecraft DNS tool at Minecraft.How. It takes two minutes and lets you point a domain at your test server without paying for hosting.

The learning curve is minimal if you've used Bukkit or Spigot before. If you're new to server administration, this adds an extra layer of complexity you probably don't need. Start with vanilla Fabric or regular Spigot first.

Plugin Compatibility: What Might Break

Before migrating a production server, test your essential plugins on a staging instance. This is non-negotiable.

Some plugins rely on Bukkit features that Cardboard implements. Others depend on internals that Cardboard's remapping can't handle. The project uses SpecialSource and SrgLib for remapping Spigot classes to their Fabric equivalents, which handles many cases but not all. If a plugin modifies entity behavior by reaching deep into Minecraft's internals, it might break or require fixes.

The maintainers maintain a Discord channel with pinned progress indicators showing what's known to work and what's still rough. Check there before testing plugins. Knowing in advance that "plugin X has issues with NMS remapping" saves hours of debugging.

Actually, even popular plugins sometimes have issues. A permissions plugin that works perfectly on Paper might misbehave on Cardboard due to subtle differences in how events fire or how the server tick works. And this is why staging is essential.

Practical Tips and Gotchas

Here's what trips people up most: assuming Bukkit compatibility means "everything just works." It doesn't. Treat it as "most things work, test first."

Second gotcha: mixing Fabric mods and Bukkit plugins can create weird interactions. If a Fabric mod modifies block breaking and a Bukkit plugin wants to prevent block breaking, you might hit edge cases. The mod acts at a lower level than the plugin, so it can bypass some plugin logic. Test realistic scenarios.

Third: the project is actively developed but focused on the latest version. If you're on 1.21.4 and hit a bug, updating to 1.21.8 might fix it, but you can't always stay on old versions.

If you're setting up complex permissions or grief protection, don't assume Bukkit plugins designed for Paper will just transplant. Spigot NMS is one compatibility layer; Cardboard's remapping is another. Two layers of compatibility means two places where things can subtly break.

When to Use Cardboard (and When Not To)

If you're running a small friend server and want both Fabric mods and Bukkit plugins, Cardboard is worth testing. If you want Fabric-only, don't use it; just run Fabric. If you want pure Bukkit plugins with zero mods, use PaperMC instead.

The sweetspot is: you've got a set of Bukkit plugins you love, there are Fabric mods you also want, and you're willing to test compatibility before going live. If any of those three things aren't true, a simpler option probably exists.

Large public servers often avoid Cardboard because the compatibility risk is higher and the payoff isn't always worth it. If you're hosting for hundreds of players, stick with Paper or Spigot. If you're hosting for friends, Cardboard is worth experimenting with.

Alternatives and Comparisons

If you want plugins without mods, Paper is simpler and more stable. If you want mods without plugins, use Fabric directly or Quilt. If you want a Fabric plugin system, look at Quilt Loader's plugin spec or Fabric API's module system.

Cadix is another project attempting similar goals, but it's less mature. Mohist tried something similar for Forge and struggled with maintenance. Cardboard works partly because the Bukkit API is well-documented and the remapping tools (SpecialSource, SrgLib) already existed.

The real advantage of Cardboard over building something yourself is the community work already done. You're not reinventing plugin compatibility; you're using years of the Bukkit, Spigot, and Paper teams' effort.

The Community and What's Next

The project has a Discord with active maintainers and testers. Apex Hosting runs a public test server at cardboardmod.apexmc.co:25666 if you want to see it running before setting up your own. That's genuinely helpful for understanding what a working Cardboard server feels like.

For admin tools and configuration, the block search tool at Minecraft.How is handy for quickly looking up block IDs and properties when configuring Bukkit plugins or Fabric mods.

Development is ongoing. The project credits the Bukkit, Spigot, and Paper teams (whose GPL-3.0 licensing it inherits), plus Glowstone for the library loader and the developers behind SpecialSource and SrgLib. It's a community effort built on years of prior work.

If you're considering Cardboard, join the Discord, test a plugin list on a staging server, and check the progress indicators for your version. If your plugins work and you've tested mods alongside them, you've got a solid hybrid server. If anything breaks, fallback is straightforward: move your plugins to a PaperMC server instead.