Contact

How to contact us

If you found an incorrect location, outdated step sequence, missing condition, or unclear explanation, please send it through our feedback channel so the editorial queue can process it in priority order. We review player reports daily and use them to decide what gets updated first. Reports that include concrete evidence and clear reproduction context are resolved much faster than generic messages. Our contact flow is designed to minimize back-and-forth and move directly from report to verification.

Use: /feedback for all correction and request submissions. If your request is policy-related, include the exact URL, current issue, desired outcome, and why the change is needed. A short, structured report helps us avoid ambiguity and lets us ship a correct fix on the first pass.

Best format for correction reports

For data corrections, include five fields: page URL, what is currently wrong, expected behavior or location, steps you used in game, and proof details such as map region or timing condition. If the issue is route efficiency rather than pure accuracy, mention your objective and session constraints so we can test under comparable conditions. This distinction matters because a route that is valid for completion might still be weak for speed farming, and we maintain different guidance for those intents.

If your report references event-specific mechanics, include the event name and phase. Many player issues come from timing confusion rather than map confusion. We verify event reports against current rotation windows before updating live pages. When something cannot be confirmed immediately, we add provisional notes to reduce player risk while full validation is in progress.

Missing page and expansion requests

We also accept requests for missing guides, especially when a game system has changed and existing pages no longer answer common questions. To prioritize fairly, please include the specific question players are asking, what existing pages fail to cover, and which route decisions are currently unclear. Requests with explicit user intent are easier to scope and ship quickly. Broad requests like add more content are harder to action because they do not define the decision gap we should solve.

When several requests compete for the same update window, we prioritize by player impact, duplication risk, and maintenance cost. Critical fixes that can cause repeated resource waste usually go first. Feature-like expansions come next. This process helps keep the site reliable for daily gameplay instead of becoming a backlog of unfinished pages.

Response expectations and privacy

Most reports receive an initial response within a few business days. Complex corrections may take longer if they require repeated gameplay checks across conditions. We do not need sensitive personal data to process normal reports. Share only what is necessary to reproduce the issue, and avoid posting private account details. If you accidentally submit sensitive information, tell us in your message so we can remove it during processing.

Thanks for helping maintain guide quality. High-quality community feedback is one of the strongest inputs we use to keep pages practical, current, and trustworthy.

If your request is urgent because an incorrect step can cause repeated resource loss, mention that impact clearly in your report title. Impact-based triage helps us prioritize fixes that most affect daily gameplay and keeps the update queue focused on player outcomes.