Modloader
NeoForge
Minecraft version
1.21.1
Hex Casting version
0.12.0-devel-pre-17
Modloader version
21.1.234
Modpack info
https://modrinth.com/modpack/ottercraft-modpack (unfortunately not yet passed moderation, but I can provide a download or access if needed)
The latest.log file
https://mclo.gs/88wPtKR
Issue description
When starting the game with hex casting installed, sometimes it crashes during mod loading with the error IllegalStateException: There should be exactly one IClientXplatAbstractions implementation on the classpath. Found: [].
Launching the game again usually results in the same error not appearing. It also seems to me as if the error is more likely to occur after changes have been made to the modpack, but it is neither guaranteed nor exclusive to this condition.
Steps to reproduce
- Install Hexcasting 0.12.0-devel-pre-17 and P.A.U.C.A.L. 0.7.1-pre-27+1.21.1-neoforge or a modpack containing both (direct link to the Modrinth modpack I used here)
- Start the modpack
- If error doesn't occur, try disabling or enabling any other mod, then repeat
Other information
I understand that due to the nondeterministic nature of this bug it's hard to identify its cause, so if you have anything you need me to look out for specifically, feel free to let me know.
I've experienced this issue using Prism Launcher 11.0.2 and some of my friends have had the same issue with the official Modrinth app (so likely the launcher has nothing to do with it).
Modloader
NeoForge
Minecraft version
1.21.1
Hex Casting version
0.12.0-devel-pre-17
Modloader version
21.1.234
Modpack info
https://modrinth.com/modpack/ottercraft-modpack (unfortunately not yet passed moderation, but I can provide a download or access if needed)
The latest.log file
https://mclo.gs/88wPtKR
Issue description
When starting the game with hex casting installed, sometimes it crashes during mod loading with the error
IllegalStateException: There should be exactly one IClientXplatAbstractions implementation on the classpath. Found: [].Launching the game again usually results in the same error not appearing. It also seems to me as if the error is more likely to occur after changes have been made to the modpack, but it is neither guaranteed nor exclusive to this condition.
Steps to reproduce
Other information
I understand that due to the nondeterministic nature of this bug it's hard to identify its cause, so if you have anything you need me to look out for specifically, feel free to let me know.
I've experienced this issue using Prism Launcher 11.0.2 and some of my friends have had the same issue with the official Modrinth app (so likely the launcher has nothing to do with it).