You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug RPGStats v5.2.1 (for Minecraft v1.21.0) crashes with a "Could not initialize class" error when running under QuiltMC 0.27.0-beta 1 and QFAPI 11.0.0-alpha.3 / QSL 10.0.0-alpha.1.
Further comments
Normally, I have a collection of mods running alongside this one. However, in attempting to update Minecraft to 1.21.0 (from 1.20.1), I ran into a few dozen snags. Eventually, I was able to narrow things down to this specific mod, as you can see.
Other versions were specifically marked for Quilt, but this one and the next one are marked specifically for "Fabric". As such, is probably my fault since I'm using the Quilted Fabric API instead of using Fabric. I would think it would work with either/or. Clearly not.
Not thrilled that it now uses another dependency on top of Kotlin, either, but that's neither here nor there.
The text was updated successfully, but these errors were encountered:
Describe the bug
RPGStats v5.2.1 (for Minecraft v1.21.0) crashes with a "Could not initialize class" error when running under QuiltMC 0.27.0-beta 1 and QFAPI 11.0.0-alpha.3 / QSL 10.0.0-alpha.1.
To Reproduce
Expected behavior
The game should load normally with RPGStats installed as a mod.
Actual outcome
The game crashes and generates an error log.
Screenshots and Logs
Environment
Mod list
See above.
Further comments
Normally, I have a collection of mods running alongside this one. However, in attempting to update Minecraft to 1.21.0 (from 1.20.1), I ran into a few dozen snags. Eventually, I was able to narrow things down to this specific mod, as you can see.
Other versions were specifically marked for Quilt, but this one and the next one are marked specifically for "Fabric". As such, is probably my fault since I'm using the Quilted Fabric API instead of using Fabric. I would think it would work with either/or. Clearly not.
Not thrilled that it now uses another dependency on top of Kotlin, either, but that's neither here nor there.
The text was updated successfully, but these errors were encountered: