c:lead_oresA 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:lead_ores, forge:lead_ores. 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 Lead Ore | modern_industrialization:deepslate_lead_ore | |
| Lead Ore | modern_industrialization:lead_ore |
| Item | Identifier | |
|---|---|---|
| Deepslate Lead Ore | palladium:deepslate_lead_ore | |
| Lead Ore | palladium:lead_ore |
| Item | Identifier | |
|---|---|---|
| Andesite Lead Ore | spelunkery:andesite_lead_ore | |
| Diorite Lead Ore | spelunkery:diorite_lead_ore | |
| Granite Lead Ore | spelunkery:granite_lead_ore | |
| Tuff Lead Ore | spelunkery:tuff_lead_ore |
None in the corpus.
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.