DragonSword: Awakening quest tracker and prerequisite guide
Use the released Orbis quest graph to identify what blocks a mission, what it unlocks, where each objective happens, and what completion pays.
Trace every prerequisite and branch
The tracker uses 219 verified prerequisite links across the published main, epic, character, promotion, and tutorial quest lines. Unreleased World 2 quests are excluded.
Use the quest workspace to identify the first verified break in a prerequisite chain, then open the localized mission to review its ordered objectives, known locations, and published rewards. Choose a retail Slot.db file in the page header. Decryption, integrity checks, and schema validation run only in this browser; the file is never uploaded, and its raw bytes are discarded as soon as parsing finishes. prerequisite chain.
Read objectives before you travel
Each available step keeps the official localized objective, target count, time limit, objective type, and known map or dungeon name.
Search and category filters narrow the quest catalog without changing saved completion. A loaded profile can distinguish mapped completed quests from remaining records across main, epic, character, promotion, and tutorial lines. After validation, the site keeps only a normalized progress profile in IndexedDB. Adventure Book, Quests, and Progress read the same profile, so loading a save on one of those pages makes it available on the other two without another file selection.
Plan rewards and preserve progress
Choose a retail Slot.db to project only verified quest completion. The normalized IndexedDB profile is reused across pages; unsupported mappings show — or not loaded, and the raw save bytes are discarded after local validation.
A database capability is not assigned to a quest merely because its text looks similar. This conservative boundary prevents branch names, repeated objectives, or localization differences from creating false completion. Completion is projected only where the current save capability has a verified mapping to a published player-facing record. An unknown or unsupported capability stays shown as — or not loaded instead of being matched by a similar name or treated as completed.
What to compare before committing
Use this section to connect the page’s visible result to the decision you need to make.
When a target still appears blocked after a new save is loaded, compare its direct prerequisite, first remaining objective, branch, and linked region. The graph explains verified relationships but does not invent a hidden trigger. Choosing a newer or different Slot.db replaces the normalized profile and refreshes all three save-driven pages. Filters and detail views then use the replacement snapshot, while the original database bytes are not retained as a downloadable backup.
What to check next
Use this section to connect the page’s visible result to the decision you need to make.
Continue from a verified objective to its map link or from a known requirement to the related item page. Unknown rewards and unavailable World 2 records remain outside confirmed planning until current-version evidence exists. The imported snapshot is a local reading aid, not a live connection to the running game. Re-select a current save after playing when you want refreshed results, and confirm any unresolved trigger, reward, or value in the game rather than filling the gap manually.
For a reliable quest check, load the newest retail Slot.db, confirm that the header reports a validated local profile, and follow the first mapped unfinished prerequisite. Do not add a manual check when a mission is absent from the projection: — or not loaded means the capability has not been verified for that record. Selecting another save refreshes the shared IndexedDB profile for Adventure Book, Quests, and Progress, while the raw database is discarded after parsing.