confluence:glowing_mushroom_blocksA 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 | |
|---|---|---|
| Glowing Mushroom | confluence:glowing_mushroom | |
| Glowing Mushroom Cattail Block | confluence:glowing_mushroom_cattail_block | |
| Glowing Mushroom Indusium Block | confluence:glowing_mushroom_indusium_block | |
| Glowing Mushroom Moss | confluence:glowing_mushroom_moss | |
| Glowing Mushroom Pileus Block | confluence:glowing_mushroom_pileus_block | |
| Glowing Mushroom Stem Block | confluence:glowing_mushroom_stem_block | |
| Glowing Mushroom Vine | confluence:glowing_mushroom_vine | |
| Mushroom Grass Block | confluence:mushroom_grass_block | |
| Mushroom Path | confluence:mushroom_path |
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.