Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Private, browser-local player worksheet

Build a precise Starbound troubleshooting note

Record the variables that change the correct support route. Your entries stay in this page until you choose to copy the note; they are not uploaded or saved. Never enter passwords, recovery codes, payment details, or another player's personal data.

Suggested next step

Record the exact symptom and compare the current official support instructions before changing data.

Game: Starbound
Guide: Starbound Crash Report: Find the Log and Capture a Reproducible Case (starbound-crash-log-support-report-checklist)
Platform/storefront: Not recorded
Symptom category: Other reproducible issue
Displayed build/version: not recorded
Recent change: none recorded
Observed result (redact personal data): not recorded
Safe next check: Record the exact symptom and compare the current official support instructions before changing data.

This is an editorial worksheet, not official support, automated diagnosis, a game-state check, or a promise of recovery. Use the guide's cited sources and current client as authority.

Capture enough context to reproduce

Chucklefish asks for a descriptive title, exact symptom, what you were doing, whether it repeats, operating system/version, mod list, display mode and—when the game crashes—the error log. That is more useful than a bare 'crash' report and helps separate a game issue from one tied to a particular mod or setup.

Report fieldRecordAvoid
TriggerMenu/action/location and exact last stepGuessing at a cause without a repeatable case
EnvironmentOS/version, storefront/build if visible, windowed/fullscreenAssuming a Windows fix applies to Mac/Linux
ModsNames and whether the issue reproduces without themDeleting a whole mod setup before backing up
EvidenceFAQ log path, relevant error text, basic hardware detailsPosting personal paths/usernames without redaction

References: Chucklefish: Starbound FAQ and crash-report checklist

Use the correct FAQ path

The publisher lists separate Windows, macOS and Linux locations. Confirm the installed storefront and OS before looking; if the path does not exist, do not substitute another platform's location. The FAQ's examples may need adjustment for a non-default install.

  1. Write down the OS/version, storefront, game build if available, and whether any mods are installed.
  2. Repeat the same in-game action once only if it is safe; note the steps and whether the symptom recurs.
  3. Open the matching OS log location named in the publisher FAQ and copy the relevant log without editing it.
  4. Describe expected behavior, actual behavior, display mode, and the exact recent change (update, mod or driver) without declaring it causal.
  5. Use the publisher's support forum/email route; redact account names, local usernames and unrelated personal data before attaching files.
  6. If the issue appears mod-related, identify the mod author/support route rather than treating an old community fix as official.

References: Chucklefish: Starbound FAQ and crash-report checklist · Starbound Steam Community Discussions

Before you play

  • OS and storefront match the chosen log path.
  • Trigger steps and expected/actual behavior recorded.
  • Mod list and display mode disclosed.
  • Log reviewed for personal paths before sharing.
  • Community fixes treated as anecdotes, not confirmed patches.

Frequently asked questions

Does this page upload my log?

No. The worksheet only formats details you enter in the open browser page; it cannot read Starbound files or send a support report.

Can I use a Windows log path on Linux?

No. Use the operating-system-specific path in Chucklefish's FAQ and account for custom storefront installs.

Does a JSON error prove a particular mod caused it?

No. The FAQ notes mods can be involved, but isolate cautiously and confirm against the mod author's current support guidance.

Sources & revision notes

Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. Chucklefish: Starbound FAQ and crash-report checklist (Official)

    Publisher FAQ covers supported platforms, multiplayer setup, reproducible bug reports, OS/mod/display details and log locations. Its troubleshooting examples reflect the FAQ's published guidance and can predate current operating systems or storefront changes; verify the installed build. No installation was tested.

  2. Starbound Steam Community Discussions (Community)

    External player-written Steam board, not verified GamerWin advice. Match operating system, storefront, build and mod list; do not download files from unsolicited posts.

What changed in this revision

November 7, 2026: first publication, reorganized Chucklefish's report fields into a platform-aware, privacy-conscious checklist. No game install or crash was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.