Minecraft Java Snapshot 26.4-1: What It Means for Your Kingdom
What Changed
On 22 September 2026, a fresh Minecraft: Java Edition snapshot landed in the launcher, 26.4-snapshot-1. This is the first publicly visible build under the 26.4 version label, part of Mojang's year-based versioning system that replaced the old numbered scheme (think 1.21, 1.22…) with a year-and-cycle format.
Because this release arrived as a version manifest entry only, with no accompanying written changelog at the time of publication, the precise feature set and bug-fix list are not yet confirmed. Mojang typically follows up manifest drops like this with a full blog post within hours or a day, so keep an eye on the official Minecraft site for the detail breakdown.
What we do know: snapshot releases in the 26.x family continue to iterate on whatever major feature arc Mojang is developing for the next full release cycle. Expect experimental toggles, internal data-pack changes, and potential protocol shifts that ripple outward to the broader ecosystem.
Why It Matters
Snapshots are Mojang's way of letting the community road-test ideas before they're locked into a full release. That's great news for curious players who love being on the bleeding edge, but it also means the wider server and mod ecosystem needs time to catch up. Every snapshot can bring protocol changes, world-format tweaks, or API breaks that affect plugins, mods, and proxy software.
The jump to year-based versioning (26.x) is a bigger shift than a typical snapshot cycle. It changes how launchers, server jars, and compatibility layers identify and negotiate client versions, which has real consequences for multi-version servers like SNT kingdoms.
Java and Bedrock
This snapshot is Java Edition only. Bedrock Edition follows its own release track and was not updated alongside this drop. If your family mixes Java and Bedrock players (for example, someone on a console or mobile device joining the same world as a PC player), there is no change to Bedrock behaviour today.
Crossplay between Java snapshots and Bedrock is never officially supported, so Bedrock players should continue connecting exactly as they do now.
For Server Owners
If you run your own server infrastructure, here are the key points to watch:
- PaperMC, Velocity, and ViaVersion all need dedicated builds to support each new Mojang version, and year-based versions (26.x) require migration work that is still ongoing across those projects.
- Do not attempt to force a 26.x server jar into production yet; plugin and API compatibility is not guaranteed and world corruption is a real risk with snapshot builds.
- Monitor the PaperMC, ViaVersion, and Velocity GitHub repositories and Discord servers for announcements about 26.x support timelines.
- Snapshot worlds can differ in chunk format from release builds, always back up everything before experimenting.
For Parents
Nothing about this snapshot requires any action from you today. Your child's game on an existing server will continue to work exactly as before, snapshots only affect players who deliberately switch their launcher profile to the new snapshot version.
If your child is excited and wants to try the snapshot, that's completely fine as a solo, single-player experiment using a separate launcher profile. Just make sure they know not to open any existing worlds they care about in the snapshot, since doing so can make those worlds unreadable in older versions. A fresh test world is always the safest playground.
For Players
Snapshots are genuinely exciting, they're like a sneak peek behind the curtain at what Minecraft is becoming. Here's how to enjoy 26.4-snapshot-1 safely:
- Open the Minecraft Launcher, go to Installations, and enable "Snapshots" to see it in the list.
- Create a brand-new world just for testing, don't load your favourite survival world.
- Explore, break things, and report any weird bugs on the official Minecraft bug tracker (bugs.mojang.com), Mojang actually reads those!
- Remember: snapshot features can change or disappear before the final release, so don't get too attached to anything just yet.
Do SNT Kingdoms Need an Update?
No action is needed, and SNT kingdoms are not affected by this snapshot. Here's the full picture:
SNT Gaming kingdoms run Paper 1.21.11 backends behind a Velocity proxy, with one Fabric 1.21.4 backend powering the custom SharedLife experience. Crossplay is handled by Geyser + Floodgate, and ViaVersion / ViaBackwards / ViaRewind allow clients running anything from version 1.13 through 1.21.11 to connect seamlessly.
However, Minecraft 26.x clients are not yet supported on SNT kingdoms. PaperMC, Velocity, and the Via family have not completed migration to Mojang's year-based version scheme, which means there is no safe or stable path to accepting 26.x connections yet. This is an ecosystem-wide situation, not something unique to SNT.
If you or your child updates their launcher default profile to the snapshot, they may find they cannot connect to the kingdom until they switch back to a 1.13–1.21.11 profile. The fix is simple: in the launcher, select an installation that uses a supported version. All six worlds, Survival, SharedLife, RandomLoot, Chaos, Spleef, and Rivals, will be right there waiting.
We are watching the PaperMC and Via ecosystems closely and will announce 26.x support as soon as it is stable and thoroughly tested. Your kingdom, your progress, and your community are safe.