The official Steam page lists Cooking as a DragonSword : Awakening feature and recent independent pages show clear player interest in recipes, ingredients and preparation. This guide focuses on the decision behind a meal and the record needed to keep a progression recommendation accurate. It does not publish a fixed recipe table because the reviewed official material does not provide one and third-party lists need current in-game verification.
Identify the reason for cooking
Start with the encounter or route that needs help. Are you losing health, failing to control an enemy, running out of time, or preparing for a Dungeon? Read the current meal result before choosing a recipe. A meal is useful when its effect addresses the failure. It is not automatically useful because it has a rare ingredient, a long name or a recommendation on a ranking page.
Write the goal in one sentence: “I am testing this meal because the second phase defeats the party.” After the run, write whether survival, damage, control or clarity improved. If nothing changed, check whether the effect was active, expired, limited to one hero or obscured by another system. A short test prevents a player from farming a resource for a benefit that does not apply.
Record a recipe from the live interface
Use a five-field note: displayed name, ingredients, preparation action, result text and verification date. Add the number of portions or duration only when the game shows it. Copy the exact wording for an unusual status or stat. If the game adds a cookbook entry, record whether discovering the recipe changes the collection state. Do not translate a descriptive effect into a precise stat unless the interface gives the number.
When an ingredient comes from the world, save the location and the route separately. A location may be a one-time pickup, a repeating node, a creature drop or a shop stock. The Store page confirms Orbis as an open world but does not verify a complete ingredient map. Use the World guide for exploration evidence and update the cooking page only after the route reproduces.
Keep progression investments reversible
Cooking is one part of progression, alongside heroes, skills, Familiars, equipment and story access. Before spending a scarce ingredient or upgrade material, check the preview and the other systems that use it. If the resource is shared, invest enough to learn the current effect and keep a reserve for the hero or route that has already solved a problem twice.
Do not spread small quantities across every system. Pick one combat problem and one progression target. Test the meal or upgrade, repeat the encounter, and continue only if the result is clear. If the result is mixed, the failure may come from switching, positioning or the enemy’s resistance rather than the meal. Link to Combat instead of treating every loss as a crafting problem.
Compare meals fairly
Use the same hero, party, route, difficulty and preparation when comparing two meals. Change one recipe and keep the encounter timing similar. Record which effect was visible and when it ended. If one meal seems stronger because the enemy used a different pattern, repeat the test before calling it better.
Public guides may list methods such as grilling, boiling or slicing, but this audit does not promote those names as official mechanics without a current in-game confirmation. Use whatever the live UI calls the action. A guide should preserve regional or translated labels carefully so a reader can find the matching menu.
Progression milestones
Use story progress as the first milestone because it reveals which systems the game expects you to learn. Use a repeated encounter as the second because it gives you a stable test. Use a completed upgrade as the third because it shows whether the resource investment solved a real problem. Only then decide whether a long ingredient route or a new Familiar is worth prioritizing.
Keep a dated change note when a patch or Steam News post alters a meal, material or achievement. The public version label was not found in the reviewed Store page, so do not attach a made-up version to a recipe. If a page gives a precise cost, link the source and say whether the value came from the current interface or a working source.
Checklist for a useful meal page
- State the base-game and Windows scope.
- Name the encounter or route the meal is meant to support.
- Copy the current ingredient and result text.
- Say whether the effect is personal or party-wide only if shown.
- Record the date, public build label if available and source.
- Test once without the meal and once with it when safe.
- Mark a community recipe as working source until reproduced.
Is every recipe required?
The official page confirms Cooking but not mandatory recipes. Follow the current objective and result text rather than farming a complete list first.
Should I trust a list of 73 meals?
Treat a precise list as a working lead. Verify the count, names, ingredients and effects in the current game before publishing or investing.
How does cooking relate to heroes?
Test a meal with the hero and encounter that need it. Do not assume a general food effect replaces a party or skill decision.