Wrong fml translation key used, leading to crash when displaying loading errors
Erdragh opened this issue · 4 comments
java.lang.IllegalArgumentException: When using FML translation keys, only use fml.modloadingissue. keys for mod loading issues: fml.modloading.javafml.dangling_entrypoint
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.ModLoadingIssue.<init>(ModLoadingIssue.java:30) ~[loader-4.0.24.jar%23132!/:4.0] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.ModLoadingIssue.<init>(ModLoadingIssue.java:24) ~[loader-4.0.24.jar%23132!/:4.0] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.ModLoadingIssue.error(ModLoadingIssue.java:35) ~[loader-4.0.24.jar%23132!/:4.0] {}
at LAYER PLUGIN/[email protected]/thedarkcolour.kotlinforforge.neoforge.KotlinLanguageLoader.validate(KotlinLanguageLoader.kt:51) ~[kfflang-neoforge-5.4.0.jar%23193!/:5.4.0] {}
The line mentioned in this stacktrace uses fml.modloading.[...] instead of fml.modloadingissue.[...]:
Hi,
would you mind releasing 5.5.0 or at least create a workflow for automatically building the mod?