Fixing Crashes and Rendering Conflicts Between Sodium, Indium, and Other Mods

Identify the Real Culprit

Indium rarely crashes on its own. When something goes wrong, it is usually a mod using the Fabric Rendering API in a way that conflicts with Sodium, or a mod that assumes vanilla rendering. Read the crash log's top stack trace to see which mod's rendering code failed.

Troubleshooting Steps

1. Confirm Sodium and Indium are both present and are builds meant for the same Minecraft version and mod loader. Mismatched versions are a frequent cause of startup crashes.

2. Remove other rendering-optimisation mods that overlap with Sodium's role. Two mods trying to replace the same rendering pipeline will conflict.

3. If the crash names a specific block or entity mod, test without that mod. If the crash disappears, the issue is that mod's compatibility with Sodium, not Indium itself.

4. Check for mods that bundle their own copy of the Fabric Rendering API or a rendering library. Duplicate libraries cause class conflicts.

5. Update the offending mod first. Rendering-API compatibility is often fixed on the mod's side.

6. As a last resort, remove Indium and see whether the crash changes. If it becomes a visual glitch instead of a crash, you have confirmed Indium was translating an incompatible call.

Report persistent issues to the mod that owns the failing render code, not to Indium.