Minecraft: Java Edition has been obfuscated since its release. This obfuscation meant that people couldn’t see our source code. Instead, everything was scrambled – and those who wanted to mod Java Edition had to try and piece together what every class and function in the code did.

Modding is at the heart of Java Edition – and obfuscation makes modding harder. We’re excited about this change to remove obfuscation, as it should make it quicker and easier for modders to create and improve mods. Now you won’t have to untangle tricky code or deal with unclear names. What’s more, de-bugging will become more straightforward, and crash logs will actually be readable!

surprisingly fantastic and consumer friendly move from mojang, good on them

  • JustARegularNerd@lemmy.dbzer0.comEnglish
    35·
    23 hours ago

    Previously, they had the versioning system 1.MAJOR.MINOR, where Major referred to a feature update, and minor referred to bug fixes or other non-breaking technical changes

    The first instance where they broke this was 1.16.2 by adding the Piglin Brute, but this was so minor that hardly anyone really cared, and hey, free feature with a minor update!

    Well, now they have update “drops” where the minor version means either what it used to, or it’s also a feature update, just not as big as a full update.

    From the wiki:

    • 1.20: Trails and Tales Update
    • 1.20.3: Bats and Pots Drop
    • 1.20.5: Armored Paws Drop
    • 1.21: Tricky Trials Update
    • 1.21.2: Bundles of Bravery Drop
    • 1.21.4: The Garden Awakens Drop
    • 1.21.5: Spring to Life Drop
    • 1.21.6: Chase the Skies Drop
    • 1.21.9: Copper Age Drop
    • Oxysis/Oxy@lemmy.blahaj.zoneEnglish
      231·
      23 hours ago

      That’s close to how the numbering system works! It’s MAJOR.MINOR.PATCH, Mojang just doesn’t use the major part at all.

      Also I completely forgot the piglin brute existed! Also netherite templates got added it the 1.16 patch versions too if I am remembering right.

      • mercano@lemmy.worldEnglish
        18·
        22 hours ago

        It’s kind of like Java itself, Sun dropped the leading 1 after 1.4, following it up with Java 5.

      • magz :3@lemmy.blahaj.zoneEnglish
        4·
        16 hours ago

        the problem is that the way version numbers are handled now, it’s more like 1.MAJOR.MINOR, with no real definition of what counts as a “minor” update, so it’s hard to tell which versions are compatible. i feel like this problem would mostly go away if they either added another number to the version to signify patches, or actually used semver properly (they could mix these approaches to do something similar to java, so the next version would be 22.0.0)

        i feel like this whole version debacle is only gonna get worse because microsoft is planning to move to a “content drop” model, with smaller more frequent updates, which means even more pressure on the “patch” version. so unless their update model or versioning systen changes, we’ll probably be playing 1.21.37 in a couple of years, and good luck figuring out which of those versions are actually compatible