![Puzzles Lib [Forge & Fabric]](https://media.forgecdn.net/avatars/thumbnails/776/232/256/256/638118144989284933.png)
[Crash]: Crash on Startup with UnsupportedClassVersionError - Puzzles Lib v21.1.36 on Minecraft 1.21.1
Closed this issue ยท 2 comments
Mod Loader (Required)
Fabric
Minecraft Version(s) (Required)
MC v. 1.21.1, Fabric v. 0.16.14
Mod Version(s) (Required)
21.1.36
Other Mods Involved (Required)
No
Notes (Required)
Hello,
I'm experiencing a consistent crash on startup when using the latest version of Puzzles Lib on Minecraft 1.21.1. The crash report seems to point to a Java version incompatibility.
Java Version: 21.0.6 (OpenJDK 64-Bit Server VM)
Issue Description:
The game crashes during the initialization phase. The crash log shows a java.lang.UnsupportedClassVersionError
, showing that the mod might have been compiled with a newer version of Java than the one used by Minecraft 1.21.1.
The key error looks to be:
java.lang.UnsupportedClassVersionError: net/minecraft/class_332 has been compiled by a more recent version of the Java Runtime (class file version 66.0), this version of the Java Runtime only recognizes class file versions up to 65.0
This issue occurs with Puzzles Lib and any dependent mods (like Easy Anvils, Diagonal Fences, etc.).
Steps to Reproduce (I think):
- Set up a Fabric instance for Minecraft 1.21.1.
- Install Fabric API.
- Install Puzzles Lib
v21.1.36
. - Attempt to launch the game.
- The game might crash before reaching the main menu.
Thank you for your time and for maintaining this essential library.
Crash Report (Required)
latest.log (Optional)
Yeah, that's something with the Java version. There isn't really something I can do about that, I can only recommend to try and install different distributions of Java 21 if your current one does not work.
Yeah, that's something with the Java version. There isn't really something I can do about that, I can only recommend to try and install different distributions of Java 21 if your current one does not work.
After some troubleshooting, I found the two mods responsible. They were not related to yours at all, thank you for the assistance anyway.