If you've been blocked from joining because your launcher or account shows a different Minecraft version than the server, this page is for you.
Server version, in one line ¶
The server runs Paper 26.2. That's the only thing the server software itself knows how to do. By default, only clients on 26.2 could connect.
Why a 26.3 (or newer) client still works ¶
We run the ViaVersion plugin (plus ViaBackwards on the same plugin family). ViaVersion sits between the client and the server and translates the network protocol on the fly. When a 26.3 client connects to a 26.2 server, ViaVersion catches the new-protocol packets the client sends, downgrades them to 26.2, and forwards the result to Paper. The same thing in reverse for outgoing packets.
The end result: a vanilla launcher on 26.2, 26.3, or any nearby release will reach the server, log in, see the same world, and play without you changing anything client-side.
What ViaVersion is and is not ¶
ViaVersion is a protocol translator, not a content pack. That matters in two ways:
-
What it does well. Movement, inventory, block interactions, mob behavior, chat, sound, particles, and the rest of the existing 26.2 surface area all work the same regardless of whether your client is 26.2, 26.3, or a point release between them. If you have ever joined a friend's modded server on a slightly different client version and it just worked, that is the same mechanism.
-
What it does not do. ViaVersion doesn't add new content. If Minecraft 26.3 introduces a new block, biome, or mob that 26.2 doesn't have, that content won't appear on the server — the server's data files are still 26.2, and the new item would have nowhere to save. The 26.3 client will silently drop the unknown packet and continue with what it has. If you need 26.3-specific content, the server itself has to upgrade first; the client won't help you there.
A practical example ¶
- You're on the default launcher, currently on 26.3.
- You connect to the server, see a "logging in…" splash, and end up in the spawn area.
- Everything in the world looks identical to what a 26.2 client would see, because the server is 26.2.
- A friend on a 26.2 client joins at the same time — both of you see the same blocks, same chat, same mobs.
That's the expected behavior. It is not a downgrade hidden in ViaVersion; both clients are playing on the same 26.2 server.
If you want to check your own client version ¶
In the default launcher: click the install dropdown at the bottom of the screen, look at the selected version. In the in-game menu: pause the game, click Options → Resource Packs, the version line is in the bottom-left. On third-party launchers (MultiMC, Prism, ATLauncher, CurseForge): each instance shows a "Minecraft" entry in its instance list; the version string is right next to it.
The exact version number doesn't matter as long as it's in the range ViaVersion is configured for. If you try to connect with a version outside that range, the server will tell you so on the connect screen with a "Outdated client / outdated server" message — at that point, adjust your launcher selection to one of the supported versions and try again.
When this changes ¶
If we move the server to a new Minecraft version, ViaVersion's config gets updated at the same time. Check the homepage banner and the News section for "Minecraft version bumped" entries when that happens.