Community
Use this page when the report should become part of the site’s public maintenance trail or review queue.
Community reports
Help keep Subnautica 2 guides useful after patches and real runs.
This hub collects correction paths, reader reports, contribution rules, and review priorities so the site looks and behaves like a maintained guide project, not a frozen article dump.
Use this page for public reports and correction flow
Open Community when you want to report a stale guide, send route proof, suggest a missing page, or see how reports turn into visible maintenance. If you only need the correct mailbox, use Contact. If you want source rules or publishing boundaries, use Editorial Policy.
Reports
See how reader reports become guide fixes
Use this when you want to understand correction priority and proof rules.
Corrections
Send one page, one issue, and one proof note
Best for wrong route advice, stale patch details, repeated media, or unclear wording.
Contribute
Suggest a missing guide or visual improvement
Best when a real player blocker needs a new page, table, route map, or diagram.
Contact
Use direct email when you already know the issue type and want the fastest correction, map-proof, or partnership path.
Reader reports
Use structured report pages when the issue needs screenshots, route evidence, or a clearer review trail.
Editorial policy
Use the policy page when you want to understand source order, review standards, ad boundaries, or what the site refuses to publish.
Choose the right path
Different messages need different handling.
| Your issue | Best page | What to include | Review priority |
|---|---|---|---|
| A guide is wrong after a patch | Correction path | Page URL, changed detail, patch or build context. | High when it affects route safety, resources, co-op, or systems. |
| A route, map, or danger zone does not match your run | Map proof format | Screenshot, route note, landmark, and where the old advice failed. | High because route errors can waste active runs. |
| A page has repeated or poor visuals | Reader reports | Page URL and which image, crop, or diagram feels wrong. | Medium unless it blocks reading or causes confusion. |
| A useful guide is missing | Contribute | The player problem, when it happens, and what answer would help. | Medium, higher if many players hit the same blocker. |
| You want to know how the site makes decisions | Editorial policy | No report needed; read source order, review rules, and boundaries. | Trust and review background. |
Community standards
Reports should improve guides, not create noise.
Specific beats long
One page link and one concrete mismatch is more useful than a broad complaint about the whole site.
Proof helps route pages
Map, danger, resource, and base-location reports are easier to verify with a screenshot or route note.
Patch context matters
If a problem appeared after an update, say so. Patch-sensitive pages move first in review.
No unsafe requests
The site does not handle downloads, cheats, account services, unlockers, private files, or unofficial support.
What changes after reports
Good feedback should leave a visible maintenance trail.
Route, resource, co-op, and system issues are grouped by the pages most likely to mislead active players.
If a route is stale, the next link, table, diagram, or stop rule should also change so the reader can act on it.
Public update notes make the site look alive and give returning players a reason to trust newer pages first.
Community depth
What the report hub should decide before a reader sends another note.
This page should make the report path feel useful, not noisy. Good reports are specific enough to become a fix, and the page should tell readers what proof helps most before they send anything.
- Send one page, one problem, one proof note.
- Use screenshot or route evidence when the issue is about movement or danger.
- Put patch context in the first line if the page changed after an update.
- Sending a broad complaint instead of a fixable page-level note.
- Mixing report feedback with account or platform support.
- Leaving out the current build or route context for a stale guide.
- Open Reader Reports for a structured report path.
- Open Contact corrections for the fastest page fix.
- Open Editorial Policy if you want to know how reports are reviewed.