Mods › c:ores/platinum

`c:ores/platinum`

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.

10items in it

4mods with members

6mods using it in a recipe

2spellings merged

Written as c:ores/platinum, forge:ores/platinum. 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 Platinum Ore	`confluence:corruption_platinum_ore`
	Deepslate Platinum Ore	`confluence:deepslate_platinum_ore`
	Fleshification Platinum Ore	`confluence:fleshification_platinum_ore`
	Platinum Ore	`confluence:platinum_ore`
	Sanctification Platinum Ore	`confluence:sanctification_platinum_ore`

Create Propulsion: Simulated 2 items

	Item	Identifier
	Deepslate Platinum Ore	`createpropulsion:deepslate_platinum_ore`
	Platinum Ore	`createpropulsion:platinum_ore`

Oritech 2 items

	Item	Identifier
	Deepslate Platinum Ore	`oritech:deepslate_platinum_ore`
	Endstone Platinum Ore	`oritech:endstone_platinum_ore`

Pixelmon 1 item

	Item	Identifier
	Platinum Ore	`pixelmon:platinum_ore`

Mods that name it in a recipe

alloy_forgery, create, immersiveengineering, occultism, oritech, tconstruct

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.