What this means for modders
We know that this change may pose challenges for existing modding tools, which are typically designed for obfuscated code, and we’re going to help modders prepare for this change. Starting with the next snapshot we will provide un-obfuscated “experimental release” versions alongside obfuscated ones. Modders will be able to use these to test their tools and workflows before we transition fully to non-obfuscated versions.
The first snapshot following the complete Mounts of Mayhem launch will be the first version without obfuscation.
Why are we doing this?
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!
No changes to EULA
Just a quick reminder: these changes don’t affect our Minecraft End User License Agreement and Minecraft Usage Guidelines. Both still apply to Minecraft: Java Edition and any mods, so please keep them in mind. For extra transparency, you’ll now find a LICENSE file inside the jar that links directly to the EULA.
Here’s what modders can expect in upcoming releases and snapshots:
No more obfuscation maps in version .jsons – as they’re no longer needed
The client and server .jar files won’t be obfuscated
Each .jar now includes a new LICENSE file
As with all of our releases, we’ll want your feedback on this change – especially as we transition from an obfuscated past into our new, more transparent future!