Mods › c:dyes/blue

c:dyes/blue

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
56mods using it in a recipe
2spellings merged

Written as c:dyes/blue, forge:dyes/blue. 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.

Chalk 1 item

ItemIdentifier
Blue Chalk chalk:blue_chalk

Create: Connected 1 item

ItemIdentifier
Blue Fan Dyeing Catalyst create_connected:blue_fan_dyeing_catalyst

Mods that name it in a recipe

additionallanterns, adorn, alexscaves, aoa3, armourers_workshop, ars_nouveau, biomeswevegone, bits_n_bobs, cluttered, cobblemon, comforts, computercraft, connectedglass, cookingforblockheads, create, create_dd, createfood, divinerpg, dndecor, dndesires, domesticationinnovation, elevatorid, enderio, extendedae, farmersdelight, forbidden_arcanus, icarus, immersiveengineering, industrialforegoing, kaleidoscope_tavern, lightmanscurrency, lrarmor, mekanism, mekanismadditions, numismatics, occultism, pixelmon, pneumaticcraft, quark, refinedstorage, regions_unexplored, securitycraft, sfm, silentgear, sleep_tight, snowyspirit, supplementaries, tconstruct, tide, toms_storage, touhou_little_maid, ultramarine, valhelsia_structures, vintagedelight, waystones

56 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.