Mods › c:ores/uranium

`c:ores/uranium`

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

5mods with members

5mods using it in a recipe

2spellings merged

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

Alex's Caves 1 item

	Item	Identifier
	Radrock Uranium Ore	`alexscaves:radrock_uranium_ore`

Create Nuclear 2 items

	Item	Identifier
	Deepslate Uranium Ore	`createnuclear:deepslate_uranium_ore`
	Uranium Ore	`createnuclear:uranium_ore`

Immersive Engineering 2 items

	Item	Identifier
	Deepslate Uranium Ore	`immersiveengineering:deepslate_ore_uranium`
	Uranium Ore	`immersiveengineering:ore_uranium`

Mekanism 2 items

	Item	Identifier
	Deepslate Uranium Ore	`mekanism:deepslate_uranium_ore`
	Uranium Ore	`mekanism:uranium_ore`

Oritech 1 item

	Item	Identifier
	Deepslate Uranium Ore	`oritech:deepslate_uranium_ore`

Mods that name it in a recipe

create, immersiveengineering, mekanism, occultism, 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.