Bukkit, Spigot, Paper: the History of the Invisible Software Behind Every Server

Think of the last Minecraft server you played on. The one with ranks, a lobby with NPCs, a command to teleport you home, perhaps a minigame with its own points system. None of that — absolutely none of it — was made by Mojang.

It was made possible by a layer of software the player never sees and to which it owes everything. It has names that sound like garage tools: Bukkit, Spigot, Paper. And behind those names there is a story of volunteers, one fork after another, and a legal dispute that in 2014 came close to wiping it out overnight.

Mojang's server couldn't do any of that

The official Minecraft server, the one Mojang hands out, does one thing: it lets you play the game. It has no ranks, no permissions, no custom commands, no way of installing a plugin. For Mojang, that was enough. For the community, it wasn't.

So the community built what was missing. After some early attempts such as hMod, Bukkit appeared in 2011: a layer that sat on top of Mojang's server and offered something revolutionary — an orderly way for anyone to write plugins. CraftBukkit was the piece that made it work. Suddenly you didn't need to know how to poke around in the game's innards to add a clan system or a market: you just had to install a plugin someone else had written.

That changed everything. The explosion of servers in the golden age — the minigames, the economies, the ranks — was born there.

When Mojang hired the people who made it

The story has an early twist: in 2012, Mojang hired the Bukkit team. It made sense — they were the people who best understood how to extend the game — but it also sowed an ambiguity that would blow up later. Whose, exactly, was Bukkit? The community that maintained it, or the company that was now paying its developers?

For a couple of years, nobody needed to answer that question. Until someone asked it out loud.

The 2014 dispute that nearly killed it

In 2014, a Bukkit contributor called Wesley Wolfe raised an awkward problem: CraftBukkit included decompiled code from Minecraft itself, and that clashed with the licence under which it was distributed. To force the issue, he filed a legal claim — a DMCA — which, in practice, halted Bukkit's distribution almost overnight.

It was a moment of panic. Thousands of servers depended on that software, and suddenly its future was a legal unknown. What had seemed like solid infrastructure turned out to be, deep down, a fragile arrangement between volunteers that had never been fully put in writing.

Spigot and Paper: life after Bukkit

But open source has a remarkable property: it is hard to kill. Spigot had already been born from Bukkit, a fork focused on performance — it let the server handle more players without choking — and Spigot became the community's new meeting point.

And from Spigot, in turn, came Paper: another fork, faster still and with better tools for plugin authors. Today Paper is, de facto, the ground almost every serious server runs on, including those on the most modern versions, and it has produced derivatives of its own. The full lineage reads almost like a family tree: from Mojang's server came Bukkit, from Bukkit came Spigot, from Spigot came Paper.

Each link was born because someone thought it could be done better, and did it.

What this story says about servers

There's something to learn here, and it goes beyond the technical. The layer the whole ecosystem depends on — every server, every community, every memory we've told in this magazine — was built by people who weren't paid for it, driven by the idea that the game could offer more.

Anyone who sets up a server today, like KobiiCraft, doesn't start from zero: they inherit ten years of invisible work by people whose names appear on no loading screen. Building well, in Minecraft, starts with recognising whose shoulders you're standing on.

The names you never saw

Next time you join a server and use a command as trivial as teleporting home, it's worth a second of remembrance. That command exists because, years ago, someone decided to give the world a way to write it. They weren't paid, you didn't see them, you probably don't know their name.

The most important software we use tends to be exactly that: the kind that works so well it becomes invisible, made by people who never asked to be seen.

Frequently asked questions

What are Bukkit, Spigot and Paper? They are the layers of software that let a Minecraft server use plugins, something Mojang's official server doesn't support. Bukkit (2011) was the first standard plugin API; Spigot grew out of Bukkit with a focus on performance; and Paper grew out of Spigot, faster still and with better tools. Today, almost any server with ranks, commands or minigames runs on one of them, usually Paper.

What happened to Bukkit in 2014? A contributor, Wesley Wolfe, pointed out that CraftBukkit included decompiled Minecraft code, which conflicted with its licence, and filed a legal claim — a DMCA — that halted Bukkit's distribution almost overnight. It was a moment of crisis for the thousands of servers that depended on it. The community survived by migrating to the forks that already existed, above all Spigot.

Why do almost all servers use Paper today? Because it is the most optimised and convenient fork in the family: it handles more players without choking and gives plugin authors better tools than its predecessors. Since it inherits from Spigot, which in turn inherited from Bukkit, it is compatible with almost the whole plugin ecosystem. For a modern server, building on Paper is simply the path with the least friction.

Who made the software Minecraft servers use? Community volunteers, not Mojang. The official server doesn't support plugins; the whole layer that does — Bukkit, Spigot, Paper and their derivatives — was built by people working for free, convinced the game could offer more. It is one of the most widely used pieces of Minecraft infrastructure and, at the same time, one of the least recognised.