Editorial policy

1. Start with the player’s question

The title and opening answer should match the situation that brought the player to the page. Introductions do not repeat marketing language or delay the first useful instruction.

2. Show the complete route

Walkthroughs name the start NPC or menu, required materials, important intermediate actions and the visible result that confirms completion. A single action is not split into several artificial steps.

3. Use screenshots as evidence

Images should identify the menu, marker, NPC, item, route or result discussed beside them. Decorative images do not replace proof, and annotations must not hide the relevant part of the interface.

4. Write like a player, not a template

• Prefer direct instructions and concrete nouns.
• Remove repeated summaries, inflated adjectives and generic “comprehensive guide” language.
• Keep troubleshooting only when it explains a real failure state.
• Do not expand a page merely to increase word count.

5. Label uncertainty

Recipes, prices, schedules and objectives can change. The live in-game panel takes priority. A primary location may be listed, but moving NPCs should be tracked through the game instead of assigned an unverified fixed schedule.

6. Correct before expanding

Existing pages are reviewed for contradictions, old counts and broken routes before new content is added. In Task 50, for example, outdated card counts were corrected to match the actual walkthroughs.