Fast answer

Use the official support form with the exact build, platform, host/client role, shortest reproduction, expected versus observed result, and private evidence. Review DxDiag, paths, screenshots, and archives for personal information first.

Do this first

Save-safe order

  1. Search the official tracker and upvote the exact issue when appropriate.
  2. Write the shortest repeatable sequence.
  3. Include build, platform/store, world type, and host/client role.
  4. Attach evidence without exposing account details.
  5. Review save archives and DxDiag before private upload.

01

A reproducible report

Start with the state before the problem, list one action per step, then state the observed and expected result. Separate what always happens from what happened once.

  • Build and platform
  • World type
  • Host or client
  • Location/objective/item
  • Reproduction rate
  • Last known-good build

02

Evidence and privacy

DxDiag and saves may expose usernames, paths, or hardware details. Send them through the official private channel, not a public thread, and inspect archives before upload.

Evidence ledger

Sources checked

Official supportHow to Report a Grounded 2 Issue

Official evidence and attachment requirements for useful support reports.

OfficialGrounded 2 Issue Tracker

Authoritative issue IDs and current status. Recheck the tracker before acting on a status label.

Official supportGrounded 2 Known Issues List

Official support entry that routes players to the current known-issues tracker.

Editorial boundary

Official sources establish shipped features, issue status, and support steps. Cross-check and community sources are labeled and never treated as universal fixes.