DragonSword : Awakening Systems

DragonSword : Awakening has more to manage than a single combat stat. The official Steam page names Cooking, Familiars, Active Skills, Signal Skills, Dungeons, 19 Heroes and 59 Steam Achievements. This hub connects those systems to player decisions while refusing to turn incomplete public lists into fixed facts. Use it to decide what to inspect, what to record and when a resource is worth spending.

A system is useful when it solves a problem

Before opening a system guide, name the problem. If you cannot survive, start with Combat and party tools. If you cannot reach a route, start with World and Familiars. If an encounter is close but inconsistent, inspect Cooking, equipment or the skill descriptions. If you want completion, inspect the Steam achievement list and record the exact wording. This prevents a player from spending resources simply because a menu is available.

A system page should show its scope, input, output, cost and evidence date. “Input” is the material, hero, action or route. “Output” is the effect the game displays. “Cost” includes resources and opportunity cost. “Evidence date” matters because a launch guide may outlive a balance or reward change. Keep those fields separate so the page can be updated without rewriting its advice.

Cooking as a preparation decision

Cooking is an official feature and a clear search opportunity. The safest first question is not “what is the best meal?” It is “what does this meal change for the encounter I am about to run?” Read the current result text, duration, target scope and ingredient cost. If the effect improves survival, control or damage, connect it to that specific failure. Do not assume that a meal’s rarity or name proves its value.

The Cooking & Progression guide provides a record format. Use it for recipes you can reproduce, and mark third-party recipe tables as working sources until the ingredients and result text match the current interface. A large recipe count or a precise farming route should never be repeated only because several sites use the same number.

Progression without a blind spending loop

Progression decisions should follow a tested goal. Pick one hero or party problem, inspect the next upgrade preview, and check whether the material is shared with a later system. Spend enough to test the improvement, then repeat the same encounter. If the result is clear, continue. If not, record what changed and test a different variable.

Keep separate notes for hero growth, equipment, Familiars, Cooking and story unlocks. A guide that calls every new screen “progression” becomes impossible to search. The right page should answer which menu owns the action and which other systems can change the result. This is especially important while the public version label is not stated on the reviewed Store page.

Steam achievements are a checklist, not a rumor

Steam’s Store page shows 59 Steam Achievements. That is a stable starting fact for a completion page, but it does not reveal the full condition list in the store description. Open the Steam achievement panel for the exact wording and record whether an achievement is story, exploration, combat, collection or system-related. Keep the text tied to AppID 4570720 so a similarly named product is not mixed in.

Do not claim that an achievement is missable, hidden, bugged or easiest with a specific hero without a current test or official post. If a community guide supplies a route, record its date and verify the condition from Steam. A completion guide should make uncertainty visible because a wrong claim can make players repeat a long route unnecessarily.

Connect systems instead of duplicating them

Cooking can support a combat test. Familiars can change exploration. Heroes and Signal Skills can change how a Dungeon is approached. Achievements can reveal a completion goal but do not automatically explain the fastest route. Link to the owner page for each decision and keep this hub focused on relationships and resource safety.

When a system interacts with another, state what is proven and what is only a hypothesis. For example, “the Store page lists Cooking and Dungeons” is official. “This recipe is required for the first Dungeon boss” needs a dated in-game or official source. That sentence-level distinction is more useful to players than a broad confidence badge with no explanation.

What to do after an update

Check the Steam News index, the current Store text and the in-game panel. Compare the public version label if one appears, changed recipes, achievement wording, hero skill text and reward routes. Update the narrowest page first. If an update changes a system relationship, add a dated note rather than silently changing a permanent claim.

Keep old values out of evergreen headings. A title such as “best recipe” can remain stable; a paragraph that says a recipe always gives a fixed effect may not. Use a scope line on every page: base game, full release, Windows PC, audit date and public version status. This makes the guide safer for future localization.

Systems FAQ

How many Steam achievements are confirmed?

The official Store page shows 59 Steam Achievements. Individual conditions must be checked in Steam.

Is Cooking mandatory?

Cooking is an official feature. The public page does not prove which meals are mandatory for each encounter, so follow the current result and requirement text.

Should I farm ingredients immediately?

Only after naming the encounter or upgrade the ingredient will support. Record the current route and result before committing to a long farm.

Where do combat systems belong?

Use this hub for system relationships and resources; use Combat for switching, skills and Status Ailments.