Subnautica 2 Guide Hub Guides, Map, Database, Tools

Reader reports and corrections

How player reports turn into guide fixes.

A useful report does not need to be long. This page shows what to include, which problems are checked first, and where to look when a guide has already been updated.

If you only have a minute

Send one page, one changed detail, and one context note. Add a screenshot or route proof when the issue is visual. Reports about route safety, progression, or co-op saves are checked first because they can affect an active run.

What this page is for

Use Reader Reports when you want to understand what a useful correction looks like, which report types move first, and where a guide fix is likely to appear next. If you already know you need the mailbox, use Contact.

Send a correction

Use the contact page when a page no longer matches your current run, especially after a patch or balance update.

Open correction path

Send route proof

Use screenshots, route notes, or map context when the issue is about landmarks, danger edges, or a material loop.

Open map proof format

See what is next

The update tracker shows which page groups are likely to be reviewed first during the next Monday update.

Open review queue

See the publishing rules

The editorial policy explains what the site publishes, reviews, corrects, and refuses to host.

Open editorial policy

Current report priorities

What we would review first if several reports arrive together.

Priority Report type Why it moves first Best evidence
1 Dangerous route or landmark mismatch A stale danger page can waste a good run or send a player into a bad return path. Guide URL, changed edge, route screenshot, patch context.
2 Rare material route no longer pays off Rare routes cost time and risk, so one wrong payoff can make the advice feel thin or outdated. Target material, route point, what the old page made you expect.
3 Co-op progression or host behavior changed Co-op confusion affects several players at once and often depends on save ownership or session setup. Host, platform, fresh or continued save, what carried over.
4 Typos, phrasing, or small layout issues These still matter, but they usually do not break the guide's practical answer. Page URL and the exact sentence or section.

How reports are used

What a report can change on the site.

Media checks Repeated images are checked across the page, not only one card.

When a report points out duplicate media, the surrounding guide cards are checked too so the same image is not simply moved elsewhere.

Guide updates Changed advice is updated with its next useful link.

A corrected sentence is not enough if the next step still sends a player into the old route, material loop, or co-op assumption.

Unconfirmed reports Unclear claims are labeled instead of being presented as fact.

If a report cannot be reproduced or verified yet, the page can be tightened with a warning rather than quietly overstating certainty.

Report-to-review workflow

How reader proof becomes a more original, more useful page.

Reader reports are not copied into pages as anonymous claims. They are used to decide what should be retested, what warning should be clearer, and whether a guide needs a stronger original table, checklist, route note, or media replacement.

Step What happens Visible result
1. Triage The report is matched to one page, one player problem, and one patch or platform context. The page may receive a warning, queue entry, or correction note.
2. Review The guide answer is checked against official context, existing route logic, and practical reader impact. The table, checklist, next-step link, or source wording is revised.
3. Maintenance record Meaningful changes are reflected in updates, review dates, or public support pages. Readers can see why the page changed instead of trusting a silent edit.

Report boundaries

What this page is not.

This page is not official game support, a bug tracker for Unknown Worlds, or a place to request downloads, account services, unlocks, cheats, or private game files. It is only the public guide-site correction layer for Subnautica 2 Guide Hub.

If your message is about official purchases, refunds, platform access, account problems, or product support, use official game, store, or platform support channels instead.

The notes on this page are not a promise that every report will be published or fixed immediately. They are a public signal for how the site weighs reader feedback, which reports are most useful, and which page groups are most likely to move into the next visible update cycle.

Reader proof help

What makes a report easy to trust and easy to act on.

A strong report answers one practical question: what changed, where it changed, and what should be checked next. That is the difference between a useful correction and a vague complaint.

Quick answer
  • Send one page, one issue, and one proof note.
  • Use screenshots or route proof when the problem is visual or location-based.
  • Say whether the change happened after a patch, a session reset, or a page refresh.
Common mistakes
  • Sending the problem without the page URL.
  • Mixing several unrelated corrections into one message.
  • Assuming a report is obvious when the page still needs exact context.