The short version
Cooking mixes ingredient experimentation with fixed recipes that remain visible after discovery. The reference will organize every confirmed recipe by machine, ingredients, result, recovery, buff, and game version.
Recipe-table fields
Name, machine, ingredients, processing time, batch behavior, stamina, health, energy, buff, sale value, and verification version.
High-demand answers
The first pass will prioritize all-recipes searches plus cheese, plain bread, iced tea, honey, delicious thresholds, and the most useful early-game recovery foods.
How recipe discovery should be documented
A confirmed row needs the correct machine, exact ingredient names and counts, result, processing time, recovery or buff, sale value, and version. Experiment results should state whether order matters and whether a failed dish consumes the inputs. A screenshot of the discovered entry is stronger evidence than a list copied from an older Early Access spreadsheet.
Cooking for exploration versus profit
Food can solve different problems: immediate health or stamina, a timed buff, a task, a gift, or added sale value. Keep those uses separate when deciding what to cook. An expensive dish is not automatically the best travel food, and processing a scarce quest ingredient for profit can create more backtracking than the money saves.
Why the database is not indexed yet
Searchers need a working recipe list, not a promise of one. Exact version 1.0 inputs and outputs still need a structured capture pass, including cheese, bread, tea, honey, failed dishes, and machine-specific behavior. This page explains the system and verification fields but remains outside the sitemap until the table contains reproducible rows.
Sources and verification
Primary sources are linked beside the claims they support. Community material is used only as a lead or is labeled as community-tested.
- Official Steam store ↗Cooking, farming and crafting feature context.
- Official Steam guides ↗Community recipe leads pending version 1.0 reproduction.