Cooking in REKA. One good meal.

Name the meal’s job first

A meal can complete a request, make a useful offering or simply belong in the home you are creating. Decide which role you mean before gathering a large batch. A particular villager’s order may care about flavour and quantity, while a different task names a specific dish. Those are different checks, even when the same ingredients are close at hand.

Write the intended result and the person or purpose beside it. That small note prevents an ingredient from being spent on an attractive experiment when it was the final component of the meal you promised. Experimentation is part of the pleasure; make its opportunity cost visible.

Treat fuel and ingredients as separate supplies

The community cooking reference describes an oven supplied with fuel and three ingredient positions. Ingredient order does not determine its listed combinations. Before troubleshooting a recipe, check that the cooking setup is ready and that the three items are the ones the recipe actually calls for.

Wood is also a construction material. A decorating session and an evening of cooking therefore draw on the same broad reserve. Keep the next use in mind instead of treating all wood as surplus building stock. We recommend preparing a small working batch before expanding the kitchen or converting every foraged ingredient into food.

Use two small references to learn the pattern

The following are limited community-wiki references, not an exhaustive 1.0 recipe database. Confirm the exact ingredient labels and result in your game before committing scarce supplies.

Use a successful small recipe to understand what you are spending and receiving. Do not extrapolate a complete recipe rule from two examples. Similar-looking ingredients, broad category labels and a dish’s name do not establish every valid substitution.

Read the item, not only the picture

The reviewed pages use broad labels such as berries and honey alongside item names such as Honeycomb and Raspberries. That is a reason to check the current book and inventory rather than assume that every page uses identical terminology. Flour also has its own supply route; the ingredient reference lists buying it from the Merchant instead of treating harvested grain as flour automatically.

For gathering, record what is missing rather than everything you could collect. A tree with honeycomb, a patch of mushrooms and a merchant purchase belong to different stops. Combining those stops into a short purposeful outing makes the return to the oven easier to assess.

Match the villager’s whole request

The recurring meal request described by the village-help reference distinguishes sweet or savoury food and a small, medium or large meal. Its listed quantities are one, two or three food items respectively. Read the actual dialogue before offering the dish: a suitable flavour alone does not necessarily satisfy the quantity.

Our practical habit is to write both parts together, such as “savoury, two portions,” in your own notes. Then check the cooked items before returning. We do not promise a fixed payment or a universal reward table; the purpose is to make the request legible and avoid spending the wrong result.

Keep useful raw ingredients available

Honeycomb’s item reference lists uses beyond the oven, including candle making and herbal preparation. Processing every available unit into a meal can therefore displace another plan. Keep a small reserve when you already know a different use is coming, and mark optional experiments separately from requested food.

Finish a kitchen session with a clear next need: fuel, a purchased ingredient or one foraging stop. The field journal can hold that note and a preparation checklist, but it never reads your inventory or certifies a recipe. The current in-game result remains the final check before you spend more.

A FEW SMALL ANSWERS

Questions by the hearth.