Reading the log

Sodium Mod Config Not Found (Hidden NeoForge Mod Loading Error)

What the log looks like

java\.lang\.RuntimeException: Sodium mod config not found
net\.caffeinemc\.mods\.sodium\.client\.config\.ConfigManager\.registerConfigs\(ConfigManager\.java

How to fix it

  1. Open logs/latest.log from your instance folder rather than relying only on the crash report, as the real failure happens earlier during mod loading.
  2. Search latest.log above the Sodium crash for lines containing ERROR, Error during pre-loading phase, Failed to register, NoClassDefFoundError, or MixinPreProcessorException.
  3. Check the bottom of the crash report as well for any Caused by section that names a completely different mod.
  4. Remove, update, or install the required dependencies for the mod identified in that earlier error (frequent causes include incompatible mods loaded through Sinytra Connector or outdated addons).
  5. If you have trouble finding the culprit in latest.log, temporarily disable Sodium and launch the game once so NeoForge can display its built-in error screen naming the broken mod, then re-enable Sodium after fixing it.
LoadersNeoforge
SeverityStops the game
CategoryReading the log

Check your own log

Related errors

Reading the logFabric Crash: NumberFormatException: For input string: "4 "Open `.minecraft/logs/latest.log` in a text editor and find the `[main/WARN]: Mod resolution failed` section rReading the logForge LoadingFailedException: Loading errors encounteredLook at the lines immediately inside 'Loading errors encountered: [ ... ]' to find the failing mod's name and Reading the logForge Mod Loading Crash (LoaderExceptionModCrash)Open the crash report and find the 'LoaderExceptionModCrash: Caught exception from <Mod Name>' line to see whiReading the logHarmless Server Warning: ClassNotFoundException: net/minecraft/class_5616 (registrate-fabric)Ignore [main/WARN] lines referencing net/minecraft/class_5616 (from registrate-fabric) as well as class_906 anReading the logInvocationTargetException — the real error is wrapped insideThis exception never is the cause — it only wraps another oneReading the logNullPointerException: "this.cpuVendor" is null (OSHI Warning)Check that this message is marked `[main/WARN]` in your log; it does not stop Minecraft or your server from ru