c:ores/tungstenA 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.
Written as c:ores/tungsten, forge:ores/tungsten. 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.
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.
| Item | Identifier | |
|---|---|---|
| Corruption Tungsten Ore | confluence:corruption_tungsten_ore | |
| Deepslate Tungsten Ore | confluence:deepslate_tungsten_ore | |
| Fleshification Tungsten Ore | confluence:fleshification_tungsten_ore | |
| Sanctification Tungsten Ore | confluence:sanctification_tungsten_ore | |
| Tungsten Ore | confluence:tungsten_ore |
| Item | Identifier | |
|---|---|---|
| Deepslate Scheelite Ore | superbwarfare:deepslate_scheelite_ore | |
| Scheelite Ore | superbwarfare:scheelite_ore |
alloy_forgery, 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.