Mods › c:ores/gold

`c:ores/gold`

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

5mods with members

9mods using it in a recipe

2spellings merged

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

AoA3 1 item

	Item	Identifier
	Precasian Gold Ore	`aoa3:precasian_gold_ore`

Confluence 3 items

	Item	Identifier
	Corruption Gold Ore	`confluence:corruption_gold_ore`
	Fleshification Gold Ore	`confluence:fleshification_gold_ore`
	Sanctification Gold Ore	`confluence:sanctification_gold_ore`

Deeper and Darker 2 items

	Item	Identifier
	Gloomslate Gold Ore	`deeperdarker:gloomslate_gold_ore`
	Sculk Stone Gold Ore	`deeperdarker:sculk_stone_gold_ore`

Spelunkery 4 items

	Item	Identifier
	Andesite Gold Ore	`spelunkery:andesite_gold_ore`
	Diorite Gold Ore	`spelunkery:diorite_gold_ore`
	Granite Gold Ore	`spelunkery:granite_gold_ore`
	Tuff Gold Ore	`spelunkery:tuff_gold_ore`

The Undergarden 1 item

	Item	Identifier
	Depthrock Gold Ore	`undergarden:depthrock_gold_ore`

Mods that name it in a recipe

alloy_forgery, bloodmagic, enderio, eternal_starlight, immersiveengineering, mekanism, occultism, tconstruct

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