crash on load up neoforge-1.21.11-21.11.13

[SDUBZ]

Issue type:

• 🐛 Bug
  Caught exception during event net.neoforged.fml.event.lifecycle.FMLCommonSetupEvent@49aac4b7 dispatch for modid cyclopscore
  java.lang.NoClassDefFoundError: org/cyclops/cyclopscore/metadata/RegistryExportableItemTranslationKeys
  at TRANSFORMER/cyclopscore@1.25.5/org.cyclops.cyclopscore.metadata.RegistryExportables.load(RegistryExportables.java:17)
  at TRANSFORMER/cyclopscore@1.25.5/org.cyclops.cyclopscore.CyclopsCoreNeoForge.setup(CyclopsCoreNeoForge.java:118)

---

Short description:

Steps to reproduce the problem:

1. crashes on laod up not sure why the cyclops core fails

Expected behaviour:

---

Versions:

• This mod: cyclopscore-1.21.11-neoforge-1.25.5-875
• Minecraft: 1.21.11
• Mod loader version: neoforge-1.21.11-21.11.13

Log file:

latest.log

[rubensworks]

Thanks for reporting!

[Jack-McKalling]

According to this exception in the log, some module descriptors may need tweaking or the wrong version of something is being referenced.

Caused by: java.io.IOException: Module cyclopscore has been closed
	at net.neoforged.fml.classloading.ModuleClassLoader$ModuleInfo.getReader(ModuleClassLoader.java:519)

[rubensworks]

That's a weird error. I've never seen that one before.
Does you get this error consistently?
Or does it occur for different classes and/or mods?
Does the problem persist when no other mods are installed?
What about different NeoForge versions?

[SDUBZ]

Its default options by blay worked it out mate

…

On Thu, 25 Dec 2025, 1:33 am Ruben Taelman, ***@***.***> wrote: *rubensworks* left a comment (CyclopsMC/CyclopsCore#214) <#214 (comment)> That's a weird error. I've never seen that one before. Does you get this error consistently? Or does it occur for different classes and/or mods? Does the problem persist when no other mods are installed? What about different NeoForge versions? — Reply to this email directly, view it on GitHub <#214 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLOSGIJEAVK76ZQMIBQIBD4DKP37AVCNFSM6AAAAACP57MINGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBZHE2DINRQGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Jack-McKalling]

All right, thanks for letting us know!

Would this be some form of incompatibility that could be looked into before closing, @rubensworks ?

[rubensworks]

Ok, considering this not an issue on our end then.