Mods › c:ores/jade

`c:ores/jade`

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.

15items in it

5mods with members

1mods using it in a recipe

2spellings merged

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

	Item	Identifier
	Deepslate Jade Ore	`aoa3:deepslate_jade_ore`
	Jade Ore	`aoa3:jade_ore`

Confluence 5 items

	Item	Identifier
	Corruption Jade Ore	`confluence:corruption_jade_ore`
	Deepslate Jade Ore	`confluence:deepslate_jade_ore`
	Fleshification Jade Ore	`confluence:fleshification_jade_ore`
	Jade Ore	`confluence:jade_ore`
	Sanctification Jade Ore	`confluence:sanctification_jade_ore`

Samurai Dynasty 2 items

	Item	Identifier
	Deepslate Jade Ore	`samurai_dynasty:deepslate_jade_ore`
	Jade Ore	`samurai_dynasty:jade_ore`

Spelunkery 4 items

	Item	Identifier
	Andesite Jade Ore	`spelunkery:andesite_jade_ore`
	Diorite Jade Ore	`spelunkery:diorite_jade_ore`
	Granite Jade Ore	`spelunkery:granite_jade_ore`
	Tuff Jade Ore	`spelunkery:tuff_jade_ore`

Sully's Mod 2 items

	Item	Identifier
	Deepslate Jade Ore	`sullysmod:deepslate_jade_ore`
	Jade Ore	`sullysmod:jade_ore`

Mods that name it in a recipe

confluence

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.