Save Progress Guide: Find Unfinished Quests, Adventure Book Entries, and Goals

The game stores your account progress in a local Slot database, and this site's save reader opens the selected Slot file entirely in the browser: it decrypts and validates the database, projects it into a normalized profile, and keeps only that profile locally. The profile is then reused by the supported pages, which means the completion pages can show what is actually unfinished instead of what you remember marking. The save work happens on your machine, and the browser only stores the normalized result. The progress database /progress shows the supported views once a profile is loaded.

The boundary matters: the reader can only report what the save file records. An unmapped field or an activity the save does not track stays out of the report, so the pages are an evidence layer, and anything they do not show is an in-game check rather than a claim that it is done.

The workflow is a single import: choose the Slot database, let the reader validate and project it, and the normalized profile becomes the shared input for the completion pages. There is no per-page re-import, and no manual marking of what you already did. The progress database /progress is the hub, and the related pages—quests, Adventure Book, and the rest—read the same profile, so the numbers stay consistent across pages.

The privacy property is worth repeating: the game's Slot database never leaves the machine, and nothing is uploaded. The import is a local computation with a local result, which makes the tool safe to use with your own saves.

With a profile loaded, the quest view can show which quests remain and where they sit in the ordered chain. The current quest catalog has 268 quests with 1,899 ordered steps, and the save profile reveals which steps are still pending. The quest database /quests shows the steps in order, so the "what do I do next" question is answered by the chain rather than by a map marker. The profile turns a wall into a list.

The same view exposes the quest categories: story, character, promotion, and the rest. A stalled promotion trial and a missed character quest look different in the list, and each has its own next action. The quest database /quests filters by category, which matches the save-derived view.

The Adventure Book has 149 entries across five sections, and the save profile shows which entries are registered. The Adventure Book /adventure-book page marks the missing entries with their locations and requirements, so the completion route is derived from the save instead of from memory. The same profile feeds the progression views: achievements, activities, and account milestones.

The completion checklist becomes a byproduct of the import: after loading the profile, the remaining work is visible on the pages that read it, and the next session's plan is a list of missing items rather than a guess. The Orbis map /map layers and the quest database /quests turn that list into routes.

The profile is a snapshot of the save at import time, so it goes stale when the game changes. Re-import after a major session to refresh the completion views, and keep in mind that the reader reports what the save records, with the unrecorded parts left as in-game checks. The progress database /progress documents the supported fields, so the boundary is explicit rather than surprising.

The practical habit is one import per play session: load the save, read the remaining work, plan the session, play, and re-import when the session changes the state. The pages stay consistent, the plan stays derived from evidence, and the completion goal keeps a date instead of a mood.