What I’d feared has now become reality.
Mojang has announced it’ll remove obfuscation from Minecraft Java Edition: https://www.minecraft.net/en-us/article/removing-obfuscation-in-java-edition
I believe this is excellent news for many Mod developers and those who are creating or intend to create ModLoader, as it reduces the workload of maintaining mappings and eliminates the need to reference intermediaries.
However, things have taken a turn for the worse for ExtraSounds. It has become extremely difficult to support 26.1-snapshot-1 while maintaining the traditional functionality of simultaneously supporting versions from 1.18.x to 1.21.11.
Here’s what happens: click to expand the technical issue.
1. Java bytecode confliction
fabric-loom accesses the class “dxo” indirectly under the name net/minecraft/class_310 in MC1.18. This instance is accessible as net/minecraft/client/MinecraftClient in modders code using Yarn Mappings. However, obfuscation has been removed, and simultaneously, fabric-loom no longer supports this level of intermediary access. As a result, class_310 no longer exists there; instead, net/minecraft/client/Minecraft (official named class by Mojang) is present. ExtraSounds must precisely control and simultaneously provide class_310 for Minecraft up to version 1.21.11, and Minecraft for Minecraft version 26.1 and later. No, that phrasing isn’t quite right. If ExtraSounds cannot provide these functions accurately, Minecraft will crash with a NoClassDefFoundError or a ClassCastException. This issue stems from Java language limitations, making implementation extremely difficult.
2. Jar processor confliction in AccessWidener
When attempting to import a deobfuscated Minecraft 26.1 into the Root Project, the AccessWidener processor in fabric-loom assumes/enforces that the namespace is “official”. This prevents maintaining compatibility with other mods. Even if ExtraSounds didn’t use AW at all, if AW is used anywhere - even just once - by another mod during integration attempts, Gradle configuration phase will report failure.
3. Mod-id confliction; fabric vs. fabric-api
I don’t understand why the Fabric team made that decision, but the mod-id in the Fabric API differs between versions 1.x and 26.x. ExtraSounds requires the Fabric API, but there is no provision in fabric.mod.json to specify this as an OR condition.
ExtraSounds 3.0.0+1.21.11 will be the final release for legacy Minecraft - version 1.x, and a new build versioning will begin as ExtraSounds 3.0.0+26.1.
Please note that there is no compatibility between two versions until this issue is still alive; ExtraSounds 3.0.0+26.1 will not support version 1.x.
What I’d feared has now become reality.
Mojang has announced it’ll remove obfuscation from Minecraft Java Edition: https://www.minecraft.net/en-us/article/removing-obfuscation-in-java-edition
I believe this is excellent news for many Mod developers and those who are creating or intend to create ModLoader, as it reduces the workload of maintaining mappings and eliminates the need to reference intermediaries.
However, things have taken a turn for the worse for ExtraSounds. It has become extremely difficult to support 26.1-snapshot-1 while maintaining the traditional functionality of simultaneously supporting versions from 1.18.x to 1.21.11.
Here’s what happens: click to expand the technical issue.
1. Java bytecode confliction
fabric-loom accesses the class “dxo” indirectly under the name
net/minecraft/class_310in MC1.18. This instance is accessible asnet/minecraft/client/MinecraftClientin modders code using Yarn Mappings. However, obfuscation has been removed, and simultaneously, fabric-loom no longer supports this level of intermediary access. As a result,class_310no longer exists there; instead,net/minecraft/client/Minecraft(official named class by Mojang) is present. ExtraSounds must precisely control and simultaneously provideclass_310for Minecraft up to version 1.21.11, andMinecraftfor Minecraft version 26.1 and later. No, that phrasing isn’t quite right. If ExtraSounds cannot provide these functions accurately, Minecraft will crash with aNoClassDefFoundErroror aClassCastException. This issue stems from Java language limitations, making implementation extremely difficult.2. Jar processor confliction in AccessWidener
When attempting to import a deobfuscated Minecraft 26.1 into the Root Project, the AccessWidener processor in fabric-loom assumes/enforces that the namespace is “official”. This prevents maintaining compatibility with other mods. Even if ExtraSounds didn’t use AW at all, if AW is used anywhere - even just once - by another mod during integration attempts, Gradle configuration phase will report failure.
3. Mod-id confliction;
fabricvs.fabric-apiI don’t understand why the Fabric team made that decision, but the mod-id in the Fabric API differs between versions 1.x and 26.x. ExtraSounds requires the Fabric API, but there is no provision in
fabric.mod.jsonto specify this as an OR condition.ExtraSounds 3.0.0+1.21.11 will be the final release for legacy Minecraft - version 1.x, and a new build versioning will begin as ExtraSounds 3.0.0+26.1.
Please note that there is no compatibility between two versions until this issue is still alive; ExtraSounds 3.0.0+26.1 will not support version 1.x.