Mods › c:ores/diamond

`c:ores/diamond`

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.

12items in it

4mods with members

6mods using it in a recipe

2spellings merged

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

	Item	Identifier
	Corruption Diamond Ore	`confluence:corruption_diamond_ore`
	Fleshification Diamond Ore	`confluence:fleshification_diamond_ore`
	Sanctification Diamond Ore	`confluence:sanctification_diamond_ore`

Deeper and Darker 2 items

	Item	Identifier
	Gloomslate Diamond Ore	`deeperdarker:gloomslate_diamond_ore`
	Sculk Stone Diamond Ore	`deeperdarker:sculk_stone_diamond_ore`

Spelunkery 5 items

	Item	Identifier
	Andesite Diamond Ore	`spelunkery:andesite_diamond_ore`
	Diorite Diamond Ore	`spelunkery:diorite_diamond_ore`
	Granite Diamond Ore	`spelunkery:granite_diamond_ore`
	Smooth Basalt Diamond Ore	`spelunkery:smooth_basalt_diamond_ore`
	Tuff Diamond Ore	`spelunkery:tuff_diamond_ore`

The Undergarden 2 items

	Item	Identifier
	Depthrock Diamond Ore	`undergarden:depthrock_diamond_ore`
	Shiverstone Diamond Ore	`undergarden:shiverstone_diamond_ore`

Mods that name it in a recipe

enderio, immersiveengineering, mekanism, occultism, tconstruct

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