c:ores/zincA 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/zinc, forge:ores/zinc. 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 | |
|---|---|---|
| Deepslate Zinc Ore | create:deepslate_zinc_ore | |
| Zinc Ore | create:zinc_ore |
| Item | Identifier | |
|---|---|---|
| Andesite Zinc Ore | spelunkery:andesite_zinc_ore | |
| Diorite Zinc Ore | spelunkery:diorite_zinc_ore | |
| Granite Zinc Ore | spelunkery:granite_zinc_ore | |
| Tuff Zinc Ore | spelunkery:tuff_zinc_ore |
alloy_forgery, create, immersiveengineering, 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.