- cross-posted to:
- games@sh.itjust.works
- gaming@beehaw.org
- cross-posted to:
- games@sh.itjust.works
- gaming@beehaw.org
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
It has. There have been major rewrites of parts of the codebase, like Sodium, Cubic Chunk, server frameworks, just to start.
Major performance issues, and associated code fixes, have been repeatedly reported to Mojang’s tracker.
The issue is that any major modification is inherently incompatible with other major modifications, hence most persist for one version (or a few) before the devs burns out maintaining it. There are two solutions to this:
Get Mojang to pull in large optimizations. Thus far, they have been uninterested in this (though some controversy over Optifine may have left a bad taste).
Pull the changes into a modding framework. Understandably, Fabric/Forge aren’t willing to pull in a huge overhaul they’d have to maintain. Mojang may have similar feelings.
Some modifications (like Sodium) minimize vanilla changes to prioritize compatibility, and are popular to the extent that some other mods implement workarounds for them specifically. But this is rare, and it’s still problematic.
I remember that. I think the issue there was it mostly handled badly… It seemed like Mojang was trying to go behind the communities back (which I thought sounded a lot like the way Microsoft does things…so I blamed them instead of Mojang). IMO - if this is an era of more open-collaboration it may be possible for Mojang to benefit from working with the community. (There is an excellent example of this in the way AMD has worked with the Open Source community…)
I can see that too… That’s why I am thinking that it might be possible for there to be a more collaborative effort… Like a repository set up where community devs can submit PR’s for changes, and Mojang can either approve or deny them. If that started working well, I could see a situation where there are specifically Mojang employed community devs, the role of working on changes that will help both the main Minecraft tree and the modding community.
(Okay, I am probably more optimistic than I should be – after all Microsoft is in the mix here…)
Yeah, that sounds dreamy. It could certainly work.
And yeah, the problem is not just Microsoft but Mojang. Mojang is an extremely conservative/careful dev, even before they got bought by MS. It’s why the game hasn’t enshittified too bad, but also why development seems to move so slow for arguably the biggest game on Earth.
Collaborating via a repo like that would be… a lot.
Again, it’d be awesome and I think it would work, but it would be a massive step even if Microsoft wasn’t in the picture.
Yeah, Mojang’s conservative development style is arguably the reason for Minecraft’s success, while also being a source of frustration and friction for the community, IMO.
MS is another story altogether, though. While Mojang is a very thoughtful company, MS is driven by profit. I’m honestly surprised there aren’t more collisions between the two cultures.