Mod conflicts

Failed to Build Config Options: Value Formatter Must Be Set (Iris & Sodium)

What it looks like in the log

java.lang.NullPointerException: Value formatter must be set

How to fix it

  1. Update Iris Shaders to version 1.10.1 or newer, where the Sodium Config API overlay bug was fixed.
  2. Update Sodium and any mods that add or modify Sodium config options (such as C2ME) to their latest available builds.
  3. If an updated Iris build is not available for your modpack yet, temporarily disable Iris Shaders or downgrade/update C2ME to a version that does not use config overlays.
LoadersFabric, Neoforge, Quilt
SeverityStops the game
CategoryMod conflicts

Check your own logDownload sodium on 9Minecraft

Related errors

Mod conflictsAE2 Crash Viewing Unnamed Cable Tooltip When Channels Are DisabledUpdate Applied Energistics 2 to the latest `rv3` release for Minecraft 1.7.10, which updates recipes automaticMod conflictsCrash on World Load: class_5944.method_34583 NullPointerException (Iris & Rendering Mod Conflict)Remove or disable Immersive Portals from your `mods` folder if it is installed alongside Iris Shaders, as its Mod conflictsInvisible Blocks and Console Spam: Sodium ColorProvider.getColors NullPointerExceptionUpdate LittleTiles (and CreativeCore) to the latest version available for your Minecraft version, as newer relMod conflictsIris Shaders: Tried to use a destroyed GlResourceOpen Options -> Video Settings -> Shader Packs and turn shaders off before loading into a world, then re-enablMod conflictsOptiFabric Crash: Cannot Invoke class_5944.setSampler Because shaderinstance Is NullRemove both OptiFabric and the OptiFine JAR from your mods folder, and use native Fabric alternatives like SodMod 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 Nv