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

  • Oxysis/Oxy@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    4
    ·
    19 hours ago

    Mojang started adding in substantive resource pack changes in the patches for 1.19. Which made it more annoying for resource pack artists to support the update their since it required 2 separate versions of a pack to be made and maintained just to make sure it works properly. Let alone the annoyance of having to constantly deal with people complaining about it not working when it is an issue Mojang made.

    There is also Mojang’s censorship of their community that began in the 1.19 patch versions which allowed Mojang to just ban anyone for saying something they didn’t like. Servers largely just disable it since it’s a headache to deal with and it doesn’t benefit them at all, only Mojang.

    Then in 1.20 and 1.21 Mojang began adding content in the patches so it makes it a nightmare to support the patch versions since they now function differently than they used to. Which only makes it harder for servers to update and makes the experience of joining servers more frustrating. So plenty of servers on those updates just blacklist certain versions just to make sure things are able to function.

    Oh and at some point Mojang added censorship to player skins. And it can be triggered by just mass reporting any individual skin for any reason.

    Basically Mojang made a fuck ton of problems where none needed to be or used to be.

    • Oxysis/Oxy@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      5
      ·
      19 hours ago

      Also I just want to add this, but I was sounding the alarm on the patch version problem back in the 1.19 days. The community at the entire either ignored me or called me crazy for pointing out how it was problematic. Now the community is growing more and more annoyed and I’m just sitting over here saying I told you so.

      I’ve mostly stopped playing the game because of Mojang’s constant shitty choices and because of the community refusing to call Mojang out on their bullshit.

      • Truscape@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        9
        ·
        18 hours ago

        The no chat reports mod and having community hosted servers that don’t really need to give a damn about what Mojang thinks (I’ll convert my server to support cracked accounts if I have to) kind of pulls the heavy lifting to allowing players to keep playing without having to give a shit about overall moderation by the company.

        • Oxysis/Oxy@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          5
          ·
          18 hours ago

          The no chat reports mod is great but it still is an uphill battle to get players to install it. We also need to focus on putting on Mojang to remove the problematic system in the first place so the experience is better for everyone including Bedrock players.

          • Truscape@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            9
            ·
            17 hours ago

            Installing the mod (or plugin) server-side strips all player chat messages of the information that makes them reportable, so no requirement is needed for the client (Although recommended for complete protection and for usage on non-compatible servers)