c:meshesA 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.
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 | |
|---|---|---|
| Advanced Brass Mesh | createsifter:advanced_brass_mesh | |
| Advanced Custom Mesh | createsifter:advanced_custom_mesh | |
| Advanced Sturdy Mesh | createsifter:advanced_sturdy_mesh | |
| Andesite Mesh | createsifter:andesite_mesh | |
| Brass Mesh | createsifter:brass_mesh | |
| Custom Mesh | createsifter:custom_mesh | |
| String Mesh | createsifter:string_mesh | |
| Sturdy Mesh | createsifter:sturdy_mesh | |
| Zinc Mesh | createsifter:zinc_mesh |
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.