c:dyes/green

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:dyes/green, forge:dyes/green. 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

	Item	Identifier
	Green Chalk	chalk:green_chalk

Create: Connected 1 item

Ender IO 1 item

	Item	Identifier
	Organic Green Dye	enderio:organic_green_dye

Mods that name it in a recipe

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

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