DragonSword: Awakening Co-op Guide: Hunts, Raids, and Recovery

Co-op is for selected boss activities, not the whole adventure

DragonSword: Awakening does have online co-op, but it is a focused boss-play option rather than shared story or open-world exploration. Set the encounter first, then form the lobby around it. That expectation prevents the most common false start: trying to invite a friend while roaming Orbis or midway through a story objective.

Use co-op to add a second set of Break pressure, safer rotations, and another player who can keep attacking while the boss turns. It does not replace the character growth required by the selected tier. Each player should still arrive with a working three-hero team, recovery plan, and an understanding of the target's large attacks.

Before you queueBuild the team you will bringCheck status handoffs and Signal Skills before a Hunt or Raid instead of deciding them in the lobby.→

Pick the activity by the material and the group size

For a Hunt, first confirm the boss and tier contain the material your character actually needs. For a Raid, first confirm that the group can preserve recovery and a Break-to-Signal sequence for the final phase. A higher displayed tier is not automatically the better farm if it produces wipes or slow, inconsistent clears.

Use a short lobby checklist

1. Match the game version. If a patch has just arrived, let every player finish updating before recreating the room.
2. Agree on the encounter and tier. Say the boss, difficulty, and material goal out loud; this prevents a successful clear that gives the wrong reward pool.
3. Assign a host with the steadier connection. This is a practical precaution, not a guarantee; keep the party geographically sensible where possible.
4. Check everyone is ready before launch. Update 1.0.9 later fixed a Raid-start issue involving unreadied members, so treat the ready check as a real gate.
5. Separate your initial positions. Do not stack on the same side of a large target. One player can hold Super Armor pressure while another avoids the next sweep.

Update 1.0.7 added Quick Entry and a lobby-search-range setting for multiplayer content. It also explicitly said the accompanying Retry feature was delayed at that point. Use Quick Entry to reduce setup friction, but do not plan a farm route around an assumed in-lobby retry button.

What changed after a wipe or a new dungeon entry

Update 1.0.7 changed the recovery baseline: entering a dungeon and recovering after a wipe now starts all characters revived and at 100% HP. That removes the old reason to abandon a learning attempt solely because the roster entered weakened. It does not change the boss pattern, timer, difficulty requirement, or the value of food and defensive preparation during the run.

After a wipe, name one concrete reason before going back in: missed telegraph, spent stamina, unplanned Signal swap, insufficient Break damage, or a connection problem. Change one of those variables, then retry the encounter. Repeating the same first thirty seconds with the same plan only turns recovery into another failed clear.

Recover from the failure that actually happened

• A guest cannot join: confirm the activity is co-op eligible, recreate the lobby after both clients finish patching, and verify the room method or code before changing builds.
• The whole group dies to one sweep: start on different flanks and reserve one dodge; the player not targeted should pressure Break rather than crowd the attack line.
• Raid phase three collapses: stop spending every long cooldown at the end of phase two. Carry one recovery option and the cleanest Signal sequence through the transition.
• The group clears but progress feels wrong: check the chosen Hunt/Raid tier and its preview before repeating. Co-op cannot correct a mismatched reward route.
• The lobby is unstable: pause background downloads, let the host recreate the room, and try again with a simpler party setup before treating it as a combat issue.

For the exact encounter rules and reward pools, return to the Hunt database or Raid database. For the post-launch changes behind this guide, see Update 1.0.7 and Update 1.0.8.