I would like to share my concerns about the plan to move away from the traditional 1.x.x version numbering system.
For many long-time players, the 1.x.x format is not just a technical label, but part of Minecraft’s identity.
It is familiar, easy to understand, and has been used consistently for more than a decade.
Switching suddenly from versions like 1.21 to something like 26.1 could be confusing.
Some players may feel that the version number has “jumped” dramatically, or assume they have missed many major updates.
This may create unnecessary misunderstanding, especially for casual players and younger audiences.
If the goal is to clearly distinguish Game Drops or frequent updates, I believe this can be achieved without changing the core version format.
For example, additional identifiers or suffixes (such as extra sub-version markers) could be added while keeping the 1.x.x structure intact.
I respectfully suggest considering ways to preserve the 1.x.x versioning scheme, while still clearly communicating Game Drops and update timing.
Thank you for continuing to listen to community feedback and for your ongoing work on Minecraft. for example, Instead of switching to a completely new versioning format (like 26.1), why not preserve the familiar '1.x.x' structure and introduce meaningful suffixes like 1.x.x-gd1, 1.x.x-fe1, or 1.x.x-hf to indicate update types? This would keep consistency for players and developers alike, while allowing more flexibility for releases like Game Drops.
Please sign in to leave a comment.
0 Comments