Community report desk

Subnautica 2 Community Reports

Anonymous summaries of recurring player questions, Hotfix 3 follow-up reports, and launch-week patterns. This page is designed for fast updates without copying Discord messages, usernames, screenshots, or private community content.

How reports work: Community reports are treated as leads, not final confirmation. Hotfix 3 gives us official fixes to reference, but nearby symptoms still need platform, build, save-state, and repro details before they move to known issues.
Divers and a maintenance robot near an underwater habitat corridor

Report buckets we track

These buckets are used to summarize recurring access, co-op, performance, reward, and policy questions without copying individual community posts.

Topic Likely report Source type Status Action
Launch timing and install access Players usually ask why a store page still shows the wrong entitlement state, why install access differs by launcher, or why Game Pass access is tied to a different Microsoft account. Official timing plus storefront reports Live triage Route users to the download guide, server status page, and storefront-specific checks before calling it a game bug.
Game Pass and Xbox ecosystem questions Expected questions include PC Game Pass versus Game Pass Ultimate, cloud availability, Xbox on PC, ROG Xbox Ally, and Microsoft account entitlement. Xbox Wire plus player reports Ready to triage Keep subscription tier, account, device, region, and cloud access separate in every summary.
Co-op invite and cross-platform behavior Current watch items include Steam/Xbox version mismatch after hotfix rollout, invite failure, host disconnects, platform mismatch, account login, Tadpole session / reprint state, base-teleport or dock-load wording, and late-route stability. Hotfix 3 specifically fixes clients reverting to a previous position when rejoining multiplayer. Official hotfix context plus community reports Active watch Record host platform, client platform, game version, error text, biome, vehicle state, base or dock state, save age, reprint wording, and whether Xbox / Windows Store has received Hotfix 3 before publishing a workaround.
Performance, crashes, and PC requirements Reports may combine low FPS, DLSS crashes, Frame Generation availability, settings not saving, startup crashes, DirectX errors, AMD driver timeouts, hard power-off symptoms, post-hotfix save-load freezes, cloud-session errors, storage pressure, and hardware below the official minimum. Official requirements plus player reports Hotfix 3 split Ask for CPU, GPU, RAM, OS, driver, storage, storefront, GeForce NOW / local status, resolution, DLSS / Frame Generation settings, overlay list, thermals, power-supply context, crash logs, and whether the report happened before or after Hotfix 3.
Biome collision and out-of-bounds leads A May 30 lead mentions a Hot Caves no-collision or out-of-bounds path. This is useful to watch, but it is still a single-report lead rather than a confirmed recurring bug. Community report lead Pattern needed Ask for biome, route, depth, coordinates if available, vehicle state, whether the player saved out of bounds, and whether the same path can be reproduced twice on the current build.
Rewards, launch-week gift, and Twitch Drops Some players may confuse launch-week purchase rewards, Microsoft Store bundles, Twitch Drops, and account-linking timing. Official reward posts plus player reports Separate issue lane Separate purchase date, storefront, platform account, Twitch account, game account, and account-linking status.
Save rollback, missing files, and .bak recovery Players are discussing missing or rolled-back saves and whether local .bak files can be used after a patch or crash. Community reports plus save-location checks Community workaround watch Tell users to copy the entire SaveGames folder first. Do not treat .bak renaming as an official fix unless Unknown Worlds documents it.
Creature combat expectations Some players expect hostile creatures to be killable or expect the Survival Tool to behave like a weapon. Hotfix 3 changed Hammerhead / Tadpole wording, Nibbler perception and damage, and Marrowbreach damage and attack frequency. Official community letter plus player feedback Not-a-bug clarification Route this to creature mitigation guidance: aggression, aggro range, flares, Survival Tool behavior, and vehicle/base interactions are tuning targets; lethal combat and exact damage values should not be promised.
Armor, Tadpole Haul Chassis, and vehicle-state cleanup Hotfix 3 fixes Strike Armor modification stacking additively and goggles remaining visible after exiting the Tadpole Haul Chassis as a passenger. Nearby armor, passenger, docking, or vehicle-state reports still need clean repro context. Official Hotfix 3 plus community reports Fixed symptoms / watch nearby Separate exact Hotfix 3 fixes from adjacent reports. Ask for biomod loadout, armor state, passenger role, vehicle module, dock state, build version, and whether the save was created before the patch.

Intake rules

  • No usernames, direct Discord quotes, private screenshots, or copied player images are published here.
  • A single player message is a lead. A report becomes useful only when the same symptom repeats with platform context.
  • Official posts override community guesses. When official guidance changes, the old report summary should be replaced.
  • Every summary should say what is known, what is not confirmed, and what a reader can check next.

How a report becomes a site update

  1. 1. Record only the meaning of the report: symptom, platform, source type, and whether the same report repeats.
  2. 2. Check official sources and store pages before publishing a conclusion.
  3. 3. Publish a short anonymous summary here when the report is useful but not confirmed.
  4. 4. Move confirmed patterns into known issues with a specific workaround or next check.

Related pages

Use these pages to turn a raw community report into a useful player answer.