Mods › c:ingots/lead

`c:ingots/lead`

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

16mods using it in a recipe

2spellings merged

Written as c:ingots/lead, forge:ingots/lead. 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.

Confluence 1 item

	Item	Identifier
	Lead Ingot	`confluence:lead_ingot`

Create Nuclear 1 item

	Item	Identifier
	Lead Ingot	`createnuclear:lead_ingot`

Immersive Engineering 1 item

	Item	Identifier
	Lead Ingot	`immersiveengineering:ingot_lead`

Mekanism 1 item

	Item	Identifier
	Lead Ingot	`mekanism:ingot_lead`

Superb Warfare 1 item

	Item	Identifier
	Lead Ingot	`superbwarfare:lead_ingot`

Create: The Factory Must Grow 1 item

	Item	Identifier
	Lead Ingot	`tfmg:lead_ingot`

Mods that name it in a recipe

confluence, create, createnuclear, delightful, design_decor, immersiveengineering, mekanism, mekanismgenerators, occultism, spartanshields, spartanweaponry, superbwarfare, supplementaries, tconstruct, tfmg

16 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.