Correction
Give one page URL, the wrong detail, and the correct detail if you know it.
Corrections and page ideas
Help keep the guide hub current.
If you spot a stale route, a mismatched image, a missing page, or a title that no longer matches the content, this is the fastest place to send it.
Use this page for missing-page and improvement ideas
Open Contribute when the issue is broader than one correction: a missing guide, a better diagram, a clearer title, or a new player blocker that deserves its own page. If one live guide is simply wrong, use Contact instead.
Best reports
Useful reports are specific, not long.
Missing page idea
Tell us which blocker needs a dedicated guide instead of a broader article.
Visual issue
Flag repeated images, unreadable text, bad crop, or a picture that does not fit the page.
Trust note
Tell us when a guide feels stale after a patch or a live update changes the answer.
What to include
The faster we can verify it, the faster it can be fixed.
- One page link or page title.
- One short sentence about what is wrong or missing.
- One screenshot, route note, or source link if you have it.
- One note about whether the issue came from a patch, a guide mismatch, or a visual problem.
Where to send it
Use the contact path for direct reports.
Email editor@subnautica2.top for corrections, media notes, or missing-guide ideas. The contact page also has a fallback path if email is not available.
What not to send
Keep it short, factual, and easy to verify.
- Do not send spam, phishing, or unrelated promo links.
- Do not send guesses without saying they are guesses.
- Do not send personal data unless it is needed for a correction you are trying to report.
- Do not send files or screenshots that you do not have permission to share.
Contribution help
What makes a contribution useful instead of just polite.
The best contribution usually removes one visible problem from the site: a wrong detail, a missing page, or a visual that confuses the reader. Short and specific reports are easier to turn into real maintenance work.
- Point to one page and one exact issue.
- Tell us what changed in the run or what is missing from the page.
- Attach proof only when it helps verify the problem faster.
- Sending a vague idea without a page or topic.
- Mixing several unrelated issues into one report.
- Sending guesses as if they are confirmed corrections.
- Open Contact corrections for direct fixes.
- Open Reader Reports to see how reports are handled.
- Open Editorial Policy to see what the site will and will not publish.
Contribution depth
What a useful contribution should add to the site.
The best contribution is not a vague compliment or a loose idea. It is one clear improvement that reduces confusion, adds a missing answer, or makes an existing page easier to trust.
- Point to one page or one missing topic.
- Say what the player problem is and why it matters.
- Attach proof only when it helps verify the issue faster.
- Sending a broad idea with no page or blocker.
- Mixing unrelated fixes into one message.
- Treating guesses as if they are confirmed corrections.
- Open Contact corrections for direct fixes.
- Open Reader Reports to see how feedback is handled.
- Open Version History to see what maintenance looks like publicly.
Contribution filter
Only send ideas that can become a page, table, or fix.
Contribution pages stay useful when they narrow the ask. If the idea cannot turn into one concrete site change, it is probably too broad for this room.
Good fit
One missing guide, one wrong detail, or one page that needs a better handoff.
Needs more detail
A broad topic that still needs one exact player problem.
Wrong room
Account help, platform support, or anything outside the site itself.