c:storage_blocks/jadeA 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:storage_blocks/jade, forge:storage_blocks/jade. 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 | |
|---|---|---|
| Block of Jade | aoa3:jade_block |
| Item | Identifier | |
|---|---|---|
| Jade Block | confluence:jade_block |
| Item | Identifier | |
|---|---|---|
| Block of Jade | goety:jade_block |
| Item | Identifier | |
|---|---|---|
| Block of Jade | samurai_dynasty:jade_block |
aoa3, confluence, goety
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.