Authors & Contributors

Who maintains Heartopia Guide

Heartopia Guide is maintained by a small editorial group supported by active community contributors. Our contributors include players who specialize in different game loops such as fishing optimization, event route planning, NPC affinity progression, and collection-focused exploration. This division of focus helps us review pages with relevant practical context instead of treating all topics as interchangeable list content.

We do not rely on single-source publishing for high-impact pages. Articles that influence progression choices are reviewed by at least one additional editor before major revisions are released. Reviewers check clarity, internal consistency, and whether recommendations are still valid under current game state.

Editorial roles

The core team generally works across four roles. Route editors draft execution steps and fallback logic for common player objectives. Data verifiers reproduce claims in gameplay and flag edge cases that should be called out explicitly. Structure editors simplify page hierarchy so readers can find the next action quickly on both desktop and mobile. Maintenance editors track update queues, merge duplicate intent pages, and keep canonical references clean.

Contributors can support one or more roles depending on expertise. We value reproducible evidence over volume. A short, well-tested correction is more useful than a long but unverified suggestion.

How author quality is maintained

Before publishing substantial updates, we run a checklist: define player intent, confirm route assumptions, verify internal links, and ensure the page includes actionable guidance rather than generic recap text. When gameplay evidence is uncertain, we annotate the section as provisional and avoid presenting speculation as fact. This policy reduces incorrect confidence and keeps trust with returning readers.

We also review historical edits to identify recurring issues such as duplicate phrasing, missing prerequisites, or inconsistent naming across map regions. Editors use those patterns to improve templates and prevent similar errors from reappearing in future pages.

Community contribution standards

Community reports are one of our strongest quality inputs. To submit effectively, include the page URL, specific issue, expected behavior, and reproducible context. If your report concerns timing windows, mention event phase or patch version. If your report concerns location ambiguity, include map region and nearby reference points. Detailed reports let us validate quickly and publish precise corrections.

We do not require professional writing style from contributors. We only require enough clarity to test the claim. When a correction is validated, we apply it to the primary page and update linked pages that depend on the same mechanic.

Submit a correction

Want to contribute a fix or a new finding? Submit through /feedback with evidence details. We appreciate player contributions that improve real gameplay outcomes for the whole community.

Our best contributor reports usually include both accuracy evidence and usability context. Accuracy tells us what is correct; usability tells us how to present the fix so players can act on it faster.

Contributors who include clear before-and-after examples help us improve both data precision and page readability. Those examples are especially useful when we update related guides in the same topic cluster.

As our guide library grows, we continue refining contributor standards so updates stay accurate, concise, and actionable for day-to-day players.

We also maintain an internal review checklist for contributor notes: clarity of objective, reproducible test context, map or timing precision, and expected player outcome after applying the change. Using the same checklist across topics helps us keep writing quality consistent whether a page is about fishing, NPC routing, events, or collection tracking.