c:gems/jade
A 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:gems/jade, forge:gems/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.
Members
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.
AoA3 1 item
| Item | Identifier | |
|---|---|---|
 |
Jade | aoa3:jade |
Confluence 1 item
| Item | Identifier | |
|---|---|---|
 |
Jade | confluence:jade |
Goety 1 item
| Item | Identifier | |
|---|---|---|
 |
Jade | goety:jade |
Samurai Dynasty 1 item
| Item | Identifier | |
|---|---|---|
 |
Jade | samurai_dynasty:jade |
Sully's Mod 1 item
| Item | Identifier | |
|---|---|---|
 |
Jade | sullysmod:jade |
Mods that name it in a recipe
aoa3, confluence, goety, samurai_dynasty
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.