Quick answer
PocketMine-MP is from-scratch php bedrock server (archived). Historically provide a lightweight, highly extensible Bedrock server and PHP plugin ecosystem.
| Developer / maintainer | PMMP community (historically) |
|---|---|
| Software type | From-scratch PHP Bedrock server (archived) |
| Upstream / lineage | Independent Bedrock server implementation built from scratch in PHP/C/C++. |
| Current status | Legacy / status |
| Best fit | Existing legacy PocketMine deployments that need status/migration information. It is no longer an appropriate default for a new server after archival. |
Who develops PocketMine-MP?
PMMP community (historically) develops or maintains this project. Independent Bedrock server implementation built from scratch in PHP/C/C++.
This matters because “Minecraft server software” covers very different kinds of projects. Some are direct forks of Paper, some are mod loaders, some are compatibility layers, some are proxies, and some reimplement the server from scratch. The lineage above tells you what ecosystem, APIs, and operational assumptions carry over.
What is its main goal?
Historically provide a lightweight, highly extensible Bedrock server and PHP plugin ecosystem.
A good reason to choose a server implementation is that its design goal matches a real requirement you have. Switching only because a fork is advertised as faster, more configurable, or more modern usually creates extra compatibility work unless you can name the problem it solves for your server.
How is it different from normal Minecraft?
PocketMine-MP reimplemented Bedrock behavior and historically prioritized plugin extensibility over exact Vanilla parity.
“Vanilla compatibility” can mean several things: the same client protocol, similar gameplay, identical redstone/farm behavior, the same world format, or simply the ability for an unmodified client to join. Those are not equivalent. For technical survival, modded worlds, or long-lived production servers, test the exact behavior you depend on.
How does it differ from its upstream or related forks?
Unlike Mojang BDS it had a PHP plugin ecosystem and independent engine. It is also distinct from Java Nukkit/PowerNukkitX projects.
Fork relationships are especially important for plugins and configuration. A downstream fork usually inherits much of its upstream API, but extra patches can change internals, scheduling, defaults, and edge-case mechanics. The closer a plugin is to undocumented internals, the less useful a generic “Paper-compatible” or “Bukkit-compatible” label becomes.
What type of server is PocketMine-MP good for?
Existing legacy PocketMine deployments that need status/migration information. It is no longer an appropriate default for a new server after archival.
For a new server, start with the simplest software that meets the requirement. More layers—especially hybrid plugin+mod stacks or multithreaded forks—mean more combinations to test when Minecraft, Java, plugins, or mods update.
Plugin, mod, and ecosystem compatibility
PocketMine plugins for its API; not Bukkit/Paper/Nukkit plugins.
Always match extensions to the exact Minecraft version and software family they target. A JAR being Java does not make it universally compatible, and a plugin/mod loading successfully does not prove every code path is safe.
Stability and project maturity
The official GitHub repository was archived by its owner on July 9, 2026 and is now read-only. The final indexed release 5.44.3 was published July 6, 2026 for Bedrock 1.26.30 / display version v26.30.
Current version note: Archived / no longer actively maintained in its official repository as of July 9, 2026.
MSH does not assign a numeric stability score. Release status, maintenance activity, official warnings, supported Minecraft versions, architecture, and ecosystem compatibility are more useful than a single rating. A mature project can still be the wrong fit, while a beta project can be useful for a team that deliberately accepts the risk.
Before switching to PocketMine-MP
Migration checklist: Maintenance warning: the pmmp/PocketMine-MP GitHub repository was archived on July 9, 2026. Check the project’s current maintained distribution/status before planning a new long-lived deployment. PocketMine-MP is a Bedrock-oriented PHP server, not a Java/Paper plugin host.
How to verify: Before migration, confirm Bedrock client compatibility and the intended PHP/PocketMine plugin API. Test world import and feature parity on a disposable server; Java plugin JARs will not load as PocketMine plugins.
Existing servers should plan around an unmaintained upstream: no future protocol/security/game updates should be assumed. Evaluate maintained Bedrock alternatives before the next forced client protocol change.
If the server contains modded blocks/entities, switching away from the loader or mods that created that data can permanently damage a world. If the change involves proxies or threading models, compatibility problems may appear only when players move between servers or when plugins access data concurrently.
Official references
These primary project sources were checked on September 23, 2026. Software status changes quickly, so the linked project documentation should win over this article if a newer release changes support or requirements.
Related server software
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.