PaperMC/Paper

Paper is a Minecraft Java Edition server built as a patch series over the official vanilla server, aimed at fixing gameplay and mechanics inconsistencies while improving performance. It is aimed at server administrators who want to keep vanilla-style gameplay, and at plugin developers who want a stable server API.

Two ways to use it

Server administrators download the Paperclip jar from the downloads page and run it like a normal jar on their server downloads page. No source build is involved on this path. The project documentation covers operation and configuration Paper documentation. Hacker News commenters from 2024 described replacing the vanilla server jar with Paper's as the migration route; one hosting operator said they had moved all their servers to Paper for reliability with vanilla gameplay comment on replacing the jar and hosting operator's account.

Plugin developers depend on paper-api from PaperMC's Maven repository with a provided scope; the README shows Gradle and Maven snippets and sets the Java toolchain to 25 API setup. The API source and javadocs are linked from the repository Paper API source, javadocs.

What changes in practice

The practical effect is that existing vanilla worlds and plugin ecosystems carry over, while the server gains performance work and mechanics fixes. Because Paper is a patch series rather than a fork rewritten from scratch, the maintainers describe conversion as dropping in a different jar — though the README itself does not promise a round-trip path back to vanilla.

Requirements and constraints

Building the jar from source requires JDK 25 and an internet connection, followed by the Gradle patch and packaging tasks README instructions. Most admins should not need this path.

A licensing point raised in discussion: Paper does not ship binaries of Mojang's proprietary code; users obtain the server through Paper's download/build process because redistributing Mojang's binaries would infringe copyright comment on licensing. The repository's license is listed as NOASSERTION, so anyone embedding or redistributing parts should check the terms rather than assume a standard open-source license.

Versions 1.21.3 and below now live in a separate archive repository, so older-version users need to look there archive repository.

Scope of evidence

The README and docs describe purpose, paths and build prerequisites; there is no supplied benchmark data, compatibility matrix, or evaluation of plugin breakage across versions. The Hacker News thread (2024) shows discussion interest, not measured performance.