projectvibrantjourneys:hollow_logsA 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 | |
|---|---|---|
| Acacia Hollow Log | projectvibrantjourneys:acacia_hollow_log | |
| Birch Hollow Log | projectvibrantjourneys:birch_hollow_log | |
| Cherry Hollow Log | projectvibrantjourneys:cherry_hollow_log | |
| Dark Oak Hollow Log | projectvibrantjourneys:dark_oak_hollow_log | |
| Jungle Hollow Log | projectvibrantjourneys:jungle_hollow_log | |
| Mangrove Hollow Log | projectvibrantjourneys:mangrove_hollow_log | |
| Oak Hollow Log | projectvibrantjourneys:oak_hollow_log | |
| Spruce Hollow Log | projectvibrantjourneys:spruce_hollow_log |
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.