Pantrywork

# 🍞 One cheese. Every recipe.

Farmer's Delight has cheese. Croptopia has cheese. Pam's has cheese. **None of them are the
same cheese** — three mods, three incompatible tag dialects, none referencing the others. So the
recipe that wants cheese takes exactly one of them, and your pack quietly has three parallel
food economies that never touch.

Pantrywork fixes that. It is pure data: a tag layer that bridges those dialects into the official
NeoForge / Farmer's Delight `c:foods/*` convention, then adds a second layer describing what an
ingredient *does*. No blocks, no items, no gameplay changes. Just recipes that finally work.

## 🏷️ Two layers

**Identity** — `c:foods/*`. Extends the built-in convention and translates the others into it.
Croptopia's plural dialect (`c:cheeses`) and Pam's concatenated dialect (`c:rawpork`) both resolve
to canonical names (`c:foods/cheese`, `c:foods/raw_pork`). Bridges run in **both** directions:
24 dialect tags also gain the other mods' equivalent items, so Croptopia's and Pam's *own* recipes
start accepting foreign ingredients too.

**Role** — `pantrywork:food_component/{protein, starch, dairy, garnish, liquid_base, sweetener}`.
Tags-of-tags over the identity layer, describing function rather than identity. Author one recipe
against `#pantrywork:food_component/protein` and it accepts vanilla steak, Farmer's Delight bacon,
and anything a future mod tags — without you shipping an update.

## 🔌 Zero hard dependencies

Every cross-mod reference is `required: false`. Install Pantrywork with all the supported mods, one
of them, or none — it loads clean either way and simply bridges whatever it finds. There is no
"you must also install…" line, because there isn't one.

**Server-side only** — drop it on the server and every player benefits, no client install needed.
Works in singleplayer too (your game runs an internal server; just install it normally).

Supported: **Farmer's Delight** (incl. Refabricated on Fabric) · **Croptopia** ·
**Pam's HarvestCraft 2 Food Core** · **Ocean's Delight** (full identity module) ·
**End's Delight** (parent joins) · **Origins** (carnivore/vegetarian diet tags).

## 🧑‍🍳 For pack makers

Stop writing one recipe per food mod. Target a role tag and the recipe covers every mod your
players have installed, plus the ones they install later.

## 🛠️ For mod authors

`PantryworkTagKeys` exposes every tag as a constant, so you can reference the taxonomy without
hardcoding strings or taking a dependency on the mods being bridged.

## ✅ Verified, not assumed

Tested live on NeoForge 1.21.1 with Farmer's Delight 1.3.2, Croptopia 4.2.4, and Pam's HC2 Food
Core 1.0.4 loaded together — including a single crafting recipe that consumes vanilla bread,
Farmer's Delight bacon, and Croptopia lettuce at once. Automated GameTests cover role tags,
cross-mod identity, reverse bridges, and recipe resolution through `RecipeManager`.

🍞 One cheese every recipe.

Farmer's Delight has cheese. Croptopia has cheese. Pam's has cheese. None of them are the same cheese — three mods, three incompatible tag dialects, none referencing the others. So the recipe that wants cheese takes exactly one of them, and your pack quietly has three parallel food economies that never touch.

Pantrywork fixes that. It is pure data: a tag layer that bridges those dialects into the official NeoForge / Farmer's Delight c:foods/* convention, then adds a second layer describing what an ingredient does. No blocks, no items, no gameplay changes. Just recipes that finally work.

🏷️ Two layers

Identity — c:foods/*. Extends the built-in convention and translates the others into it. Croptopia's plural dialect (c:cheeses) and Pam's concatenated dialect (c:rawpork) both resolve to canonical names (c:foods/cheese, c:foods/raw_pork). Bridges run in both directions: 24 dialect tags also gain the other mods' equivalent items, so Croptopia's and Pam's own recipes start accepting foreign ingredients too.

Role — pantrywork:food_component/{protein, starch, dairy, garnish, liquid_base, sweetener}. Tags-of-tags over the identity layer, describing function rather than identity. Author one recipe against #pantrywork:food_component/protein and it accepts vanilla steak, Farmer's Delight bacon, and anything a future mod tags — without you shipping an update.

🔌 Zero hard dependencies

Every cross-mod reference is required: false. Install Pantrywork with all the supported mods, one of them, or none — it loads clean either way and simply bridges whatever it finds. There is no "you must also install…" line, because there isn't one.

Supported: Farmer's Delight (incl. Refabricated on Fabric) · Croptopia · Pam's HarvestCraft 2 Food Core · Ocean's Delight (full identity module) · End's Delight (parent joins) · Origins (carnivore/vegetarian diet tags).

🧑‍🍳 For pack makers

Stop writing one recipe per food mod. Target a role tag and the recipe covers every mod your players have installed, plus the ones they install later.

🛠️ For mod authors

PantryworkTagKeys exposes every tag as a constant, so you can reference the taxonomy without hardcoding strings or taking a dependency on the mods being bridged.

✅ Verified, not assumed

Tested live on NeoForge 1.21.1 with Farmer's Delight 1.3.2, Croptopia 4.2.4, and Pam's HC2 Food Core 1.0.4 loaded together — including a single crafting recipe that consumes vanilla bread, Farmer's Delight bacon, and Croptopia lettuce at once. Automated GameTests cover role tags, cross-mod identity, reverse bridges, and recipe resolution through RecipeManager.