Mods › c:ores/emerald

`c:ores/emerald`

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.

11items in it

4mods with members

6mods using it in a recipe

2spellings merged

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

Blue Skies 2 items

	Item	Identifier
	Emerald Ore	`blue_skies:everbright_emerald_ore`
	Emerald Ore	`blue_skies:everdawn_emerald_ore`

Confluence 3 items

	Item	Identifier
	Corruption Emerald Ore	`confluence:corruption_emerald_ore`
	Fleshification Emerald Ore	`confluence:fleshification_emerald_ore`
	Sanctification Emerald Ore	`confluence:sanctification_emerald_ore`

Deeper and Darker 2 items

	Item	Identifier
	Gloomslate Emerald Ore	`deeperdarker:gloomslate_emerald_ore`
	Sculk Stone Emerald Ore	`deeperdarker:sculk_stone_emerald_ore`

Spelunkery 4 items

	Item	Identifier
	Andesite Emerald Ore	`spelunkery:andesite_emerald_ore`
	Diorite Emerald Ore	`spelunkery:diorite_emerald_ore`
	Granite Emerald Ore	`spelunkery:granite_emerald_ore`
	Tuff Emerald Ore	`spelunkery:tuff_emerald_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.