DEPTANA
RUEN

Crash Diagnostics: NightConfig ParsingException (.toml)

Forge / NeoForge (NightConfig)

Pre-loaded crash log extracting the exact corrupted configuration filename.

Corrupted Mod Config File (config/create-client.toml)

Configuration file "config/create-client.toml" could not be parsed.

Matched error signature in log:
net.minecraftforge.fml.ModLoadingException: FailedModLoadingException: Forge config file create-client.toml failed to load
Troubleshooting steps:
  1. Delete config/create-client.toml so the mod regenerates a clean default file.

Questions & reference

How do I fix: Corrupted Mod Config File (config/create-client.toml)?

Configuration file "config/create-client.toml" could not be parsed. Delete config/create-client.toml so the mod regenerates a clean default file.

Where do I find my Minecraft error log?

Open your game profile folder. Copy a file from crash-reports or logs/latest.log. Exit Code 1 alone does not explain the crash.

Where is my log sent?

Analysis runs in your browser. Your log is not uploaded to DEPTANA, stored in settings, or included in a shared URL. The text limit is two million characters.

Does a match prove the cause?

Diagnostics checks known error signatures. A match suggests what to inspect; it does not prove the sole cause. If no rule matches, the tool says so.

Related calculators & presets in this section

Crash Log Analyzer (paste your log)Sodium & OptiFine Conflict (MixinApplyError)Java Version Mismatch (UnsupportedClassVersionError)Missing Mod Dependencies (ModLoadingException)Ticking Entity World CrashOutOfMemoryError: Java heap spaceGLFW Error 65542 (OpenGL Driver)SocketException: Connection reset (getsockopt)Exit Code -1073740791 & EXCEPTION_ACCESS_VIOLATIONDuplicateModsFoundException (Duplicate Mods)Exception Ticking World CrashCorrupted level.dat (ReportedNbtException)