Mods › c:ingots/bronze

`c:ingots/bronze`

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.

6items in it

6mods with members

20mods using it in a recipe

2spellings merged

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

Alloyed 1 item

	Item	Identifier
	Bronze Ingot	`alloyed:bronze_ingot`

Create Big Cannons 1 item

	Item	Identifier
	Bronze Ingot	`createbigcannons:bronze_ingot`

Mekanism 1 item

	Item	Identifier
	Bronze Ingot	`mekanism:ingot_bronze`

Silent Gear 1 item

	Item	Identifier
	Bronze Ingot	`silentgear:bronze_ingot`

Ultramarine 1 item

	Item	Identifier
	Bronze Ingot	`ultramarine:bronze_ingot`

Mods that name it in a recipe

alloyed, basicweapons, createbigcannons, delightful, design_decor, immersiveengineering, magistuarmory, mekanism, mekanismtools, mythicmetals, occultism, oritech, prefab, spartanshields, spartanweaponry, tconstruct, tfc, ultramarine

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