Fields of Mistria recipes
The cooking lookup is organized around the decision a player actually makes: which food uses these ingredients, what skill level does it require, how long does it take, and what value or stamina does the captured record show? The wide record set makes ingredient discovery fast, while the visible source boundary keeps recipe certainty proportional to the capture. Cooking remains bound to the v1.0.2 capture.
Steam 1.0 release ·Cooking source boundary
Start this cooking check with the displayed count, then keep the chosen field and source link together when the answer affects a longer route.
Cooking lookup
188 records shown · v1.0.2
188 records shown · Name A–Z
No records match this lookup.
The cooking lookup begins with the question a player can answer: a dish name, an ingredient, a food category, a skill level, or a captured value. Search across 188 food records, then filter or sort by ingredients, skill level, craft time, stamina, or sell value. Ingredient strings remain in their captured form so quantities and notes are not lost during display. A text match shows that the row contains the term; it does not prove that the ingredient is replaceable or that every preparation step is present. Craft time, stamina, and value are independent comparison fields rather than components of an automatic best-recipe score. A high-value dish can require scarce ingredients, and a stamina field does not describe the player’s whole day. When a recipe source or quantity is unclear, open the linked page instead of borrowing a pattern from another dish. The lookup narrows a large recipe family to the rows worth reading, while leaving substitutions, inventory state, and acquisition planning outside the sealed evidence.
What this lookup covers
Each row keeps ingredients, food category, subcategory, skill level, craft time, stamina, health, sell value, recipe source, tags, page update marker, and revision id where available. Ingredient text is displayed as captured, including quantities and source notes; the page does not infer substitutions or calculate profit after ingredient cost. Search covers ingredients as well as names, and numeric sorting changes the order using a real captured field. This separation matters because a recipe record can show a stamina field without establishing how a player should spend an entire day or which ingredient is easiest to obtain. The row is a compact recipe record, not a replacement for the full cooking page. Ingredient strings may include quantities or notes that need their original formatting, and a missing field cannot be safely reconstructed from another dish. Search therefore remains broad while the displayed values stay literal. This section keeps the 188 cooking records inside the v1.0.2 capture separate from later research.
Food rows preserve names, ingredients, category and subcategory, skill level, craft time, stamina, health, captured sell value, recipe source, tags, page update markers, ids, and revisions where the public capture exposed them. The interface does not reconstruct a missing ingredient from a similar recipe or infer a cooking unlock from the order of the list. Search is broad enough to find an ingredient inside a captured string, while the selected field filter distinguishes ingredients from category, level, time, or value. Numeric sorting reads the stored value only and does not subtract ingredient cost. The cooking route connects to farming and items because crops and materials can appear in the same daily loop, but those neighboring records do not create a recipe relationship unless the cooking source states it. A not-captured cell is therefore a boundary, not a zero or a free requirement. Use the source page for full preparation context whenever the compact row lacks a detail that affects spending or progression.
Version boundary
Search an ingredient to see every recorded dish that mentions it, then filter by food category or sort by craft time, stamina, or value. Use the source page when a recipe source needs more context. The v1.0.2 boundary is explicit because food records and official release notes answer different questions and should not be merged into one synthetic recipe system. Compare two dishes by the fields shown, then verify any missing ingredient detail in the linked capture instead of assuming a substitution or an unrecorded quantity. Begin with the ingredient or dish name, then use category and skill fields to reduce the list. Craft time, stamina, and sell value are useful comparison columns, but they answer different questions; read them separately before deciding what to cook for a particular outing or sale. Use the cooking result as a documented next step, then revisit the linked source if a later version changes the field.
The recipe collection is tied to the v1.0.2 capture shown in the masthead. That boundary matters because a patch can change a recipe, ingredient requirement, value, unlock, or source description. Community page revisions record the structured cooking fields, while official update posts record dated release claims; both remain separately linked. For a current choice, search the ingredient or dish, compare only the fields that are present, and open the source before substituting an item or assuming an unlock condition. The almanac does not read the player’s inventory, calculate net profit, or recommend a universal stamina meal. Local sorting and filtering alter only the displayed order and can be repeated without changing the source data. When a newer capture arrives, stable ids and revision markers allow the old and new rows to be compared. This provides a clear audit trail for a recipe decision instead of silently rewriting the field values that supported an earlier plan. Record the ingredient string exactly when comparing two revisions. A shortened shopping note can be convenient, but it should not be mistaken for the sealed recipe field that the source actually exposed. Keep skill level and recipe source beside the ingredient list when the cooking decision affects progression. Those fields answer different questions and neither can be reconstructed safely from the dish name alone.