Mods › c:dusts/iron

c:dusts/iron

A convention tag — the shared namespace mods use so they can work with each other's items. This is the compatibility signal; a vanilla tag is not.

7items in it
7mods with members
9mods using it in a recipe
2spellings merged

Written as c:dusts/iron, forge:dusts/iron. NeoForge renamed the convention namespace at 1.21, so one agreement between the same two mods ships under two strings; the rows are keyed on the canon form and every spelling is kept.

Members

The four counts above are corpus-wide and were computed once, across every extraction. The table below is what this database holds — a member whose mod is not loaded is listed and not linked.

Blood Magic 1 item

ItemIdentifier
Iron Sand bloodmagic:ironsand

Ender IO 1 item

ItemIdentifier
Powdered Iron enderio:powdered_iron

Immersive Engineering 1 item

ItemIdentifier
Iron Grit immersiveengineering:dust_iron

Mekanism 1 item

ItemIdentifier
Iron Dust mekanism:dust_iron

Occultism 1 item

ItemIdentifier
Iron Dust occultism:iron_dust

Oritech 1 item

ItemIdentifier
Iron Dust oritech:iron_dust

Superb Warfare 1 item

ItemIdentifier
Iron Powder superbwarfare:iron_powder

Mods that name it in a recipe

bloodmagic, immersiveengineering, mekanism, occultism, superbwarfare, tconstruct, tfmg

9 in the corpus; the rest are in mods this database does not hold.

Read out of data/<ns>/tags/** in each JAR. Tag membership is a fact in a data file; whether two mods actually work together is not something a tag can promise on its own.