Pumpkin-MC/Pumpkin

The problem

Running a Minecraft server today usually means running a JVM server — Vanilla, Paper, or a fork — where garbage collection pauses show up as lag spikes under load, and where the plugin ecosystem drags along a large, legacy API. Administrators who want predictable tick times and cheap hosting end up tuning JVM flags instead of running their world. Pumpkin is a from-scratch Minecraft server written in Rust that aims to reproduce vanilla mechanics while using multi-threading for performance and offering TOML configuration instead of the usual mess of server properties.

What's different

The obvious comparisons are Vanilla and Paper. Pumpkin's pitch is architectural: native code with no JVM, so memory and CPU behavior are different by construction rather than by tuning. It also targets both Java and Bedrock editions from one server binary, which normally requires separate servers or a proxy layer, and ships its own plugin surface with a separately MIT/Apache-licensed plugin API. It speaks the common proxy protocols — BungeeCord, BungeeGuard, Velocity — so it can slot into existing networks. The trade-off is maturity: Paper has a decade of plugin ecosystem and bug reports behind it, and Pumpkin does not.

Who it's for

Server operators and network admins who run small-to-medium Minecraft communities and are comfortable with early software, especially those already hosting on Rust-friendly infrastructure or wanting Bedrock clients on the same world without an extra translation layer. It is not for admins who depend on a specific Spigot/Paper plugin — that ecosystem does not exist here — nor for anyone running a public server where an unfinished feature would mean lost players. Plugin developers curious about a non-JVM server API may find it interesting.

Cost of adoption

The README is explicit that Pumpkin is under heavy development, with an open issue tracking what is needed before 1.0.0. Its own feature list shows work still in progress on core gameplay: chunk generation, redstone, combat, entity AI, and mobs are all marked W.I.P. or unchecked, and Bedrock support is partial. So running this today means accepting gameplay gaps, not just polish issues. It requires a Rust build environment or the Docker image referenced in the topics, and the server is GPLv3 — relevant if you plan to distribute modifications. Setup instructions live in the external Quick Start docs, not the README. Maintenance signals are strong in activity terms, but the project is young: created in mid-2024.

Verdict

Pumpkin is a genuine attempt at rebuilding the Minecraft server rather than another fork, and the Rust foundation is a real differentiator against Vanilla and Paper. The momentum is notable — roughly 12.6k stars and +1,330 in a single month on the Rust board — but it has never appeared on the daily trending board, so much of that attention is recent rather than sustained. With the 1.0.0 checklist still open and redstone, combat and chunk generation incomplete, this is a project to watch and test, not one to migrate a production community onto. Give it a try on a private world and follow the issue tracker; revisit when the gameplay gaps close.