Minecraft Bedrock is killing the things that helped it grow.
PocketMine-MP has ended support, NetherGames has shut down, and Bedrock’s technical information keeps moving behind partner gates. This does not look like a set of isolated accidents. It looks like an ecosystem slowly choking the part that helped it grow.
“Information wants to be free.” - Stewart Brand
I like that sentence because it has the kind of stubbornness the old internet used to have. Information does not want to be free because every piece of work should be treated as worthless. It wants to be free because when information is locked away for too long, the people outside the gate start running out of air. People who want to learn cannot learn. People who want to fix cannot fix. People who want to build something new end up standing in front of a closed door, waiting for someone with access to feel generous.
With Minecraft Bedrock, that feeling has become harder to ignore. The community around servers, plugins, modding, reverse engineering, and unofficial software helped make Bedrock feel alive. It kept players around. It let small server owners build their own communities. It gave someone like me a path from downloading Minecraft PE, finding IPs, hosting a server on a phone, editing PHP plugins, and eventually learning to code.
Then Minecraft became stable, huge, commercial, and mature enough to have Marketplace, Realms, partners, Featured Servers, and a polished official funnel. The painful part is that the software and servers that helped the Bedrock community grow are now being pushed into a technical environment where surviving is harder every year.
I do not have Mojang or Microsoft’s internal documents. I cannot claim there was a meeting where someone ordered PocketMine-MP or NetherGames to be killed. But pretending that only official press releases count as reality is also dishonest. Sometimes reality is in the direction created by many decisions stacked together. The direction here is clear enough. Independent Bedrock servers increasingly depend on non-public information, partner access, a few maintainers, unstable funding, and the goodwill of the very actors Mojang has already selected.
That is why this is a criticism, and also a small obituary. Farewell PocketMine-MP. Farewell NetherGames. Farewell to a part of Minecraft Bedrock that was messy, open, buggy, human, and far more real than a curated server tab.
A death that did not happen overnight
On 09.07.2026, the main PocketMine-MP repository on GitHub was archived and made read-only. Only a few days earlier, version 5.44.3 had been released on 06.07.2026. From the outside, this can look sudden. But if you read the signs from the last few years, PMMP did not collapse in one night. It reached the end after being stretched for years.
The PMMP homepage is now a farewell page with the line 2012 - 2026. It says a key developer has left Minecraft behind, and that no one on the PMMP team is left willing to update the project for new Minecraft versions. The team gathered documentation on the update process so forks can try to continue, but the PMMP team itself will not provide further updates.
If you stop there, the easy conclusion is that PMMP died because it ran out of people. That is true, but incomplete. Running out of people is the final symptom. The harder question is why a project with more than a decade of history, thousands of dependent servers, a plugin ecosystem, and a large public repository reached a point where losing a few people meant losing official updates entirely.
To answer that, it helps to read dktapps’ “I'm retiring” issue from 21.03.2024. Dylan said he would step down from PocketMine-MP and move on from Minecraft. He had lost his passion for the game years earlier and mostly launched it to test PocketMine changes. More importantly, he described the future of the project. PMMP had become a foundation that thousands of Minecraft servers depended on, but maintaining it required serious commitment, responsibility, and expertise. It was also a thankless task that did not pay the bills unless a business using it happened to sponsor the work.
That sentence hurts because it is true. PMMP was not a toy project. It was infrastructure. But that infrastructure depended on a handful of people with time, reverse engineering skill, community stamina, and sometimes funding from a partner such as Lifeboat. A healthy ecosystem should not place its backbone on so few people and then act surprised when they get tired.
Dylan also predicted a future that now feels very close. Large servers would maintain private forks. Small servers would die off. Not because small servers are lazy, but because understanding new Bedrock versions, updating protocol, updating data, and fixing plugins has become too expensive for most small communities.
PocketMine-MP was a massive doorway
For me, PMMP was never just PHP server software. It was a doorway. I already wrote more technical background in What is PocketMine-MP?, and the more personal memory in Minecraft since 2015, before I knew what an IP was. If I had to compress it into one sentence, PMMP gave many people a way to make Minecraft Bedrock their own.
Not everyone had money for serious hosting. Not everyone knew Go, C++, Java, or network protocols. But PHP, plugins, config files, Poggit, DevTools, old forums, and YouTube tutorials were enough for a student to open a server, edit spawn, adjust economy, add ranks, translate messages, and slowly realize that every feature in the game had real code behind it.
PMMP was never perfect. It was not vanilla. It lacked Mojang-style world generation, complete redstone, mob AI, and a long list of gameplay behaviour. Plugins could turn a server into a soup of errors if an owner downloaded everything without thinking. But precisely because it was imperfect, it taught people to look inside software. There was no magic box. A server was events, packets, ticks, permissions, schedulers, memory, logs, crashes, and many nights where fixing one bug revealed two more waiting politely.
An ecosystem like that does not only create servers. It creates learners. It creates developers. It creates local communities. It creates plugin archives, Facebook groups, Discord servers, GitHub organizations, tiny tools, and a habit of sharing resources. If Minecraft Bedrock has a large community today, those unofficial things cannot be erased from the story. They were the dirt under the foundation. When the house gets tall, people love to forget the dirt. The foundation did not grow from a clean logo.
NetherGames is a rare public accusation
NetherGames shut down forever on 28.06.2026. Its announcement was not a lazy status update about being tired. It was a history of almost ten years. The server started on 18.01.2016, from a small setup running public plugins downloaded from PocketMine forums. It went through the Better Together update in 2017, when mandatory Xbox login damaged player counts for many servers, then merged with Dries’ GameCraftPE. Dries’ technical expertise helped NetherGames move away from public plugins and build its own in-house systems.
During the pandemic, NetherGames reached 3,314 concurrent players. This was not a tiny server failing because it never tried. It was a large server with operations, staff, products, a community, web infrastructure, custom games, and nearly a decade of experience. And still, it shut down.
The most important part of the NetherGames closure announcement is where it says Microsoft and Mojang made it increasingly difficult for non-Featured servers to exist. NetherGames says Mojang deliberately cut non-Featured servers off from technical information that had once been freely provided, and that repeated assurances about restoring that access never turned into reality. Keeping up with Minecraft updates became, in their words, a resource-intensive battle they were never going to win. They also had a meeting with Microsoft in 2024 about becoming a Featured Server, then were ghosted by their contact.
That is NetherGames’ account, not an internal Mojang memo. But it matters because it lines up disturbingly well with what PMMP’s own technical documentation says. One side is a commercial server saying it was cut off from information and could not win the update race. The other side is open source server software saying that updating new Bedrock versions requires BDS data, and some of that data now requires access through server or Marketplace partners.
These two stories do not mean NetherGames closed because PMMP ended support. NetherGames had long moved beyond public PocketMine plugins, and Dries was a separate technical pillar for that network. That actually makes NetherGames more important as evidence. Even after building in-house systems, even after becoming large and technically capable, an independent Bedrock server still hit the same wall. Bedrock is a platform where crucial information is not distributed fairly.
Debug symbols sound dry, but they are oxygen
To understand why this matters, we need to talk about debug symbols. It sounds dry. For independent Bedrock server software, it is closer to oxygen.
Bedrock Dedicated Server, or BDS, is Mojang’s official server. A normal BDS release is a compiled binary. It runs, but it is difficult to understand from the outside. Debug symbols map parts of the binary back to useful names such as functions, classes, structures, and identifiers. With symbols, reverse engineers can tell what they are looking at. Without symbols, it is like walking through a city after someone removed every street sign.
In 2019, dktapps wrote 1.13, debug symbols and the Titanic on the PMMP forum. He explained that debug symbols were an essential tool server and mod developers had relied on for years. When symbols were removed, reverse engineering protocol became much harder. Automatic tools could become useless, and manual binary analysis became far more expensive. He warned that supporting a new Minecraft version could move from a few days to weeks or months.
At that time, dktapps still did not want to say Mojang was trying to kill third-party servers. He leaned toward the explanation that Mojang was trying to make life harder for hackers, while third-party servers became collateral damage. I respect that posture. It avoids lazy accusations. But in 2026, the picture is different. When an unfavorable decision lasts for years, when communities object, when large servers close, and when PMMP documentation itself says crucial data now depends on partner access, it is much harder to call the whole thing accidental.
PMMP’s documentation page Implementing new Minecraft version support in PocketMine-MP describes an update process that needs the matching Linux BDS, BedrockProtocol, BedrockData, block and item upgrade schemas, data dump tools, packet traces between BDS and a vanilla client, and BDS mods that extract the needed information. The crucial note is about Bedrock 1.21.40. Mojang no longer publicly provides BDS builds with debugging symbols. To generate the needed data, developers need access to builds provided by a server or Marketplace partner. Public protocol docs can replace only part of the missing information. PMMP’s conclusion is that third-party servers depend on the goodwill of Minecraft partners.
That phrase sounds polite, but it is heavy. It means independent server software no longer stands on public documentation. It stands on relationships. If a generous partner helps today, the ecosystem survives. If tomorrow that partner changes priorities, a maintainer leaves, an NDA tightens, or data stops being shared, the community is back in the dark.
A partner is not just a nice badge
Minecraft now has a very clear partner system. The Minecraft Partner Program page says official creators can sell creations on Marketplace, need a high-quality portfolio, must operate like a business, and have submissions reviewed before reaching players. The Minecraft servers page emphasizes the Official Minecraft Server List, Partner Servers inside Bedrock, Xbox profiles, community standards, and safety.
I do not deny the need for safety. Minecraft has many young players. Public servers involve chat, purchases, user-generated content, and plenty of real risk. Mojang has legitimate reasons to control part of the experience. But there is a wide grey area between protecting players and making non-partner servers struggle to breathe. The problem is that technical decisions are pushing too much important information into that grey area.
Partners have a distribution advantage. They can appear directly inside the game, or have an official route to Marketplace. Partners have a trust advantage because they carry the official label. And according to PMMP’s documentation, some server or Marketplace partners have access to BDS builds with symbols that the public does not have. Those three things together are not just marketing. They are a power structure.
If a server is shown in the official tab, gets better access to players, and may receive better technical information, outside servers are no longer competing on the same field. They must market themselves harder, update with less help, reverse engineer more, carry more risk, and then when they shut down, people can say the market chose the winner. But that is not a natural market. It is a designed one.
What bothers me is that unofficial servers and software helped Bedrock build community life long before the official ecosystem looked this polished. Before Marketplace became smooth, before Featured Servers became a powerful distribution gate, people joined servers by IP, downloaded plugins, watched tutorials, joined forums, opened small servers for friends, became staff, built lobbies, configured ranks, and created thousands of reasons to stay with the game. When the ecosystem became large enough to monetize cleanly, the part that helped it grow was pushed toward the edge.
Dragonfly survives through a narrower path
In a conversation I read, Seb said Dragonfly used to depend on PocketMine’s existence for data generation. When asked whether Dragonfly still depended on PMMP after the support-ending announcement, Seb said updates were even easier using debug servers with symbols, though those were private anyway. He also said debug servers with symbols were the only way it had been kept alive so far. Fortunately, Dragonfly now mainly needs BDS data for block upgrade schemas, and those have barely needed updates recently.
This should be read carefully. It does not publicly prove that Galaxite provides private BDS files to Dragonfly. It also does not prove that every Featured Server gets the same technical resources. But it does show a practical reality. A project close to a partner ecosystem, with someone who can access private builds, or a project that only needs a smaller slice of BDS data, has a better chance of surviving than an independent project that must update many layers of protocol and data.
Dragonfly is Bedrock server software written in Go, built around async design and often used as a library. The df-mc organization also has datagen, a tool for generating useful data from BDS, and mapping, a BDS mod heavily based around pmmp/mapping. This reinforces the larger fact. Whether the server is written in Go or PHP, independent Bedrock software still needs data from the BDS world.
Dragonfly may be able to keep going because it needs less data and appears to be in a better position. PMMP had to carry a large plugin API, a legacy ecosystem, a long history, many data types, and a huge pile of expectations. In other words, this is not only about which programming language is better. It is about who has data, who has people, who has access, who has funding, and who still has enough energy to continue.
Geyser makes the board look even more uneven
Another important piece is Geyser. Geyser does not try to reimplement a Bedrock server from scratch. It translates protocol so Bedrock players can join Java servers. That model has a huge advantage because gameplay and server logic sit on Minecraft Java, where the server software and modding ecosystem is much older and stronger.
I am not saying Geyser is bad. It is an impressive project. But its success exposes a sad contradiction. If you want to build a strong server experience for Bedrock players, a practical route may be to run Java server software and let Bedrock players in through a translation layer. That says a lot about the clean-room Bedrock server ecosystem. Going around Bedrock through Java can be more realistic than building directly on Bedrock.
That is unfortunate. Bedrock is the edition many people play on phones, consoles, and Windows. It should have strong independent server software, clear docs, stable APIs, and public data good enough for the community to build correctly. Instead, software like PMMP must reverse engineer. Servers like NetherGames build internal systems and still say the update race became unwinnable. Other projects need partner proximity or reduced dependency scope.
PMMP had problems of its own
If I blamed everything on Mojang, this article would be easier to write, but less fair. PMMP had its own internal problems too.
PHP is not the most natural choice for high-performance game server software. PMMP did many clever things to live with PHP, but as time went on, Dylan also agreed with the idea that much effort was spent working around PHP’s limits instead of developing PocketMine itself. Major API changes broke old plugins. Being non-vanilla confused many server owners. Old community plugins were often low quality. Some owners used leaked, copied, or badly shared plugins, then blamed PMMP when the server broke.
PMMP also stopped being a small playground where every idea could be merged. A project used by many servers has to become more conservative. That makes it harder for newcomers to contribute. Reviews slow down. Maintainers are limited. The door into core narrows. All of these are real problems.
But those problems do not erase the platform pressure from Bedrock. A project with technical debt can still survive when the platform is stable, documentation is good, and the needed data is public. A tired maintainer base can still transfer knowledge when the update process does not require an extremely specialized reverse engineering layer. PMMP had weak points, but Bedrock made every weak point heavier.
In other words, PMMP had pre-existing conditions. Mojang did not create all of them. But the Bedrock technical environment made them much harder to survive.
Why I call this a way of killing
Killing software does not always mean sending a legal order to shut it down. There are slower methods. Do not publish enough documentation. Remove debug symbols from public builds. Let protocol change constantly. Provide necessary data only to some partners. Avoid a stable official plugin API that could replace the need for reverse engineering. Build distribution channels where partner servers reach players far more easily. Leave non-partner servers harder to update, harder to compete, and harder to staff.
Each individual decision can be explained by a legitimate reason. Anti-cheat. Child safety. Security. Avoiding leaks. Reducing support burden. Standardizing the experience. But together, the result is an ecosystem where independent software dies slowly, and the part that survives best is usually the part closest to partners or running through another platform.
This is the strongest thing I want to criticize. If Mojang truly cannot publish BDS builds with symbols for security reasons, they can still publish the generated data. They can publish official schemas. They can provide detailed protocol changelogs. They can create a fair developer channel for independent server software. They can separate interoperability information from genuinely sensitive internals. They can say, no, we will not publish a debug binary, but here is the data so the community does not need to work blind.
The fact that these alternatives are not provided fully, while partners still appear to have access paths the public does not, makes the story difficult to read as pure security. It looks like a platform keeping power inside the platform. When a platform keeps power too tightly, outside creators become decorative. Useful during growth, disposable during control.
Information wants to be free in Minecraft Bedrock
Stewart Brand’s line should not be read naively. Information is not free just because it wants to be. Companies hold it. Laws hold it. NDAs hold it. Commercial incentives hold it. Security fears hold it. But the line reminds us that information creates value when it flows. In software, this is especially obvious. Open documentation creates developers. Clear protocol creates interoperability. Public tooling creates forks. Public schemas create servers. Open knowledge bases create the next generation.
PocketMine-MP is a living example of that. It survived through open code, open plugins, forums, Poggit, docs, examples, and the endless loop of one person helping another fix a broken server. NetherGames also began with public PocketMine forum plugins before growing into a large in-house server network. Dragonfly has open repositories, datagen tools, mapping work, and a community around it. This ecosystem did not come from secrecy. It came from people being able to look, learn, modify, break, and rebuild.
When information is locked away, the best people may still find a path. But beginners lose the door. Small servers lose the ability to rescue themselves. Plugin developers lose motivation. Maintainers spend time guessing things that should have been documented. Eventually, fewer people learn to code through Minecraft. That is not a small loss. To me, that is the loss of an educational path.
In Vietnam, this was never only software
Reading the Vietnamese Facebook posts and comment threads made this ending feel less abstract. I would not use those memories as a strict timeline, because many of them are being reconstructed after years and some details may be fuzzy. But emotionally, they are consistent. PMMP was where Vietnamese students opened ports, ran servers on phones or cheap VPS plans, translated plugins, edited configs, wrote their first plugins, and eventually found their way into Information Technology.
The comments also add a local layer that a global technical article can easily miss. The decline in Vietnam did not come from one cut. It passed through the 1.2 update making old devices and Xbox Live harder for young players, through weaker YouTube discovery, seasonal servers, DDoS, leaked plugins, repeated Skyblock formulas, and then the PM3 to PM4 transition that left many plugins and small owners behind. People remembered Genisys Pro, ElyWing, Steadfast2, Allay, PM3, PM4, servers pushed to run on weak hardware, anti-Toolbox work, Pickaxe Level, FarmingIsland, dupes, crashes, coin bugs, data loss, and maps rebuilt after mistakes. It sounds messy because it was. It also sounds alive because that mess was how people learned.
The mentions of Miheisu, Bravocraft, and a few private projects show that the flame is not completely out. It is just small. Miheisu is described as a server choosing stability and simplicity, passing through earlier names such as MineSAO and PuckVN before returning in 2024. Some people still fix old plugins, keep private projects, share resource packs, or hope a new server will launch. But the feeling is no longer a busy public square. It is a small circle around the last warm coals, telling old stories while knowing the old atmosphere will not return unchanged.
So I am not treating those posts as proof of what Mojang did. They are not technical documentation or official sources. What they do provide is texture. PMMP’s ending is not only a repository being archived. It is a sigh from people who learned code by repairing servers, grew up through awkward plugins, made mistakes, broke things, apologized, rebuilt, and eventually realized that part of their youth had become an archive.
Thank you, PocketMine-MP
I want to give PMMP its own farewell here, because criticizing Mojang should not turn PMMP into an abstract symbol and erase the real people behind it.
Thank you to Shoghi for creating PocketMine when Minecraft Pocket Edition was still a very different world. Thank you to Dylan for carrying PMMP for so long and leaving behind code, documentation, technical decisions, debates, and warnings that were not always pleasant but were often necessary. Thank you to the maintainers, reviewers, moderators, donors, plugin developers, bug fixers, documentation writers, and people who answered the same beginner questions again and again. Thank you to Lifeboat for funding development in the later years while allowing the work to remain public.
Thank you, PMMP, for showing many people that servers are not magic. Thank you for making PHP a doorway into Minecraft Bedrock. Thank you for Poggit. Thank you for DevTools. Thank you for plugin.yml, onEnable, event listeners, permissions, config files, tasks, forms, virions, red console text, and all the errors that made people angry enough to learn something.
Thank you for helping small servers exist. Some lived for a few months. Some opened during a school break and then disappeared. Some were full of bugs. Some sold ranks a little too confidently. Some had only a few friends online. But for the person running them, each one was a real world. A world with a spawn, rules, players, hope, and the feeling of making something that lived outside one machine.
PMMP ending official support does not mean every fork dies immediately. People will try to continue. Large servers will keep private forks. Archives will remain. Plugins will still run on older versions. But the era of PMMP as a shared upstream for the independent Bedrock community has closed. That deserves grief.
Goodbye, NetherGames
NetherGames also deserves to be seen as more than one server shutting down. It is proof that a server starting from public PocketMine plugins could grow, build its own systems, reach thousands of concurrent players, and become part of many people’s memories.
The closure announcement has a very human shape. Callum started the server at age 11, using hosting paid for by his parents as a birthday gift. The lobby got griefed because OP was given to the wrong person. Backups were not considered at the right moment. Then the server grew, changed names, merged, matured, went through the pandemic, built staff teams, created a web portal, developed games, and gathered players. That is community history, not a KPI chart.
The painful part is that a server like that still concluded it was in a battle it could not win. Not because it lacked love for Minecraft. Not because it failed to try. But because the technical and distribution field leaned toward selected servers. When a server says it tried to become Featured and was then ghosted, the story is no longer simply that whoever does better survives. It becomes that whoever gets the door opened has a better chance of living.
NetherGames said it would open source as many games as possible so people could host matches and keep playing what they loved. If that happens, it is a beautiful way to leave. Do not close everything in a box and bury it. Leave code, leave memory, leave a path for someone else. That is also the closest ending to “Information wants to be free”.
What remains should stay open
After deaths like this, the easiest reaction is exhaustion. The more useful reaction is preservation.
Preserve old plugins. Preserve docs. Preserve forums through archive services. Preserve tutorials. Preserve NetherGames code if they release it. Preserve the PMMP update process. Preserve schemas. Preserve datagen tools. Preserve explanations in Vietnamese and English so the next person does not have to start from dead links and scattered messages. Not because everything will come back the way it was, but because technical memory is infrastructure too.
If PMMP forks want to continue, they will need more realism than nostalgia. They need smaller scopes. They need documented update processes. They need to separate public data from anything that cannot be public. They need to avoid depending on one person. They need to say clearly which versions are supported, which things are not, and they should not sell a vanilla illusion they cannot maintain. They need a calm relationship with the truth that Bedrock is no longer an easy platform to work around.
But the larger responsibility still belongs to Mojang and Microsoft. They can do better. They can avoid publishing sensitive binaries while still publishing the data communities need. They can support interoperability while still protecting players. They can create a developer program for independent server software that does not require being selected as a commercial partner. They can admit that the outside ecosystem was not a parasite. It was part of why Minecraft lasted.
No one needs to sign a death certificate
An ecosystem can kill its outside edge without ever ordering a shutdown. Close a little more information each year. Tilt distribution a little more. Increase update costs a little more. Move more access behind partners. Let maintainers burn out. Let small servers fall. Then say it happened naturally.
But people who lived on the edge can see that it was not completely natural. PMMP did not die only because of PHP. NetherGames did not close only because a server stopped being trendy. They are both part of a larger current where Bedrock is increasingly governed as a closed commercial platform, while the things that once helped it expand are treated as external.
Minecraft Bedrock will continue. Marketplace will keep selling. Partner servers will stay busy. Realms will still have users. Official things will not vanish because PMMP ended support or NetherGames shut down. But a rougher, more creative, more community-shaped part of Bedrock has lost a lot.
And to me, the most frustrating part is that this loss could have been avoided. Mojang did not need to open source the whole game. They did not need to publish debug binaries if there are real risks. They only needed to treat independent server communities as something worth supporting with decent documentation, data, and APIs, instead of leaving them alive through unofficial relationships and partner goodwill.
Information wants to be free. Minecraft Bedrock grew because so much information was passed around, opened, reversed, rewritten, uploaded to forums, GitHub, YouTube, Poggit, and tiny servers running on weak hardware. When that information gets locked down, software is not the only thing that dies. A path into programming becomes narrower.
So farewell, PocketMine-MP. Farewell, NetherGames. Thank you for making Minecraft Bedrock bigger than its official menu.
Sources worth reading
PocketMine-MP’s farewell page announces that the project will no longer update for new Minecraft versions and thanks Lifeboat and the community.
The PocketMine-MP repository shows the archive state on 09.07.2026, the end of support announcement, and release 5.44.3.
dktapps’ “I'm retiring” issue explains why PMMP’s future was already uncertain in 2024.
PMMP’s protocol update documentation describes the BDS data process and the problem of debugging symbols from 1.21.40 onward.
The 2019 PMMP forum post about debug symbols shows that this warning has been around for years.
NetherGames’ closure announcement tells the server’s history and its accusation that non-Featured servers were cut off from technical information.
Minecraft servers and the Minecraft Partner Program show the official Bedrock server, partner, and Marketplace systems.
Dragonfly, df-mc datagen, and df-mc mapping are related pieces showing how independent Bedrock software still needs data from BDS.
You made it to the end If you need the short version
The article argues that Minecraft Bedrock is making independent servers and unofficial software harder to sustain by closing off technical information, moving important access toward partners, and raising the cost of keeping up with updates.
PocketMine-MP ended official support and NetherGames shut down, but both point toward a wider problem. Independent Bedrock servers must keep up with protocol changes, BDS data, and a distribution field increasingly tilted toward selected partners.
No. The article does not claim there was an internal order. It draws an inference from public events, technical documentation, and community experience to describe a pressure pattern that slowly weakens independent software and servers.
The Vietnamese community section shows that PMMP was not only a software repository. It was an entry point into Information Technology for students, small server owners, plugin translators, and self-taught developers.
- NhanAZ - 10.07.2026