Current game versionRelease build 1.0.6 · 2026-07-31

Database checked against release-build sourcesVerified

Patch and roadmap status

DragonSword Awakening Quest Progression Fixes in Update 1.0.4

Updated 2026-08-02

Quick answer

DragonSword: Awakening update 1.0.4 fixed several named quest and progression defects. If your game is fully updated, the old issue described for the matching quest should no longer be the expected behavior.

Quest or activityProblem listed as fixed in 1.0.4
Adventure Quest 48: SiegeBlack screen after the cutscene blocked progression.
Adventure Quest 39: Where the Giant SleepsLip-sync was missing in some dialogue.
Weldon Area QuestThe NPC was missing while its speech bubble appeared.
Certain Area Quests involving Igniter SnickrakDefeating Igniter Snickrak too early could block progression.
Adventure Quest 59: Tomb of GreedJohnny's icon appeared as Lute's icon while cooking.
Dana's Hero QuestCertain NPCs were not displayed.
Adventure Quest 35: Steelheart FortressPlayers could not move after failing the mini-game outside the fortress.
Puzzle mini-game tied to Marmot King Hog's Bond Quest: Fly, Familiar!Attempting the puzzle before completing the prerequisite could leave the player unable to move.
Adventure Quest 37: The Looming ShadowSome placed Harpy monsters were removed.

The patch note confirms fixes, not full walkthrough routes. Do not use this page as a substitute for the objective sequence shown in your current quest log.

First step: confirm the installed version

Before trying unofficial recovery steps:

  1. let Steam finish downloading the current DragonSword: Awakening update;
  2. restart Steam and the game;
  3. load the affected quest again;
  4. repeat the objective in its intended order;
  5. record the exact quest number, objective text and symptom if it still fails.

If the symptom matches a 1.0.4 entry but persists on a later build, it may be a regression or a different state. The official note does not instruct players to edit saves, replace quest flags or use third-party tools.

Adventure Quest 48: Siege black screen

The official note says update 1.0.4 fixed a black screen after the cutscene in Adventure Quest 48: Siege. This establishes the affected quest and failure point.

It does not establish:

  • which cutscene branch every player saw;
  • a manual skip command;
  • a save-file flag to edit;
  • a guaranteed recovery for a save already left in an unusual state.

Update first and retry the official flow before escalating the issue.

Weldon and Igniter Snickrak Area Quest blockers

Two Area Quest problems were addressed:

  • an NPC could be absent in a Weldon Area Quest even while its speech bubble appeared;
  • defeating Igniter Snickrak before completing certain Area Quests could prevent those quests from progressing.

The second fix is sequence-sensitive. The patch note does not name every affected Area Quest, so avoid publishing an invented complete quest list.

Dana Hero Quest missing NPCs

Update 1.0.4 says certain NPCs were not displayed during Dana's Hero Quest. If a guide written before this patch assumes an NPC will remain invisible, that workaround is stale.

For Dana's verified identity and patch context, see the Dana official profile. The profile does not claim a complete Hero Quest route or recruitment condition.

Steelheart Fortress and the prerequisite puzzle

Two movement locks were fixed:

  • failing the mini-game outside Steelheart Fortress in Adventure Quest 35 could leave the player unable to move;
  • attempting a puzzle mini-game before completing Marmot King Hog's Bond Quest Fly, Familiar! could also leave the player unable to move.

The safest current-build approach is to complete explicit prerequisites before entering their dependent puzzle and to retest after updating. The announcement does not authorize bypassing the prerequisite.

The later Ornette fix is a different patch

Update 1.0.5 fixed a blocker at the Talk to Ornette objective in Adventure Quests 15–18. That issue is documented separately because it is a distinct symptom and patch:

Keeping the pages separate prevents a search for one quest blocker from landing on an unrelated list of fixes.

When to report a persistent blocker

Capture:

  • the current game version;
  • quest number and exact objective;
  • whether the NPC, marker or interaction is missing;
  • whether movement or UI control is locked;
  • whether the issue remains after restarting the game;
  • whether unsupported mods, trainers or save edits are active.

Hound13's mod and save-editing notice says unsupported changes can cause crashes or unrecoverable progression states and may fall outside individual recovery support.

Sources