Quick answer
Cloudburst Nukkit is java bedrock edition server. Provide a Java-based, plugin-extensible Bedrock server with an approachable codebase and Nukkit plugin API.
| Developer / maintainer | CloudburstMC team and contributors |
|---|---|
| Software type | Java Bedrock Edition server |
| Upstream / lineage | Nukkit-family Bedrock implementation in Java. |
| Current status | Actively maintained |
| Best fit | Existing Nukkit ecosystems, plugin development, or Bedrock servers whose required plugins target Cloudburst Nukkit. |
Who develops Cloudburst Nukkit?
CloudburstMC team and contributors develops or maintains this project. Nukkit-family Bedrock implementation in Java.
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?
Provide a Java-based, plugin-extensible Bedrock server with an approachable codebase and Nukkit plugin API.
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?
Nukkit reimplements the Bedrock server rather than wrapping BDS. Feature parity and world behavior can therefore differ from official Bedrock.
“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?
PowerNukkitX extends the broader Nukkit lineage with additional modern feature goals. Cloudburst also has a newer Cloudburst server project that originated from Nukkit, so check which project your plugin/server guide targets.
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 Nukkit good for?
Existing Nukkit ecosystems, plugin development, or Bedrock servers whose required plugins target Cloudburst Nukkit.
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
Nukkit plugins for the matching API/protocol. Java Paper plugins and PocketMine PHP plugins are different ecosystems.
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.
Deployment distinction: Cloudburst Nukkit belongs to the Bedrock server ecosystem and uses Bedrock-oriented plugins and network transport; it cannot load Paper Java plugin JARs unchanged.
Stability and project maturity
Cloudburst Nukkit remains publicly available and under improvement, but modern Bedrock changes move quickly. Validate current protocol/gameplay support before starting a new long-lived server.
Current version note: The official repository describes Nukkit as Java Bedrock server software and provides a plugin API; CloudburstMC also develops the newer Cloudburst server project.
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 Nukkit
Do not choose by the word “Nukkit” alone—PowerNukkitX, Cloudburst Nukkit, and other forks have different APIs/features/version support.
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.
Staging acceptance test: Test a Bedrock client connection, verify the advertised protocol/version of the exact Nukkit build, and load a simple supported plugin before migrating a world.
Compatibility boundary: Java Edition world formats, redstone behavior and account identities must not be assumed interchangeable with Bedrock implementations.
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.