Combat in DragonSword : Awakening should be read as a sequence of decisions, not as a single damage number. The official Steam description highlights Status Ailments, Active Skills, Signal Skills and switching between heroes. That wording suggests a party-based action loop in which the timing of a character’s tool matters as much as the character’s raw strength. This hub explains how to study that loop without publishing invented cooldowns, multipliers or a permanent tier list.
Read a fight as four phases
Start with recognition. Before attacking, identify the enemy’s approach, range, telegraph and recovery window. The first run through an encounter is data collection. Notice what makes you move, what interrupts your plan and whether a status icon or stagger-like response appears. Do not burn every skill while you are still learning the attack pattern.
Next comes setup. Choose the hero whose current tool answers the immediate problem and place that hero in a position where the next switch is possible. “Setup” does not mean a fixed rotation; it means creating a clear reason for the next action. If you cannot explain why you are switching, wait for the interface or enemy behavior to give you a reason.
The third phase is conversion. An Active Skill or Signal Skill may create a short opportunity, and a Status Ailment may change the enemy’s behavior. Use the visible result to decide whether to continue, switch or retreat. If a guide claims that one ailment always beats another, check whether that claim applies to the current enemy and version.
The last phase is recovery. After the opportunity closes, return to a stable position, check your party state and decide whether the next exchange is safe. Many failed attempts come from treating a successful opening as permission to continue attacking through a new telegraph. A controlled reset is part of the combat plan, not wasted time.
Switching is a decision, not a button to spam
The store page explicitly mentions switching. A useful first experiment is to keep the same three heroes and change only the moment of the swap. Test an early switch before contact, a reactive switch after a telegraph, and a conversion switch after a status or skill effect appears. Record what the interface says and how long the action leaves you exposed.
When the team has a clear role split, switching becomes easier to evaluate. One hero may be comfortable starting an exchange, another may provide control, and a third may supply a different damage or status tool. The game’s public page does not provide a full role table, so use the current skills and combat feel. Do not infer a hero’s complete identity from their name or a single screenshot.
Active Skills and Signal Skills
Active Skills are named on the official page, but a public universal list of effects was not available for this audit. Read the skill text at the current level, note its target and timing, and test it in a low-risk fight before spending it during a boss attempt. A short animation, a movement effect or a status icon may matter more than the headline damage.
Signal Skills are also named officially. Treat them as an invitation to observe a trigger, not as proof of a specific combo recipe. Ask three questions: what event makes the signal available, which hero is active when it appears, and what changes on the target or party after use? If the game exposes a cooldown, resource or prompt, copy the exact wording into your session log.
Status Ailments without a made-up chart
Status Ailments are one of the strongest public search signals around this game. Independent guides discuss several possible ailment names and chain behavior, but their tables are not an official source. The safe approach is to record the exact icon, label, duration, visible target change and whether another action follows it. A status is worth using when you can explain what it changes in the current encounter.
Compare an ailment against three outcomes: control, vulnerability or damage over time. Those categories are deliberately broad because the official store page does not publish a numerical glossary. If an enemy resists or shortens an effect, write that as an observation for that encounter rather than a universal rule. If a boss appears immune, check again after a later phase or official update before declaring permanent immunity.
Build a three-hero test team
The store page confirms 19 Heroes but does not state a complete public team-building formula. Start with a small test team that lets you observe three different decisions: how you begin an encounter, how you respond to a threatening pattern and how you convert an opening. Avoid choosing three heroes because a community table labels them with the same tier. Choose three because their current skill text gives you three different experiments.
Run the same encounter twice with the same team. On the first attempt, focus on survival and recognition. On the second, test one planned switch or skill. If the result improves, keep the change. If not, write down whether the problem was timing, positioning, resource use or an incorrect assumption about the status. This creates a build note that survives balance changes better than a copied rotation.
Combat preparation and Cooking
Cooking is an official system keyword and may become relevant to preparation, but this audit did not verify the full recipe book or effect values. Before a difficult fight, read the current meal result, duration and scope. Note whether it affects one hero or the party and whether the resource cost is replaceable. A food effect is valuable only when it addresses the failure you identified; using it because it is available does not create a plan.
Familiars and equipment should be tested in the same way. Keep the combat variable small enough that you can attribute the result. If the menu has an unfamiliar term, follow the Systems or World hub, take a screenshot for your own records, and wait for a source with a clear date before making a long-term recommendation.
Combat troubleshooting
If you lose before using a skill, study recognition and positioning. If you survive but cannot create an opening, study switching and status timing. If an opening appears but the target does not fall, compare the hero’s current level, skill description and preparation. If a party member repeatedly becomes unusable, check the enemy’s visible effect and whether another hero can answer it. These branches are more useful than “farm more levels” because each points to a different fix.
Combat FAQ
Is there a universal rotation?
Not one that can be verified from the official page. Use the current skill text, the enemy behavior and a recorded test instead of copying a fixed sequence.
Are all Status Ailments confirmed by Steam?
The existence of Status Ailments is confirmed. A complete list and every interaction are not confirmed by the store listing.
How many heroes should I bring?
The public page describes hero switching and confirms 19 heroes. Use the party size and switching rules shown in your current game; do not infer an undocumented team limit from a third-party table.
Recommended guides
Choose the guide that matches what you want to do next.
All Combat guides
1 focused guides with steps, checks, and current caveats.