First, name the failure
'Won't start' and 'crashes during a cycle' are different reports. Write down whether the game closes before the menu, when opening the map, after a specific day, or after a particular interaction. Include your operating system, hardware level, and whether the issue is repeatable.
- Launch failure: no menu or immediate close
- Progression crash: closes at the same cycle or interaction
- Visual or result-screen bug: the game continues but the state is wrong
Try the low-risk checks
The developer's Steam response asks players to confirm that the device meets the minimum requirements, update graphics drivers, and describe the exact crash point. Do those checks before removing saves or reinstalling.
- Confirm the device meets the store page requirements
- Update the graphics driver
- Note the cycle, map, quest, and interaction that precede the crash
- Keep a copy of any useful error text before changing the install
Last resort: the developer's reset procedure
For a suspected faulty install, the developer recommends disabling Steam Cloud, uninstalling the game, deleting the old local save data, and reinstalling. The listed save folder is AppData\Roaming\Godot\app_userdata\Sovereign Tower (VS). This can reset progress, so treat it as a last resort and preserve anything you may need first.
- Disable Steam Cloud for Sovereign Tower
- Uninstall the game
- Back up the local save folder before deleting it
- Remove the old local save only if you accept losing that progress
- Reinstall and test the same failure point
What to include in a useful bug report
A short report with the build, hardware, cycle, exact interaction, and whether a clean reinstall changed the result is more useful than 'it crashes'. It also lets other players distinguish a local save problem from a repeatable game bug.
Platform-specific crash report: needs verification
A current Steam discussion index includes a report of a crash after a dialogue choice on CrossOver 26.3 with a Mac M4. It is a useful platform-specific search lead, not a confirmed compatibility rule. Reproduce it before changing the general troubleshooting order.
- Record macOS version, CrossOver version, game build, and translation or launch settings
- Capture the exact dialogue choice and whether the crash repeats from the same save
- Compare a clean save or a different renderer only after preserving the original state
- Evidence state: single community report / needs verification
Baseline source: official Sovereign Tower page on Steam. Additional reference: developer response to a crash report. / official Steam requirements. / Steam current discussion index. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: August 22, 2026.