I selected version X but the server runs a different build (e.g. 1.19 → 1.19.4) — why?

Picked "1.19" but ended up on 1.19.4? That's expected behaviour from the Versions installer, and it's usually exactly what you want. Here's why — and how to pin an exact build if you need one.

Why the build differs

The Versions installer usually pulls the latest build within the version line you chose. So a "1.19" pick may land on 1.19.4 (the newest 1.19.x). That's normal, and generally what you want — the latest build includes bug fixes.

Getting an exact build

1. Open the Versions tab and choose your software.
2. In the build dropdown, select the specific build you need rather than the default.
3. Alternatively, upload that exact JAR manually via Files and set it in the Startup tab.

Tip: Unless a modpack requires an exact build, letting the installer take the newest build in the line is the safer choice — you get the bug fixes.

Frequently asked questions

Is it a bug that I got 1.19.4 instead of 1.19? No — the installer pulls the latest build in the line by default, which is generally what you want.

How do I force a specific build? Choose it in the build dropdown, or upload that JAR manually and set it in the Startup tab.