Contact
Found a route that no longer works, a missing step, or a page that needs a clearer explanation? Use the path below that matches your message so it reaches the right part of the site team.
Use editor@subnautica2.top for guide corrections, route notes, and map proof. Use partners@subnautica2.top only for sponsorships, affiliate discussions, and business outreach. If you want to understand how messages are reviewed first, open Community.
Use this for outdated steps, wrong route advice, patch changes, or pages that no longer match what happens in a live run.
Guide pages now open a prefilled correction note, so readers can send the page URL, changed section, and patch context with one click.
Reserve this contact path for sponsorships, affiliate opportunities, and game-related promotional inquiries.
Include the guide URL, what changed, the build or patch context, and one screenshot if the issue is about a route, resource, or co-op system.
On the next check, opening flow, material timing, route safety, repeated media, and co-op progress are the most useful reports to send first.
If you want to know how guides are reviewed, what the site refuses to publish, and how correction reports are handled, read the public editorial policy first.
Use the editor mailbox if a page looks copied, thin, visually misleading, or unclear about image ownership.
Who reads which mailbox
| Message type | Best path | Why this path is fastest |
|---|---|---|
| Stale guide, wrong route, patch mismatch | editor@subnautica2.top | Direct correction messages can be matched to one page and one changed detail immediately. |
| Marker, coordinates, map proof, danger-edge evidence | Map proof format | Map reports move faster when the proof pack matches the format the site already verifies. |
| Missing guide idea or visual improvement | Contribute | Suggestion pages are easier to plan when they start from the player problem instead of a loose email note. |
| Sponsorship, affiliate, campaign, business outreach | partners@subnautica2.top | Business requests stay separate so guide corrections do not get buried under commercial messages. |
What happens after you send a correction
The first job is to tie the message to one exact guide, route card, or tool page so the fix is not spread across unrelated topics.
Route safety, resource loops, dangerous zones, and multiplayer rules get bumped higher because they go stale faster than evergreen basics.
If the page cannot be fully confirmed yet, the safer move is to tighten the warning or trust boundary instead of pretending certainty.
The goal is not only to patch one sentence, but to keep the next-step links and surrounding route guidance honest too.
Real report examples
Contact pages feel more trustworthy when they show what a useful report actually looks like. These scenes match the kinds of issues players most often need to flag.
The best message includes the guide URL, what changed in the biome or return path, and one screenshot that proves the difference.
Check update-sensitive pages
This is where one screenshot, one changed recipe or timing note, and one practical consequence usually lead to the cleanest fix.
Open resource hub
A multiplayer correction becomes much easier to act on when it includes one session problem instead of a broad complaint about co-op.
Open co-op update pagesMap proof submissions
The map section improves fastest when submissions include the exact proof pack the site already asks for: one clear route purpose, full coordinates, depth, version context, and the screenshots that prove the route from the same run.
| Marker type | Best proof | Why it matters |
|---|---|---|
| Safe return loop | Start point, return landmark, and turnaround screenshot from one run. | Helps players trust early route safety instead of guessing the way home. |
| Early material loop | Material cluster shot plus safe banking or retreat cue. | Shows that the route solves a real farming need, not just map trivia. |
| Landmark anchor | Outward-facing and return-facing screenshots of the same landmark. | Makes navigation guidance more trustworthy even before a full coordinate map exists. |
| Danger edge | Warning shot from a safe distance plus retreat direction screenshot. | Prevents risky map advice from looking more certain than it is. |
Marker or route name
Guide URL or map section
X / Y / Z coordinate
Depth
Game version or update date
What the route solves for players
Screenshot 1: route or target proof
Screenshot 2: return, safety, or retreat proof
Visual correction examples
The fastest fixes are tied to something visible: a route that no longer works, a material loop that changed, or a co-op assumption that broke after an update.
Before you send
What happens next
Correction Policy
What To Send
The shared guide feedback box can now prefill this note automatically and copy it for devices without mail configured.
Source Priority
Editorial Boundary
Useful Requests
What Helps Most Right Now
Contact help
Contact works best when the message is narrow: one page, one issue, one proof note, and one reason the page should change. That keeps corrections from getting buried under general comments.
