How to Keep Playing on 26.1 After 26.2 Released
Your favorite servers are still on Minecraft 26.1 after 26.2 shipped. Here's how to pin a 26.1 profile in the launcher and find communities still on that drop.
26.2 "Chaos Cubed" dropped on June 16, but the servers you actually play on are still running 26.1, and you'd rather stay with them than chase the new number. You don't have to do anything fancy — keep a 26.1 installation in the launcher, don't let your client jump to 26.2, and use the live list to see who's still on that drop. Trailing the newest version is normal and nothing to worry about; most servers sit a drop behind for a while on purpose, and staying matched to them is exactly the point. If joining a server in general is still new to you, how to join a Minecraft server is the foundational guide, and this one is about staying put once you're in.
Here's the fact the rest of this rests on: 26.1 is protocol 775 and 26.2 is protocol 776, and a client and server on different protocol numbers can't connect. Keep that in mind and the rest is straightforward.
Why staying on 26.1 is normal, not falling behind
The version number isn't a ranking — it's just what the client and server use to check they speak the same language. What matters isn't being on the highest number, it's that your client matches the servers you join, and right now those are on 26.1, protocol 775. Being on the same drop as your community is the whole goal.
Servers trail Mojang's release for a real reason. The third-party software most servers run on — Paper, Spigot, and the modloaders like Fabric and Forge — only ship their 26.2-compatible builds after the drop lands, and every plugin or mod updates on its own schedule. An owner who flips a live server to a brand-new drop before that ecosystem catches up risks breaking things for everyone, so most of them wait on purpose. There's no fixed date for when any given project is ready; it depends on the project, and the careful move is to check each one's current status rather than assume.
Datapacks, plugins, and mods written against the old version can break until they're updated and tested, so an owner who waits before flipping a live server is being careful, not slow. If your communities are on 26.1, the right move is to stay on 26.1 with them. Updating ahead just locks you out.
What "Outdated server!" means
You'll see two different version errors. "Outdated client!" means your game is older than the server wants. "Outdated server!" is the one you'd hit here — your game updated to 26.2 while the server stayed on 26.1, so now you're ahead of it.
Nothing on your end is actually broken when that happens. Your client just moved to 776 and the server is still on 775, so the numbers don't match and the server turns you away before you ever load in. That's all it is — a mismatch, not a fault.
That's the whole reason to pin 26.1 — keep your active client on it and you stay matched to 775 servers, so the message never comes up.
Pin a 26.1 installation in the Minecraft Launcher (Java)
The official launcher doesn't have a single "don't update" switch. Instead, each installation is locked to whatever version you pick in its dropdown, so a 26.1 installation simply stays 26.1 until you change it yourself. That's the mechanism — you're not disabling updates, you're just keeping a profile pinned to the version you want.
Here's the walkthrough. Open the launcher and go to the Installations tab, then click New installation. In the version dropdown, choose 26.1 — pick the specific release, not "Latest release," because "Latest release" is the setting that quietly pulls you onto 26.2. Give it an obvious name like "26.1" so you can tell it apart at a glance, and click Create.
Then make it the active one. Use the dropdown next to the Play button to select your 26.1 installation, so the green Play button launches 26.1 instead of the newest drop. That selection is what keeps you from being pulled forward.
You're not giving anything up by doing this. You can keep a 26.2 installation sitting right next to it and switch between them whenever a server you want is on the other drop — creating a 26.1 install doesn't delete or block 26.2. To confirm you're on the right one before you connect, the active version shows in that launcher dropdown and again in the bottom-left corner of the title screen.
If you already updated: getting back to 26.1
Plenty of people land here after the launcher already pulled them to 26.2. The fix is the same as above: create or select the 26.1 installation and launch it. Rolling the client back is safe on its own — switching installations doesn't touch your Multiplayer server list or your single-player worlds.
There's one risk that's worth flagging, and it only applies to your own worlds, not servers. Don't open a single-player world that was last saved in 26.2 using a 26.1 client. The game warns you about this with the version shown in red ("saved in a newer version") because loading a newer world in an older client can corrupt it. If you really need to open one, use Create Backup first. Joining a multiplayer server never loads your own save, so when you're connecting to other people's servers this doesn't come up at all.
If your problem is really just the error message and you want the swap mechanics walked through in more detail, the fix-after-updating walkthrough covers that side of it.
Bedrock players: a different situation
Bedrock works differently. It updates automatically through its store or platform and doesn't let you pin an older client the way the Java launcher does, so Bedrock players generally can't hold an older version by hand.
The practical move there is to match by choosing a server instead of by pinning a client: wait for your server to update, or play one that's already on your current Bedrock version. While you're sorting out addresses, the ports are worth knowing — Java's default is 25565 and Bedrock's is 19132.
Find the communities still on 26.1
You don't have to guess who's still on your drop. The 26.1 server list shows the communities running protocol 775 right now, so you match by picking from a list rather than connecting and hoping. The list is ordered by this month's votes, so the most active 26.1 servers sit near the top — a quick way to land on a populated server still on your drop instead of an empty one.
One thing to watch in the URL: the version is written with a dot, /servers/version/26.1, not a hyphen. The 26-1 form won't load. Same goes for 26.2 later on, when you want to see who's moved over.
And your server will move eventually — the gap is usually temporary, with large active servers tending to update within days to a few weeks. When yours jumps to 26.2, you don't have to do anything dramatic. Switch your active installation to the 26.2 one, and you follow it across.
FAQ
What if my favorite server is a modpack locked to a specific version?
Modpacks complicate the timeline, because a pack is a fixed bundle of mods built against one Minecraft version, and the whole pack only moves when its author rebuilds it. That often lags well behind the loose plugin servers, so a modded community can sit on 26.1 — or an even older drop — for months after release, and that's expected rather than neglect. Match the pack's exact version in your launcher installation, not just the nearest Minecraft release, and join through the same launcher profile the pack set up.
Does running a snapshot or pre-release change any of this?
Yes, and it's worth knowing if you ever opted into one. Snapshots and pre-releases carry their own protocol numbers that don't line up with either 26.1 or 26.2, so a snapshot client won't connect to a normal 775 or 776 server at all. If your launcher is set to a snapshot installation, that's its own kind of version gap, separate from the 26.1-versus-26.2 split. Switch your active installation back to a release version of 26.1 before trying to join the servers you play on.
How can I tell whether a server is on 26.1 or 26.2 before I join?
A good listing states the version it runs, and on this site every listing shows it — you can browse everyone currently on 26.1 or 26.2 directly. Remember the path uses a dot, not a hyphen (26.1, not 26-1). You can also read the Multiplayer screen itself: a server you can't join on version grounds shows a red X or exclamation on its ping bars, and hovering gives you the "Outdated" message, which tells you it's a version gap rather than a server that's simply offline.
Can I stay on 26.1 and still join a server that already moved to 26.2?
Only if that server's owner has enabled server-side version-bridging — the ViaVersion family of tools — which lets mismatched versions connect. That's the owner's setup, and you can't add it to someone else's server as a player. If a 26.2 server doesn't have bridging enabled, your 26.1 client will be turned away with "Outdated client!". To join it, switch your active launcher installation to your 26.2 one; keeping both installations side by side means that swap is a two-click change, not a reinstall.
