Parity means making features behave consistently across different Minecraft editions, most commonly between Minecraft: Java Edition and Minecraft: Bedrock Edition. Use this category to discuss released features that exist in both versions of the game but work differently. Please note that bugs are not parity issues and should be reported separately.

← Parity
9
Follow

Minecraft Update Number

With the announcement on minecraft.net of the new update version numbering, there is still a major flaw that hasn't been solved.

The issue with the previous update numbering (1.XX.XX) was that the number for drops were different between java and bedrock. With the new change this is still an issue. So, I would like to show you my new format:

Bedrock:

26.X.XX

Java:

26.X.X

The first X for both JE and BE are drops. The second X for BE is the minor updates. And the last X for both JE and BE are for their hotfixes. So for 2025 drop cycles:

Bedrock:                                                                    Java:

26.0.10 - Minor update (old 1.21.60)                         -

26.1.00 - Spring to Life                                              26.1.0

26.1.10 - Minor Update (old 1.21.80)                         -

26.2.00 - Chase the Sky                                            26.2.0

26.2.10 - Minor update (old 1.21.100)                        -

26.3.00 - Copper Age                                                 26.3.0

26.3.10 - Minor Update (old 1.21.120)                        -

26.4.00 - Mounts of Mayhem                                      26.4.0

The 0 on the end of each version number is changed for every hotfix that is released.

This update numbering systems makes the drops more easier to remember and simpler between bedrock and java as the numbers are the same (and for drops) other than bedrock having an extra 0 for its extra minor updates.

Avatar
Registered User shared this idea

1 Comments

Post a new comment:

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 2
    Registered User commented
    Comment actions Permalink

    Personally I think the inclusion of the year as the major update identify is massively unnecessary. This results in version changes when only minor tweaks have occurred between drops. I feel the reason Mojang would choose to do this would be to have an excuse to increase the version number every year after a bunch of drops, and while this can be an easy solution for them to update the version, this is (believe it or not) completely unnecessary. There’s no reason for a larger scale increment that occurs specifically once a year. It adds no benefit. I would suggest keeping your drop vs minor formatting and propose we just keep 1.21 as the version for now. If there’s a time when enough is added that Mojang feels the need to increment to 1.22, then go for it. But for now I agree that this “solution” fails to actually solve anything, as you have mentioned.