Fixing a Crash Caused by a Missing or Mismatched Konkrete Dependency

Reading the crash instead of guessing

When a mod that uses Konkrete fails, the crash report or log usually names the library directly. Open the latest log file and search for the word Konkrete. You are looking for lines that say a required dependency is missing, or that a version range was not satisfied. That single line tells you whether you need to add Konkrete, remove it, or swap it for a different build.

Working through the fix

1. If the log says Konkrete is missing, add it to the mods folder alongside the mod that needs it. Both must be present.

2. If the log says a version is out of range, you have a mismatch. Either update Konkrete to a build the dependent mod accepts, or roll the dependent mod back to one that matches your Konkrete.

3. If two mods demand different, incompatible Konkrete versions, you cannot satisfy both at once. Pick the mod you want more and remove the other, or find a build of each that shares a common Konkrete version.

4. After any change, delete the old crash report and relaunch so you are reading a fresh log.

Avoiding repeat crashes

Keep Konkrete and every mod that depends on it updated together as a set. Updating one without the other is the most common cause of these failures, and the error message will look identical each time.