Minecraft has had more panel work done on it than any game we run except Arma Reforger. Here is what is different if you have not looked in a while.
Six tools became one Content Hub
The Minecraft tooling had grown into six separate sidebar items, which is what happens when features arrive one at a time and nobody stops to look at the whole thing. Plugin manager here, version changer there, world manager somewhere else.
They are now one tabbed Content Hub. Same tools, far less hunting for the one you want.
The plugin browser searches three sources, not one
It used to search CurseForge only. That quietly meant anything hosted elsewhere did not exist as far as the panel was concerned, and PlaceholderAPI is the obvious casualty: enormously widely used, a dependency of half the plugin ecosystem, and simply absent from search results.
There is now a provider dropdown for All, CurseForge, Modrinth and SpigotMC. All combines results across every source, so you find the plugin and install it from whichever one actually carries it.
Where an author has blocked automated downloads, you now get a clickable link to the official page rather than a greyed-out button with no explanation. Small thing, but a dead button with no reason given is one of the more frustrating ways to lose ten minutes.
Bedrock players can join your Java server
The Cross-play tab lets Bedrock Edition players on mobile, console and Windows 10 join a Java server. One click sets it up on the port your server already has, and it shows you the Bedrock connect address to hand out.
The care is in what it does not do. Your world and your players are untouched. It checks your server type and version before it changes anything. Disabling it removes it cleanly rather than leaving fragments behind. And if it cannot start, it rolls the change back automatically and tells you, instead of handing you a server that will not boot and no clue why.
Version changes that do not end in a crash loop
Switching Minecraft versions is one of the easiest ways to break a working server, so several guards went in together.
- Crash-looping downgrades are blocked before they install, not diagnosed afterwards.
- The panel can take a backup before a version change or a modpack install, and stops the server first so the backup is consistent.
- A compatible Java runtime is chosen for you. This removes an entire class of startup crash that presents as a mod problem and is not one, and which usually costs someone an evening.
- Modpacks that ship only a Windows start script used to leave you with a server that could not start at all. That gets converted now, with memory set to your server’s real allocation rather than whatever the pack assumed.
Settings you can actually find
Worth being precise about what changed here, because it would be easy to oversell. No settings were added and nothing gained more control. Every setting described below was already editable. What changed is that they are now ordered and typed the way you would expect.
The settings list used to arrive in alphabetical order. That is a reasonable default and a bad one in practice: it put difficulty between debug and the enable options, and buried max players, game mode and the message of the day among roughly sixty siblings. Alphabetical order is only useful if you already know the exact name of the thing you want.
They are now grouped by what you came to do. Commonly changed first, then world, players and gameplay, then performance, network and access, security and moderation, and resource pack.
There is a search box above the list, and it matches on the setting’s description as well as its name. Searching for a word like lag finds view distance, even though the two share no letters. That only works because someone wrote a description for every setting, which is the actual work behind the feature.
Anything the panel does not recognise still appears, under Other. A list of known names will always drift out of date as Minecraft adds settings, and a setting that vanishes because our list is stale would be worse than an ugly catch-all group.
Some switches were drawn as text boxes. A true or false setting would sometimes appear as a text field with the word false typed into it, sitting right next to identical settings that had proper toggles. That happened to any setting Minecraft added after our list of known switches was last updated. Those get a real switch now, and so will the ones Minecraft adds next.
A server that knows its own version
A newly created Minecraft server used to report its version as Unknown until you changed the version by hand. That is a strange thing to be told about a server we had just built for you.
To be clear about what this was: the server was running perfectly well. Nothing was broken. The panel simply had no record of a build it had not installed itself, so it said so rather than guessing.
It now reads the version and build straight from the server, and tells you that is where the answer came from. When the version is read from the server rather than installed from here, it says which build it found without claiming to be tracking it, and if it cannot tell which flavour of server you are running it shows the version alone rather than inventing a name for it.
Status colours across the Minecraft screens also follow whichever theme you have picked. A few of them were fixed values that stayed the same shade on every theme, including the OLED one.
Whitelist, message of the day, and the EULA
Whitelist management is in the panel: on or off, and add players by name without touching a file.
Your custom message of the day now shows in the in-game server list even while the server is idle, which is the moment it matters most, because that is when someone is deciding whether to click.
And a new server prompts you to accept the Minecraft EULA before first start, then sets it up when you accept. A fresh server no longer sits there refusing to start over a licence step nobody told you about.
Why it is built this way
None of this is a generic file editor with a Minecraft label on it. The config editor knows what Minecraft’s settings mean, the plugin browser knows the difference between the three places plugins live, and the version changer knows which Java each build wants.
That is slower to build per game, and it is the reason the tooling can catch a bad version change before it happens instead of showing you the wreckage afterwards.
Start a Minecraft server on the order page, or see the full Minecraft page for what the panel looks like. Game servers carry a 3-day refund window.