c:nuggets/ironA 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:nuggets/iron, forge:nuggets/iron. 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.
No members in this database.
accents, alexscaves, alexsmobs, aquaculture, ars_nouveau, block_factorys_bosses, bloodmagic, cbc_at, cobblemon, cookingforblockheads, create, create_new_age, createbigcannons, createcasing, createdeco, createdieselgenerators, dndecor, enderio, exposure, framedblocks, functionalstorage, goety, immersiveengineering, ironjetpacks, irons_spellbooks, kaleidoscope_cookery, kaleidoscope_tavern, lightmanscurrency, magistuarmory, netmusic, occultism, oritech, petrolpark, pipez, powergrid, quark, rainbowcompound, ramadandelight, sootychimneys, spartanweaponry, superbwarfare, supplementaries, tconstruct, tide
48 in the corpus; the rest are in mods this database does not hold.
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.