Skip to content
Content ArchiveQuests, bosses, challenges and completion records
CurrentPatch 2.00.02

Quest Walkthrough & Encounter Encyclopaedia

Evidence-safe preparation, blocker recovery, supported checkpoints and unresolved research for named quests, bosses, Abysses and strongholds.

Evidence
Official source
Verified
2026-09-01
Spoilers
Major spoilers

The encyclopaedia turns canonical Content Archive records into usable operational guidance without promoting names into invented walkthroughs. Phases 20.1–20.7 retain 168/168 structural main-story routes from the prologue through the epilogue. All 168 carry a visible Version 2.00.00 review required warning for narrative flow, cutscenes, story moments, objective text and transitions; follow live objectives until each presentation layer is reverified. There are zero indexed main-story identities awaiting a route, but that identity and route coverage is separate from current narrative verification.

Quest and encounter fieldwork · Patch 2.00.02

Find a walkthrough

Search a quest, boss, Abyss or stronghold, open its focused route, then return here for the next task.

Searchable records
1040
Main story routes
168
Initial results
20
Record pages
1 each

Loading the lightweight search index…

  • Supported guidance may use clearly labelled official or corroborated community evidence. Phase 20 walkthroughs include starting points, requirements, objective routes, field tips, completion signals and safe recovery.
  • Indexed identity remains the safety state for corroborated records without a structural route. After Phase 20.7, zero indexed main-story missions remain in that state; the separate Version 2.00.00 review flag does not change identity support.
  • Research required confirms an official identity while explicitly withholding unknown phases, weaknesses, routes, statistics and rewards.
  • Private notes and preparation checks remain in the browser and are never sent to the guide, GitHub or an analytics service.

Do not restore an older save merely because an objective behaves unexpectedly. Confirm the current patch, required character, objective state and recorded blocker history first; preserve the newest working save before attempting rollback.