Sovereign Tower Save File Location & Rewind Guide.

Where to look first

A rewind system and a manual save slot are not automatically the same thing. Check the current pause, options, save, or rewind interface on your platform instead of importing a keybind from an older post. Record the label exactly as it appears so the answer can be reproduced after an update.

• Note the platform and build before testing
• Write the exact control label or menu path
• Make a harmless checkpoint before an irreversible choice

Official Patch 1.0.11: save UI and overwrite focus

The official 1.0.11 notes say the save/load UI flow was adjusted to prevent confusion, and that overwriting a save no longer causes focus loss with controller or keyboard input. This fixes an interaction failure; it does not establish that every local backup restores the same route flags, rewind counter, or NG+ state.

• Fixed: focus loss when overwriting a save with controller or keyboard
• Fixed: confusing save/load UI flow
• Still test: the visible save result, restored day, party, quest, resources, and route flags
• Keep a dated copy of the complete local folder before testing recovery
• Evidence state: official 1.0.11 fix / restoration behavior remains build-sensitive

Manual save vs rewind: the open player question

A current Steam discussion asks how to save manually, which is a clear practical need but not proof of one universal control path. The safest answer is to distinguish a visible save slot, an automatic checkpoint, and a Demon rewind, then record what each one restores in the current build.

• Write down the exact save or menu label shown in your build
• Test one harmless save, reload it, and compare day, party, resources, relationships, and quest board
• Test a rewind separately so it is not mistaken for a manual save
• Keep the local folder backup and Steam Cloud state in the same test log

Run one clean comparison

Keep the quest, knight, timing, and preceding state the same where possible. Change one decision, then compare the immediate result and the follow-up scene. This turns a rewind into a controlled information loop.

• Decision: what changed?
• Result: what happened immediately?
• Lesson: what should the next run do differently?

If you meant the PC save folder

The developer's crash guidance points to %APPDATA%\Godot\app_userdata\Sovereign Tower (VS), usually C:\Users\your-name\AppData\Roaming\Godot\app_userdata\Sovereign Tower (VS), for local data. Treat this as a developer-provided troubleshooting path, not proof that every save mechanic or rewind state is stored there.

• Close the game before copying the folder
• If Steam Cloud is enabled, understand which copy is current before restoring a backup
• Copy the whole folder to a dated backup location
• Never delete the original until the backup opens or the troubleshooting step is complete

Try Again vs Demon Power rewind

Treat the post-ending Try Again action and an in-run Demon Power rewind as different operations. Community reports describe Try Again as returning to Day 1 with new omniscient dialogue and some earlier recruitment access, while Demon Power is counted when time is rewound during a run. The exact carry-over and true-ending eligibility still need a build-specific check.

• Record the ending screen before choosing Try Again
• Confirm the new run's Day 1 state and current rewind count
• List which knowledge, contacts, recruits, inventory, and relationships carried over
• Do not count the reset itself as a Demon Power rewind without observing the counter
• Back up local data and record Steam Cloud state before comparing runs
• Evidence state: community report / replay pending

Before testing an NG+ failure report

Recent Steam reports describe a Dragon Knight failure that may force a Demon rewind, plus an NG+ instant-death state with no clean death option. This page can help protect the local data, but it cannot yet promise that a backup restores a zero-reset route or removes the trigger.

• Copy the complete Godot app-data folder before starting the test
• Record whether Steam Cloud is enabled and which copy is current
• Capture the build, cycle, NG+ reset state, Dragon Knight timing, and exact fail screen
• Keep the original backup untouched until a restored test reaches the same checkpoint
• Treat any restored run as a separate reproduction, not proof of a general save rule

NG+ save overwritten: recovery is not confirmed

A new high-intent report asks whether an NG+ failure or forced rewind can overwrite the save state. That is an important recovery question, but the current evidence does not show whether the problem is Steam Cloud conflict, a local slot replacement, or a route flag that survives reload. Treat any recovery claim as build- and platform-specific.

• Disable or record Steam Cloud before making a controlled backup
• Keep dated copies of the complete Godot app-data folder, not just one guessed save file
• Test manual load, normal death, and Demon rewind as separate actions
• After restoring, compare cycle, rewind count, ending state, contacts, inventory, and route flags
• Do not delete the original copy or claim a successful recovery until the same checkpoint is reached twice

What this page will not claim

Exact save behavior can change by build or platform. Label notes as confirmed in your build, player-reported, or still unknown instead of presenting a convenient but unverified answer.