goety:dark_altarsA tag in a mod's own namespace: its internal classification, used by its own recipes.
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 | |
|---|---|---|
| Dark Altar | goety:dark_altar | |
| Dark Altar | goety:dark_altar_blackstone | |
| Dark Altar | goety:dark_altar_crypt_stone | |
| Dark Altar | goety:dark_altar_deepslate | |
| Dark Altar | goety:dark_altar_end_stone | |
| Dark Altar | goety:dark_altar_highrock | |
| Dark Altar | goety:dark_altar_marble | |
| Dark Altar | goety:dark_altar_nether_brick | |
| Dark Altar | goety:dark_altar_ominous_stone | |
| Dark Altar | goety:dark_altar_prismarine | |
| Dark Altar | goety:dark_altar_stone |
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.