Quest Database Fields
- Quest name, region, and starting NPC or trigger.
- Day or night availability.
- Recommended level or story progress.
- Choice outcomes and irreversible decisions.
- Rewards, unlocks, endings, and follow-up quests.
Spoiler Policy
Quest pages should begin with a spoiler-light summary, then separate major story consequences under clear warnings. This lets players solve progression problems without accidentally reading ending details.
Launch Priority
The first walkthroughs should cover the opening route, early side quests, quests with time windows, and any mission that can fail or lock rewards. These are more useful than a full but shallow list.
Back To The Walkthrough Hub
This page is part of the walkthrough hub. Use the hub page when you want the broader reading path and related launch planning pages.
Launch-Week Publishing Pipeline
When a quest is verified, copy the quest template from templates/quest-template.html, add spoiler-safe objectives first, then add choices and consequences only after testing. Add the finished page to sitemap and link it from this quest hub.
FAQ
- What makes a quest page valuable?
- A valuable quest page tracks trigger, location, time window, choices, rewards, missables, related characters, and consequence links.
- Should quest walkthroughs be published before launch?
- Only framework pages should exist before launch. Exact objectives and outcomes require hands-on verification.
- How should spoiler-sensitive quests be handled?
- Use spoiler-light summaries at the top and hide ending or character-fate details deeper on the page with clear warnings.