Mods › c:crops/tomato

`c:crops/tomato`

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.

4items in it

4mods with members

37mods using it in a recipe

2spellings merged

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

[Let's Do] Candlelight 1 item

	Item	Identifier
	Tomato	`candlelight:tomato`

[Let's Do] Farm & Charm 1 item

	Item	Identifier
	Tomato	`farm_and_charm:tomato`

Farmer's Delight 1 item

	Item	Identifier
	Tomato	`farmersdelight:tomato`

Kaleidoscope Cookery 1 item

	Item	Identifier
	Tomato	`kaleidoscope_cookery:tomato`

Mods that name it in a recipe

abnormals_delight, aquaculturedelight, aquamirae_delight, brewinandchewin, casualness_delight, cosmopolitan, createfood, culturaldelights, delightful, delightfulcreators, ends_delight, expandeddelight, farmersdelight, goetydelight, immortalers_delight, jadensnetherexpansiondelight, jellyfishingdelight, kaleidoscope_chinesefood, kaleidoscope_cookery, lendersdelight, miners_delight, moredelight, netherdepthsupgrade, oceanic_delight, oceansdelight, ramadandelight, silentsdelight, someassemblyrequired, spawn, spelunkery, twilightdelight, ubesdelight, undergardendelight, vegandelight, veggiesdelight, vintagedelight

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