[Bug] Crashing with KubeJS compat loading
sorae42 opened this issue · 8 comments
Temporary Fix
Just in case you also run into this problem and you have KubeJS installed:
Downgrade KubeJS to 2101.7.2-build.181 version of KubeJS for the time being until further notices.
Minecraft Version
- 1.12.2 (End of support)
- 1.16.5 (End of support)
- 1.18.2 (End of support)
- 1.19.2 (End of support)
- 1.20/1.20.1
- 1.21/1.21.1
What happened?
Trying to load TLM with KubeJS make it crash for missing Class definition of "ItemEvents".
Relevant log output
---- Minecraft Crash Report ----
// There are four lights!
Time: 2025-10-14 19:45:59
Description: Mod loading failures have occurred; consult the issue messages for more details
net.neoforged.neoforge.logging.CrashReportExtender$ModLoadingCrashException: Mod loading has failed
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Render thread
Stacktrace:
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[?:?] {}
-- Mod loading issue for: kubejs --
Details:
Caused by 0: java.lang.NoClassDefFoundError: dev/latvian/mods/kubejs/bindings/event/ItemEvents
at TRANSFORMER/[email protected]+mc1.21.1/com.github.tartaricacid.touhoulittlemaid.compat.kubejs.event.MaidEventsJS.<clinit>(MaidEventsJS.java:18) ~[touhoulittlemaid-1.4.1-neoforge+mc1.21.1.jar%23463!/:1.4.1-neoforge+mc1.21.1] {re:classloading}
at TRANSFORMER/[email protected]+mc1.21.1/com.github.tartaricacid.touhoulittlemaid.compat.kubejs.ModKubeJSPlugin.registerEvents(ModKubeJSPlugin.java:52) ~[touhoulittlemaid-1.4.1-neoforge+mc1.21.1.jar%23463!/:1.4.1-neoforge+mc1.21.1] {re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.event.EventGroups.lambda$static$0(EventGroups.java:12) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) ~[?:?] {re:mixin}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.plugin.KubeJSPlugins.forEachPlugin(KubeJSPlugins.java:115) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:mixin,re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.event.EventGroups.lambda$static$1(EventGroups.java:12) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.util.Lazy.get(Lazy.java:80) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.script.ScriptType.unload(ScriptType.java:94) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:mixin,re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.script.ScriptManager.unload(ScriptManager.java:43) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.script.ScriptManager.reload(ScriptManager.java:58) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
at TRANSFORMER/[email protected]/dev.latvian.mods.kubejs.KubeJS.<init>(KubeJS.java:130) ~[kubejs-neoforge-2101.7.2-build.270.jar%23396!/:2101.7.2-build.270] {re:classloading}
... log has been truncated.Seem to be not compatible with 2101.7.2-build.270 version of KubeJS, downgrading to build.181 works.
can confirm here
This KJS update has changed the basic content.
I can't maintain compatibility between the old and new versions, and I suspect the same issue applies to other add-on mods.
I'm holding off on updating for now, as this will only lead to further issues.
我把jar中的 com/github/tartaricacid/touhoulittlemaid/compat/kubejs/ModKubeJSPlugin.class 删掉了, 目前作为暂时的兼容手段可以正常使用,只是暂时不能用kubejs修改女仆相关内容了
@TartaricAcid I have provided a temporary fix on the top of the issue text. You may want to inform people who may get the same issue.
@sorae42 The solution to fix the problem is simple, but the difficulty now is that it is not compatible with both 270 and 181 versions.