Mercenary Corps Progress

Daily missions include their exact targets, unlock quest, and every known reward draw. Key of Light milestones remain separate so the 30, 60, 90, and 120-use rewards are visible.

Daily: 9 · Target: 30 / 60 / 90 / 120 · Rewards: 18

Use the progress workspace to separate daily tasks from cumulative account growth, achievements, Orbis objectives, and activity unlocks before deciding which milestone to inspect next. 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. Light Key.

The account track uses cumulative EXP from the game data, including all 81 levels, special reward levels, stamina values, six ranks, promotion quests, and required materials.

Account level: 81 · Mercenary rank: 6 · Promotion quest: 5

The same loaded profile supplies the completion snapshot for every supported progress section. Daily targets and Light Key milestones remain distinct from permanent achievements so unlike counters are not combined into one invented total. 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.

Choose a retail Slot.db to project only verified progress mappings. The normalized IndexedDB profile is reused across pages; unsupported values show — or not loaded, and the raw save bytes are discarded after local validation.

Achievements: 103 · Region: 64 · Activity Guide: 7

Verified mappings may identify completed goals or current values, while unsupported counters remain visibly unresolved. The page never turns absence, a partial schema, or a similarly named capability into a checked objective. 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.

Use this section to connect the page’s visible result to the decision you need to make.

After selecting a replacement save, review the refreshed tab totals and the next bounded milestone, such as a Light Key reward, promotion condition, achievement group, or Orbis region target. 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.

Use this section to connect the page’s visible result to the decision you need to make.

Static requirements and rewards describe the published current version; the imported profile describes only the selected snapshot. Live cycle timing, hidden achievements, and unavailable objectives still require confirmation in the game. 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 progress check, load the newest retail Slot.db and compare the refreshed snapshot with the active game cycle. Use only mapped values when choosing the next milestone; — or not loaded is an explicit evidence boundary, not zero progress. Selecting another save updates the shared IndexedDB profile used by Adventure Book, Quests, and Progress, and the browser discards the raw database after local decryption and validation.