Modpack Conflict Radar

1.0.1 — important fix

Please use this version instead of 1.0.0.

1.0.0 accidentally shipped the test fixtures used to develop the scanner. On every install they wiped the minecraft:dirt tag, collided with the vanilla torch recipe, and overrode the cobweb loot table. A conflict detector causing conflicts. They are gone.

What's new

• /conflictradar — see the findings in game, instead of hunting for a text file.
• The report leads with what matters. A real pack contests a couple of hundred resources, almost all of them mods deliberately retuning vanilla. Reporting "225 conflicts" buried the ten that were actually broken. It now reports the problem count, and lists the expected cases separately.

What it finds

• Tag wipes — a mod sets "replace": true and deletes tag entries other mods added. Every lost entry is named.
• Recipe collisions — two recipes take the same ingredients and give different results. The game picks one. Load order cannot fix this, and the report says so.
• Sound wipes — "replace": true on a sound event silences what other packs registered.
• Silent overrides — one mod quietly beats another to a loot table, advancement or worldgen file.
• Custom data types — scanned directories come from the live registries, so mod-defined data is covered too.

Verified on a real pack: 14,505 resources across 27 packs in under a second, six genuine recipe collisions found between Quark, Supplementaries, Mekanism and Farmer's Delight.

No dependencies. No Mixins. Client and server.