Mods › c:ores/sapphire

`c:ores/sapphire`

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.

8items in it

3mods with members

4mods using it in a recipe

2spellings merged

Written as c:ores/sapphire, forge:ores/sapphire. 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 Sapphire Ore	`confluence:corruption_sapphire_ore`
	Deepslate Sapphire Ore	`confluence:deepslate_sapphire_ore`
	Fleshification Sapphire Ore	`confluence:fleshification_sapphire_ore`
	Sanctification Sapphire Ore	`confluence:sanctification_sapphire_ore`
	Sapphire Ore	`confluence:sapphire_ore`

Pixelmon 1 item

	Item	Identifier
	Sapphire Ore	`pixelmon:sapphire_ore`

Mods that name it in a recipe

confluence, occultism, oritech

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