this post was submitted on 03 Feb 2026
432 points (99.5% liked)
Programmer Humor
29320 readers
1171 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It does. It clearly says
java.lang.NoSuchMethodError. If that's too complicated for you, you still need help.I mean, it got that error in
class_5699.method_65313so it's not like it isn't obfuscated at all.Congratulations you've discovered that Mojang used to ship the game after it was obfuscated! Java has nothing to do with the fact it's obfuscated that's on Mojangs end, for goofy "This'll allow us to sue people who copy our game" logic. NeoForge came out the gate with official mappings at runtime (non obfuscated using the offical names Mojang provides. Yes Mojang obfuscated the game and then gives us the names of stuff anyway...) and recently Mojang announced they are finally dropping obfuscation all together.
Edit. To make sure this is totally clear the obfuscated names such as
class_5699.method_65313is the actual class name and method name. The jar has a class namedclass_5699which Java loads and treats like any other class. Very goofy and annoying for modders since if you wanted a useful name you have to first decompile Minecraft, then change all the names, and then when you compile change all references to said names in your code back to their actual obfuscated nonsense.I expect this is what things like Forge were handling, right?
That's on the dev end of things but yes. Part of the build pipeline was re-obfuscation of your code so it'd actually work. Forge the mod loader just loaded the mods and provided code for modders to use. Forge Gradle was what handled the obfuscation stuff in dev
The next line implicates the
de.mschae23.grindenchantmentsmod; seems like a pretty clear starting point for troubleshooting.