Mod conflicts

java.lang.IllegalStateException: BufferBuilder was empty

What the log looks like

java\.lang\.IllegalStateException: BufferBuilder was empty

How to fix it

  1. Check the second 'at' line right below 'BufferBuilder' in the crash stack trace to see which mod attempted the empty draw call.
  2. If the line mentions 'CloudRenderer' and 'sodium', update Sodium to version 0.5.10 or newer, or disable any resource packs that alter or hide clouds.
  3. If another rendering or overlay mod is named on that line (such as Simple Block Overlay or Roughly Enough Items), update that mod to its latest Minecraft 1.21+ build or remove it.
  4. If your game crashes immediately upon loading a world due to clouds or a texture pack, open 'options.txt' in your instance folder and change 'renderClouds' to 'false' or clear the 'resourcePacks:[]' list.
LoadersFabric, Quilt, Neoforge, Forge
SeverityStops the game
CategoryMod conflicts

Check your own log

Related errors

Mod conflictsAE2 Terminal Crash with REI: TextField.isFocused() NoSuchMethodErrorUpdate both Roughly Enough Items (REI) and Applied Energistics 2 (along with Cloth Config and Architectury APIMod conflictsApplied Energistics 2 Server Startup Crash (WorldData IllegalArgumentException with SpongeForge)Check your server's mods folder for SpongeForge (specifically builds around 1.12.2-2838-7.2.3) or check if youMod conflictsCannot Get Config Value Before Config Is LoadedOpen the full `logs/latest.log` or crash report and look at the `at ...` stack trace lines immediately below `Mod conflictsConcurrentModificationException — two threads touched the same listA mod bug, not a setting you can changeMod conflictsCould not execute entrypoint stage 'main'The "from mod" part names the mod whose startup threwMod conflictsCrash When Opening Inventory: IllegalArgumentException: Duplicate delegatesUpdate Iris Shaders (Fabric/Quilt) or Oculus (Forge/NeoForge) to the latest release for your Minecraft version