Broken Tag Fixer silences the dreaded warning:
[Mekanism] Broken tags in Mekanism recipes detected
…and the whole class of problems behind it — empty item tags that recipes still reference.
It is generic: it is not tied to Mekanism. It works for any mod whose recipes point at an item tag that ended up empty (very common with optional cross-mod "compat" recipes, e.g. Ad Astra shipping a recipe but not the matching tag).
A mod ships a recipe that uses an item tag (for example forge:sandstone/venus_sandstone), but nothing ever fills that tag — the item exists, the recipe loads, yet the tag is empty. Minecraft/Mekanism then complain that the recipe has a broken ingredient, spamming your log on every launch.
At load time, Broken Tag Fixer scans every recipe of every mod (raw JSON, no mod API needed) and, for each empty tag a live recipe depends on, it applies a careful cascade:
This mod is intentionally conservative — it never "guesses wildly":
mod_loaded) are never touched. Many empty tags are intentional optional-compat — those are left alone.brokentagfixer-report.txt in your game directory, so you can see exactly what was done and why.Works on both client and server (recommended on both for a multiplayer setup). Lightweight, no config required to get the default safe behaviour.
Drop the matching file into your mods/ folder:
brokentagfixer-forge-1.0.0.jar → Minecraft 1.20.1 (Forge)brokentagfixer-neoforge-1.0.0.jar → Minecraft 1.21.1 (NeoForge)Then launch as usual and (optionally) read brokentagfixer-report.txt.
Broken Tag Fixer is data-friendly. If you'd like a specific case added to the built-in known-fix table, or you want to contribute a data-only fix (a tag → item mapping for a particular mod), come tell us on Discord.