Comment on Minecraft is removing code obfuscation in Java Edition
DaPorkchop_@lemmy.ml 5 days agoMy point is that literally nobody has been looking at obfuscated code for at least 5 years by now. All the toolchains automatically handle de- and reobfuscation transparently to the point that nobody has to think about it anymore unless maybe you are one of the like 3 people who is actually maintaining the classloading stage of a modloader, or if you are manually writing a bytecode transformer (which almost nobody has needed to do for years either, ever since tools like Mixin entered the scene).
For 99.9% of the modding community, and this includes most optimization mods, the only thing that is going to change is everyone deletes a line or two from their build.gradle and continues about their day.
As far as reporting things to Mojang: again, nothing changes here either, everyone who has ever set up a mod dev environment already has a copy of the deobfuscated source code on their computer, which is the only thing they are looking at when inspecting the minecraft source code or making changes to it. There have been reports on the issue tracker with actual suggested code changes basically since the issue tracker became a thing.
Unattributed@feddit.online 4 days ago
Okay - I am a bit of a dreamer, but I hope that Mojang dropping the obfuscation side of things is a sign that they are interested in working more closely with the community.
Of course, if I were to put on my pessimistic hat, I might think this is a move for Mojang to distance themselves from the Java edition as it’s likely that Microsoft thinks from a business perspective focusing on Bedrock is a better deal.