c:tools/shieldsA 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:tools/shields, forge:tools/shields. 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 | |
|---|---|---|
| Enchanter's Shield | ars_nouveau:enchanters_shield |
| Item | Identifier | |
|---|---|---|
| The Thorn | biomancy:thorn_shield |
| Item | Identifier | |
|---|---|---|
| Enderite Shield | enderitemod:enderite_shield |
| Item | Identifier | |
|---|---|---|
| Jade Shield | sullysmod:jade_shield |
| Item | Identifier | |
|---|---|---|
| Battlesign | tconstruct:battlesign | |
| Plate Shield | tconstruct:plate_shield | |
| Traveler's Shield | tconstruct:travelers_shield |
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.