Crash when trying to create a new world
Sunconure11 opened this issue ยท 9 comments
Minecraft Version
1.19.2
KubeJS Version
1902.6.0-build.79
Rhino Version
1902.2.1-build.242
Architectury Version
6.2.46
Forge/Fabric Version
Quilt 0.17.5-beta3
Describe your issue
Whenever I try to make a new world, I get a crash blaming your mod
Crash report/logs
Same error on my 1.19.2 fabric server with same message.
https://paste.ubuntu.com/p/PZq8zFBrkN/
Happens on 1.18.2 fabric after I updated to the latest kubejs/rhino released earlier today.
Rolling back to an earlier version fixes the problem for me.
I'm having the same issue and my post was closed and marked as "not planned", does that mean that this error is not going to be fixed or it was because the post was a duplicate?
I'm having the same issue and my post was closed and marked as "not planned", does that mean that this error is not going to be fixed or it was because the post was a duplicate?
Yes, when you go to close an issue github has a few words describing the two close states, and duplicate is one of the ones for not planned.
Well, I know that now. When people say "not planned", they usually mean "not going to be implemented", and not "this is a duplicate". A "closed as duplicate" would be way more clarifying.
Looks like it is because it is a duplicate of this issue. I had also brought it up on the Discord run by this dev.
Same problem here, both builds "KubeJS Fabric 1902.6.0-build.86" and "KubeJS Fabric 1902.6.0-build.79"
result in crash with:
Failed to load datapacks, can't proceed with server load. You can either fix your datapacks or reset to vanilla with --safeMode java.util.concurrent.ExecutionException: java.lang.NullPointerException: Cannot read field "logErroringRecipes" because "dev.latvian.mods.kubejs.server.ServerSettings.instance" is null
When trying to add this mod to an existing server / word.
Interestingly enough, this does not happen when starting the client, untill i click the singleplayer button
I'm having the same issue and my post was closed and marked as "not planned", does that mean that this error is not going to be fixed or it was because the post was a duplicate?
Yes, when you go to close an issue github has a few words describing the two close states, and duplicate is one of the ones for not planned.
