How contributions are reviewed

Curated wiki rows and permanent map markers are maintained as reference data. Posts, comments, dynamic resource reports, and custom pins are user contributions. The interface keeps these sources distinguishable because they have different levels of review and freshness.

A community contribution can be helpful before it is formally verified, but it should not be presented as an official statement from the game developer. Official announcements and the current game client take priority when they conflict with a community observation.

Useful reports are specific, reproducible, and dated when timing matters. Include the map, server, nearby landmark, relevant condition, and what another player should expect to see. Screenshots can support a report, but a short written explanation is still important.

• Describe one issue or discovery at a time.
• Separate confirmed facts from guesses.
• Avoid copied guides, promotional links, and personal data.
• Update or comment when an earlier report is no longer current.

Reports can be hidden when they are abusive, misleading, duplicated, unrelated, or unsafe. A hidden contribution is not automatically a judgment about the author; it may simply be outdated or attached to the wrong map, server, or category.

Corrections preserve useful context where possible. For a small factual error, updating a field or adding a clarifying comment is preferable to deleting the entire discussion. Repeated spam or harmful content may be removed and the account restricted.

Use the report control attached to the affected post, comment, or marker. Include the exact problem and the expected correction. Privacy, account, copyright, or rights-holder requests should use the contact page rather than a public comment.

Heartopia Hub does not guarantee that every record is complete or error-free. The goal is to make uncertainty visible, respond to concrete evidence, and keep frequently used reference pages understandable after game updates.