c:plates/iron
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.
Written as c:plates/iron, forge:plates/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.
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.
Ad Astra 1 item
| Item | Identifier | |
|---|---|---|
 |
Iron Plate | ad_astra:iron_plate |
Create 1 item
| Item | Identifier | |
|---|---|---|
 |
Iron Sheet | create:iron_sheet |
Immersive Engineering 1 item
| Item | Identifier | |
|---|---|---|
| Iron Plate | immersiveengineering:plate_iron |
Mods that name it in a recipe
cbc_at, create, create_bic_bit, create_dd, create_new_age, create_radar, createaddition, createbigcannons, createcasing, createdeco, createdieselgenerators, createrailwaysnavigator, design_decor, dndecor, dndesires, escalated, extended_industrialization, immersiveengineering, numismatics, petrolsparts, pipeorgans, powergrid, tconstruct, tfmg
25 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.