Mod conflicts

NullPointerException: Cannot get config value without assigned Config object present

What it looks like in the log

java.lang.NullPointerException: Cannot get config value without assigned Config object present

How to fix it

  1. Check your mods folder and remove any mods built for a different Minecraft version (such as a 1.13 mod left inside a 1.14+ folder), as an incompatible mod can silently abort Forge's config loading stage.
  2. Open logs/latest.log or logs/debug.log and search near the top of the file for the very first ERROR or Exception during mod loading to identify which mod broke startup before configs were assigned.
  3. Inspect the lines directly below ForgeConfigSpec$ConfigValue.get in the crash stack trace; if a mod package appears there instead of net.minecraft, update or remove that specific mod.
  4. Update Forge to the newest build available for your Minecraft version, especially on 1.13.2 and 1.14.2 where early releases failed to assign server configs when connecting to servers.
  5. Back up and delete forge-client.toml and forge-common.toml from your config folder (plus forge-server.toml inside your world's serverconfig folder) so Forge regenerates fresh files on launch.
LoadersForge
SeverityStops the game
CategoryMod conflicts

Check your own log

Related errors