UNOFFICIALIndependent help site. Not affiliated with Blue Bottle Games or Kitfox Games.

DIAGNOSTICS // 1.0

Ostranauts 1.0 Problems & Fixes Checklist

A safe troubleshooting order for Ostranauts 1.0 save, loading, mod, missing-content, and Internal Affairs Woes quest problems.

Living pageVerified for Ostranauts 1.0 launch buildChecked August 10, 2026

Quick answer

What you need to know

Protect the save first, confirm the game finished updating, test without mods, and compare the problem in a fresh 1.0 game. If Internal Affairs Woes stalls after the confrontation, other players report the same dead end, but there is not yet a verified dialogue choice that completes it.

Use this order

  1. Back up the affected save.Do not keep testing destructive changes on the only copy.
  2. Confirm the update finished.Restart Steam and verify the game reports the expected build.
  3. Disable non-Core mods.In MODS, clear mod checkboxes and inspect any MISSING, ERROR, or red version warning.
  4. Retry once in the same save.If the problem disappears, restore mods in small groups.
  5. Compare with a fresh 1.0 game.Missing station or plot content in an old world is not the same as a universal game bug.
  6. Collect a useful report.Record build, save origin, active mods, location, exact action, and whether the issue reproduces fresh.

Problem shortcuts

New plot or station missing

Compare with a fresh 1.0 world; old generated systems can lack new content.

Mod not loading

Check MODS for MISSING or ERROR, then remove local/Workshop duplicates.

Red mod label

The declared target version is older than the running game. Treat it as a compatibility warning.

Old ship matters, old world does not

Use the Ship Editor import feature and begin a fresh 1.0 run.

Internal Affairs Woes will not advance

Use the focused checks below. The current public discussion confirms the symptom, not a universal solution.

Internal Affairs Woes stuck after “rough them up”

A player report describes exhausting the post-confrontation dialogue without getting a new objective, and replies report the same stall. That makes this a known player-reported dead end, but the thread does not prove which dialogue branch, stat check, timer, or game state is intended to advance the quest.

  1. Keep a save from before the confrontation.Do not overwrite the only point where you can test another branch.
  2. Record the exact last objective and dialogue choices.This distinguishes a hidden prerequisite from a broken state when reporting it.
  3. Retest without non-Core mods.Use a copy of the save; this check does not imply that mods caused the problem.
  4. Do not follow an invented dialogue sequence.No public source checked on August 10 documents a reproducible completion route.
  5. Abandon only if you accept losing this quest branch.Some players chose to abandon it, but that is an exit from the dead end, not a verified fix.

What this page does not promise

A clean mod-free reproduction can still be a real 1.0 bug. This checklist narrows the cause; it does not claim that every launch issue has a local fix.

Manage choices

Optional services stay off until you choose otherwise.