Mods › c:plates/copper

c:plates/copper

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.

3items in it
3mods with members
20mods using it in a recipe
3spellings merged

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.

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.

Create 1 item

ItemIdentifier
Copper Sheet create:copper_sheet

Immersive Engineering 1 item

ItemIdentifier
Copper Plate immersiveengineering:plate_copper

Superb Warfare 1 item

ItemIdentifier
Copper Plate superbwarfare:copper_plate

Mods that name it in a recipe

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.