How Recipes was built

Raw game files read

• recipes/grid/*.json
• recipes/smithing/*.json
• recipes/clayforming/*.json
• recipes/knapping/*.json
• recipes/alloy/*.json
• recipes/barrel/*.json
• recipes/cooking/*.json

Processing

Every recipe file under the 7 category directories above is read and normalized into one common shape (ingredients, output, category). Grid recipes keep their shaped-pattern slot layout; smithing/clayforming/knapping recipes keep their voxel pattern (rows of #/_ per layer, used by the item page's layer preview); alloy/barrel/ cooking recipes keep their ratio-range ingredients (minratio/maxratio). Ingredient/output codes with an unresolved * wildcard or {placeholder} are expanded against the recipe's own allowedVariants (or the matching block/item file's variant groups) wherever that's resolvable, rather than left as a literal template string.

Recipes with no name of their own in the game data (alloy, barrel, cooking, knapping, smithing, clayforming never have one) are titled after their output item and labeled "(Item Recipe)" on this wiki, so it's clear that's a derived title, not a second real name for the item.

Pipeline code

• apps/vs-wiki/src/ingest/models/recipes.ts