c:plates/copperA 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:plates/copper, forge:plates/copper, neoforge:plates/copper. 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 | |
|---|---|---|
| Copper Sheet | create:copper_sheet |
| Item | Identifier | |
|---|---|---|
| Copper Plate | immersiveengineering:plate_copper |
| Item | Identifier | |
|---|---|---|
| Copper Plate | superbwarfare:copper_plate |
create, create_dd, create_new_age, create_sa, createaddition, createbigcannons, createdeco, createdieselgenerators, createutilities, design_decor, extendedwrenches, immersiveengineering, petrolpark, pipeorgans, powergrid, sliceanddice, superbwarfare, tconstruct, tfmg
20 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.