Mods › c:ores/tin

`c:ores/tin`

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.

9items in it

3mods with members

8mods using it in a recipe

2spellings merged

Written as c:ores/tin, forge:ores/tin. 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 5 items

	Item	Identifier
	Corruption Tin Ore	`confluence:corruption_tin_ore`
	Deepslate Tin Ore	`confluence:deepslate_tin_ore`
	Fleshification Tin Ore	`confluence:fleshification_tin_ore`
	Sanctification Tin Ore	`confluence:sanctification_tin_ore`
	Tin Ore	`confluence:tin_ore`

Mekanism 2 items

	Item	Identifier
	Deepslate Tin Ore	`mekanism:deepslate_tin_ore`
	Tin Ore	`mekanism:tin_ore`

Mods that name it in a recipe

alloy_forgery, create, immersiveengineering, mekanism, occultism, oritech, tconstruct

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