Quest journal & map usability

8 September 2026 · Interface update after the M4 alpha pack

The journal now prioritizes one actionable objective, offers a direct map link and keeps full quest details optional. The map separates personal guidance from the selected territory report. Existing quest progress, rewards, ownership, equipment and server combat rules are preserved.

Verification

• Client TypeScript check passes.
• Seven focused logic tests pass in tools/journey.test.ts: objective prerequisites, return-to-giver guidance, locked quests, missing locations, pending server completion, escort/boss instructions and connected territory recommendations.
• An isolated local server and a synthetic character were used for the browser checks. Journal-to-map-to-journal navigation, inert background cleanup, follow controls, search and its empty state, optional future quests, expandable sections and preserved focus passed.
• Staged client progress checked objective advancement, reward-ready guidance, marker relocation, completed history and stale-marker removal. These checks exercise presentation; they do not claim new combat or reward-system coverage.
• Saved preferences were checked for an intentionally empty tracker, accepting a new quest, migration from multiple pins to one followed quest and a manually marked territory surviving unrelated quest updates.
• Keyboard typing and Escape, focus wrap, and the controller navigation/activation callbacks passed. Physical controller ergonomics remain a human playtest item.
• Visual checks covered 1440 × 900, 1280 × 633, 390 × 844 and 720 × 450. Journal and map content stayed within the window width; shorter views retained scrolling and usable primary actions.

The journal renders when quest data or a deliberate UI action changes. Map position and the small world compass update at most five times per second, separately from the performance HUD. This update adds no WebGL models or post-processing effects. It does not replace the longer performance and group-balance playtests listed in the M4 verification.

Screens

The journal and quest-map images below use the isolated character's tutorial state. The territory image shows the same test world's initial enemy holdings.