Minecraft Java Snapshot 26.3-rc-2: What You Need to Know
What Changed
On 11 September 2026, Mojang quietly pushed Minecraft: Java Edition 26.3-rc-2 to the official version manifest. The "rc" label stands for Release Candidate, this is the second candidate build in the 26.3 cycle, meaning the development team believes the code is feature-complete and is now focused purely on squashing any last bugs before a full public release lands.
Because this build arrived as a version manifest entry rather than an accompanied changelog article, a detailed list of every fix and tweak hasn't been published alongside it yet. Release candidates at this stage typically contain targeted stability patches, crash fixes, and minor polish rather than splashy new features.
Why It Matters
Release candidates are the final pit stop before a stable version ships. Historically, Mojang publishes just one or two RCs before flipping the switch on a full release, so 26.3-rc-2 signals that a finished Minecraft Java 26.3 is very close. That matters for the whole community:
- Content creators will start publishing 26.3 tutorials and videos almost immediately after stable drops.
- Players using vanilla launchers will be prompted to update, which means they'll be on a version their favourite servers may not yet support.
- Server owners need to watch the ecosystem (PaperMC, Velocity, plugins) closely so they know exactly when it's safe to migrate.
Java and Bedrock
This snapshot is Java Edition only. Bedrock Edition follows its own release schedule and versioning system, so Bedrock players and servers are unaffected by this specific build. Cross-play between Java and Bedrock, powered by tools like Geyser, remains tied to whichever stable Java version the server is running, not the latest snapshot.
If you're a Bedrock player connecting to a Java server, nothing changes on your end today. Keep an eye out for a matching Bedrock update if Mojang synchronises features across both editions with the final 26.3 release.
For Server Owners
The Minecraft ecosystem runs on more than just the game client. PaperMC, Velocity, Geyser, ViaVersion, ViaBackwards, and every plugin in between all need time to test and adapt to a new version string, especially one using Mojang's newer year-based versioning format (26.x), which is a structural change from the old 1.x scheme.
- Do not rush a migration. Even after the stable 26.3 release, wait for PaperMC and Velocity to publish production-ready builds before touching a live server.
- Check the PaperMC, Velocity, and ViaVersion GitHub pages and Discord announcements for migration timelines.
- Back up every world before any version upgrade, release candidates can still carry edge-case bugs that affect chunk data.
- Remind your players that connecting with a 26.x client profile to a 1.21.x server will not work until the Via compatibility layer is updated.
For Parents
If your child is excited about the new Minecraft update and wants to jump on their favourite server straight away, a little heads-up goes a long way. Managed servers, like the ones families use, take time to update safely so that nothing breaks and no progress is lost. Encouraging patience now means no lost worlds or frustrated evenings later.
The short version: it is completely fine for your child to update their personal launcher to try the snapshot in single-player, but they should keep their regular game profile on the current stable version to keep playing on their server without any hiccups.
For Players
A release candidate is basically Minecraft saying "we think it's ready, help us find the last few bugs!" If you love testing new things, you can switch to the 26.3-rc-2 snapshot in the Java launcher's installation settings and explore it in a fresh single-player world. Just remember:
- Never load your main saved worlds in a snapshot, it can corrupt them.
- Your server might not support 26.x clients yet, so keep a separate launcher profile on your usual version.
- If something feels broken or weird in the snapshot, that feedback is actually valuable, Mojang reads bug reports on their official tracker!
Do SNT Kingdoms Need an Update?
No, and they won't update until the full ecosystem is ready. SNT Gaming kingdoms currently run Paper 1.21.11 backends with a Fabric 1.21.4 backend for the SharedLife world, all sitting behind a Velocity proxy. Players can connect using any client from version 1.13 through 1.21.11 thanks to ViaVersion, ViaBackwards, and ViaRewind.
However, Minecraft 26.x clients are not yet supported on SNT kingdoms. PaperMC, Velocity, and the Via family of plugins have not yet migrated to Mojang's year-based version format, which means there is no safe compatibility layer in place. Connecting with a 26.3 client profile will result in a failed connection, this is expected and temporary.
The moment PaperMC, Velocity, Geyser, and the Via plugins all publish stable, production-ready builds for 26.3, our team will begin thorough internal testing across all six game worlds, Survival, SharedLife, RandomLoot, Chaos, Spleef, and Rivals, before rolling out any update to live kingdoms. Your progress, your builds, and your experience are always the priority. We'll announce the update window well in advance.