Closed pali6 closed 6 months ago
Hey,
thanks a lot for the detailed report! I'll look into this ASAP (ideally tomorrow).
And you're correct about the submodule structure. I use the cerium-core
branch as a submodule for the two branches you named. This streamlined the process of applying changes on all MC versions from 1.7 to 1.20.
~ Accidentally closed, reopening.
The two main branches have been updated. As soon as the GitHub actions finish, you can download the fixed versions here: 1.20+ and below 1.20. The artifact ZIP files contain every JAR for all currently supported versions of the game.
Could you check if it now works fine with that fixed version (4.0.7)? If that's the case I'll later publish it on CF.
Yep, fixed. Thanks!
~ Version 4.0.7 has been published for Fabric, Forge and NeoForge.
Version: 4.0.6
Stack trace:
Example options.txt line that causes a crash:
key_key.fire_ability_one:scancode.72
https://github.com/Jomcraft-Network/DefaultSettings/blob/2b925bc5220a3a1e1d13202ffb183dc91445e028/src/main/java/net/jomcraft/defaultsettings/CoreUtil.java#L81 Logic on this line seems to be incorrect and/or outdated. The example options.txt line above fails both of those checks but since it has only one
:
the else branch will generate an emptykeyName
. Most likely thenumberParsable
check should be changed to acceptscancode.[number]
too. Or the else branch should always read at least one part instead of potentially reading zero.I can PR a fix if you want but I'm slightly confused about the way you have submodule structure set up. Is the branch
cerium-core
a submodule onmain
/main-1.20
?