#Craftoria crashed on startup from the Minecraft Launcher through CurseForge

1 messages · Page 1 of 1 (latest)

random sky
#

NeoForge started after the press of the Play button, but appx 30s after start, failed to continue to load the game.
I was playing fine last night - CurseForge pushed through an application update when I started the application this afternoon - that is the only setup change.

Craftoria crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log | crash-2025-07-25_14.02.11-client.txt | CurseForge: launcher_log.txt head / tail (~27k lines) | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

Removed mods:
What's your build-neoforge-1.21.1-0.3.0.jar

Updated mods:
computercraft (1.115.1 > 1.116.0)
random sky
#

I have restarted the PC, and issue still remains

random sky
#

Uninstalled Curseforge and associated files on local and roaming folders. uninstalled modpacks. completed clean installation, and placed save game in folder location. Issue is resolved - modpack loads and saves are untouched

#

I am happy for this thread to be closed with the issue being resolved, but I would be interested to find out what the original problem was! other mod packs were able to load and function correctly at the time Craftoria was not working

dawn quartz
#

pneumaticcraft's configuration file looked broken in the log above, causing it to fail to load

#

MalformedJsonException ... at line 1 column 52
...
at me.desht.pneumaticcraft.common.config.subconfig.AuxConfigJson.readFromFile:L84

#

so the PNC aux config file was corrupted at some point, and when PNC tried to load it, it was unable to load the bad file and crashed out its loader

#
umbral crystal
dawn quartz
#

would be interesting to see, but realistically you can recreate the crash by changing the thirdparty.cfg (or any auxconfig config it supports) to an invalid json file. for example, erasing all contents or erasing one of the closing brackets, or any number of things

#

it also resaves the file immediately after loading it iirc, meaning any failure at that point prior to it fully flushing the buffer to the file could cause it

random sky