Mod conflicts

48 errors

Two mods fighting over the same game code, or one mod breaking on another.

Page 2 of 2
Mod conflictsNullPointerException: Cannot read field "field_44912" because "this.field_4015.field_1724" is nullReplace any snapshot, CI, or development builds of Sodium with an official release build from Modrinth or CursMod conflictsOptiFabric Crash: "resourceName" is null During Shader ReloadUpdate both OptiFabric and Fabric API to the latest builds for your Minecraft version, as newer OptiFabric relMod conflictsOptiFine is not compatible with this mod setOptiFine patches the same code many performance mods patchMod conflictsREI Failed to Reload ServerDisplayRegistryImpl (GameInstance.getServer() is null)If REI's item panel and recipe lookups work normally in-game, you can safely ignore this log entry; it occurs Mod conflictsRoughly Enough Items Crash: Entry type minecraft:item doesn't exist!Update Roughly Enough Items (REI) and Architectury API to the latest build for your Minecraft version, as specMod conflictsSodium Crash Opening Video Settings: this.applyButton is nullFrom the Minecraft main menu, open Options -> Language and switch the game language to English (US) as an immeMod conflictsSodium Crash When Falling Into the Void (ChunkRenderColumn Index -1)Open your instance's mods folder and remove the outdated sodium-fabric-mc1.16.4-0.1.1-SNAPSHOT (or custom forkMod conflictsSodium Crash or Freeze When Joining World: renderSectionManager is nullRemove known conflicting rendering and FPS mods from your mods folder, specifically Better Fps - Render DistanMod conflictsSodium Crash: "geometryPlanes" is null in GFNITriggers (Translucent Sorting)Open Minecraft's Video Settings (or your Nvidium config file if crashing immediately on world load) and set NvMod conflictsSodium Crash: BufferUnderflowException in MultiDrawBatchCheck your crash report for 'cullleaves' in the stacktrace; if you have the Cull Leaves mod installed, remove Mod conflictsStackOverflowError — two mods calling each other foreverLook for the repeating block of lines in the trace — the loop is between those classesMod conflictsjava.lang.IllegalStateException: BufferBuilder not startedIf you are using shaders, turn off your active shader pack in Video Settings before loading the world, as custMod conflictsjava.lang.IllegalStateException: BufferBuilder was emptyCheck the second 'at' line right below 'BufferBuilder' in the crash stack trace to see which mod attempted theMod conflictsjava.lang.IllegalStateException: Not building! (BufferBuilder Render Crash)If you are using Iris Shaders with Sodium (or Oculus with Embeddium/Rubidium), update both mods to the latest Mod conflictsjava.lang.IllegalStateException: Pose stack not emptyOpen logs/latest.log and look just above the crash report for any earlier ERROR or Exception lines, which freqMod conflictsjava.lang.IllegalStateException: Rendersystem called from wrong threadLook directly below 'Rendersystem called from wrong thread' in your log: if there is an 'Index:' number above Mod conflictsjava.lang.NullPointerException: Rendering itemOpen the crash report, scroll down to the `-- Item being rendered --` section, and check the `Item Type:` lineMod conflictsjava.lang.NullPointerException: Rendering screenOpen the latest file in your `.minecraft/crash-reports/` folder and read the very first `at ...` line under `j
12