Minecraft Java Edition 26.3 Is Out, What Families & Server Owners Need to Know
What Changed
On 15 September 2026, Mojang officially released Minecraft: Java Edition 26.3, part of the newer year-based versioning system Mojang adopted to replace the classic 1.x numbering. The "26" refers to the release year, and ".3" marks it as the third major drop of 2026.
No detailed public changelog has accompanied the version manifest entry at the time of writing. That means Mojang has pushed the version live, but a full breakdown of fixes, tweaks, and additions is expected to follow in a separate changelog article. When that appears, we'll cover the specifics in a follow-up post.
Why It Matters
Even without a line-by-line changelog, a new release version always carries weight:
- Launcher prompt incoming. Players using the default Java launcher will be nudged to switch their active profile to 26.3. Kids especially tend to click "yes" without a second thought.
- Version lock. Once a client updates its active profile to 26.3, it can no longer connect to servers running older versions, unless those servers have compatibility layers in place.
- Ecosystem lag. Major tools like PaperMC, Velocity, and the ViaVersion plugin family need time to catch up to brand-new releases, particularly with the year-based versioning system still being relatively new territory for the modding community.
Java and Bedrock
This release is Java Edition only. Bedrock Edition (used on consoles, mobile, and Windows 10/11 through the Microsoft Store) follows its own separate release track and is not affected by this update. Bedrock players connecting to SNT Gaming kingdoms via Geyser crossplay continue as normal, no action needed on their end.
Java players, however, should pay close attention to which client version profile they are using in the launcher before trying to join their kingdom.
For Server Owners
If you run your own Minecraft infrastructure, hold tight before upgrading:
- Check whether PaperMC has published a stable 26.3 build before touching your server JAR.
- Confirm that Velocity and your proxy plugins support 26.3 before opening it to players.
- Verify that ViaVersion / ViaBackwards have added 26.3 to their protocol mappings, without this, older clients will be locked out.
- Test any custom plugins or mods (especially anything touching world generation or entity data) in a staging environment first, since year-based releases can carry larger internal changes than a traditional minor patch.
For Parents
Your child's Minecraft launcher may show a notification or automatically switch to version 26.3. This is normal and not a cause for alarm, but it can mean they're temporarily unable to connect to their usual server if that server hasn't updated yet.
The easy fix: in the Java launcher, click Installations, find the profile your child uses for their kingdom (it will have a specific version number), and make sure they launch from that profile rather than the "Latest Release" option. SNT Gaming families: drop us a message in your kingdom's support channel and we'll walk you through it in under two minutes.
For Players
Hey adventurers! A new Minecraft version just landed, which is exciting, but don't switch your launcher profile just yet if you want to keep playing on your kingdom. Here's the quick guide:
- Open the Minecraft Launcher and click Installations at the top.
- Look for the profile labelled with your kingdom's version (something like 1.21.11).
- Always launch from that profile, not "Latest Release."
- Once your kingdom is ready for 26.3, we'll let you know, and then you can switch!
Think of it like a theme park ride: the new ride might be open, but your group's wristbands are for the one you've already been on. Patience pays off!
Do SNT Kingdoms Need an Update?
Not yet, and that's intentional. SNT Gaming kingdoms run a carefully tested stack: Velocity proxy, Paper 1.21.11 backends, a Fabric 1.21.4 backend for the custom SharedLife experience, and Geyser + Floodgate for Bedrock crossplay. Players on Java clients from version 1.13 right up to 1.21.11 connect seamlessly today thanks to ViaVersion, ViaBackwards, and ViaRewind.
However, Mojang's year-based versioning (26.x) is not yet supported by PaperMC, Velocity, or the Via plugin family. Until those projects ship stable, tested builds for 26.3, upgrading our backend would break, not improve, your kingdom. We monitor every upstream release closely, and the moment the full ecosystem is ready and we've completed our own testing, kingdoms will be updated with zero fuss on your part. That's the whole point of fully managed hosting.
In the meantime, all six worlds, Survival, SharedLife, RandomLoot, Chaos, Spleef, and Rivals, are running smoothly. No disruption, no downtime, no action needed from you.