Editing guidelines

Short version: write things that are true, be kind, and don't be afraid to publish an imperfect page. Someone else will improve it; that's the whole point of a wiki.

Content standards

• Accuracy first. Only write what you have checked in the game or in a source you cite. Mark unverified claims as such.
• One topic per page. "Charms" is a page; "everything about the game" is not.
• Scope discipline. Each page covers only its own game, not sequels, prequels or adaptations.
• Spoilers. Hide story and late-game solutions in a spoiler disclosure. Give its summary a useful label without revealing the answer.
• No plagiarism. Don't paste from other wikis or guides. Write in your own words.

What every guide needs

A guide earns its place when it tells readers something they would not get from a summary of other sites. Before you publish a new guide, check that it has:

• One first-hand element. Steps you tested yourself, with the game version and platform in the review note; screenshots you took; or an original table or checklist you put together from the game or its official data.
• First-party sources first. Patch notes, the manual, developer posts and Steam's own data come before guides on other sites. Never link to another wiki, and don't restate one.
• A question players ask. Pick topics from what people search for and ask about: search suggestions and the game's Steam discussions and subreddit. A short page that answers a real question beats a long one nobody looks for.

Pages under 150 words start as stubs and stay out of search engines until they grow past that or a moderator regrades them. A stub grade set by a moderator stays until a moderator changes it. A moderator must approve the current revision of a member article before search engines can index it. Further member edits need a fresh approval. Adding your own review note does not approve the article.

Sources and review

Link factual claims to official manuals, developer posts, patch notes, or documented game data. Cite the specific page that supports the claim. Write your own explanation; do not copy a guide. Put a source beside the claim with [developer documentation](https://...), or collect numbered citations in a ## Sources section.

Open "Sources and review note" in the editor and tick "Add a review note with this edit" to record what you checked and when. Use "Source review" when you consulted documents. Choose "Tested in game by me" only after checking the behavior yourself, and record the platform and game version. The note records the exact text checked. Later edits show "Changed since review" until an editor checks the new text and updates the note. Older notes without a text fingerprint are shown as unconfirmed. A review records a contributor's evidence; it does not replace moderator approval or guarantee behavior after a patch.

Writing spoilers

Use the Spoiler toolbar button, or this Markdown. Keep blank lines around the hidden body:

<details data-spoiler>
<summary>Spoiler: late-game puzzle solution</summary>

Write the solution here.

</details>

Spoilers start closed and are omitted from generated excerpts and search snippets. Readers can reveal them individually or all at once.

Small contributions

A useful edit can be one tested detail: an item location, a missing requirement, or a correction to an old version. Explain what changed in the edit summary. Take a task from the contribution board, or follow a wiki to see later edits.

How coverage is counted

Every wiki shows a coverage label based on its guides. Steam information and the wiki's starter page (its home page) never count toward it.

• Useful article: a published guide marked complete or featured, with at least 80 words. Moderators set a page's status (stub, in progress, complete or featured). Wiki pages count useful articles as complete guides, as in "4 guides, 1 complete".
• No guides yet: no published guides yet, only Steam information and a starter page.
• Guides in progress: at least one published guide.
• Developed wiki: at least 5 useful articles.

The label describes how much a wiki covers, not whether each page is accurate. Review notes and page history show that.

Style

• Start pages with a one-sentence definition, then sections with ## headings. Skip the top-level heading; the title renders automatically.
• Link generously to other pages in the same wiki with [[Page Name]]. Red links are good, because they invite new pages.
• Use tables for stats and lists for steps. Keep paragraphs short.
• Leave an edit summary so patrollers can follow along.

Community standards

• Assume good faith. Fix mistakes instead of scolding them.
• No vandalism, spam, advertising or harassment. Any of these can get an account banned on sight.
• Disagreements about content belong in the page's discussion, not in edit wars.

Licensing

By saving an edit you release it under CC BY-SA 4.0. You keep attribution through the page history forever.