The short answer
The current public version checked here is 1.0.9, released August 14, 2026. Use the official patch notes to identify confirmed fixes and the developer's pinned Known Issues thread to identify problems still being tracked.
| Status | What it means on this page |
|---|---|
| Fixed in 1.0.9 | The official patch explicitly says the issue was fixed |
| Developer-listed current issue | The developer still lists the symptom under Known Issues for 1.0.9 |
| Player report only | A comment describes it, but the reviewed official list does not confirm it |
What patch 1.0.9 fixed
The official August 14 notes include these directly stated changes:
- Rufus's free-time scene at the Stables, and similar scenes for other knights, should no longer repeat.
- An Act antagonist confrontation should no longer be skipped accidentally in a way that prevents the character from appearing in the Audience Room.
- Several quest-assignment problems involving a spoiler-sensitive knight were addressed.
- A response-to-quest mapping problem in a spoiler-sensitive trial chain was corrected.
- A Repair button now appears at the Round Table after the Forge is unlocked.
- An omni-fast-forward control was added for repeated dialogue, and fast-forward can remain active after choices by default.
- Arron's affected stat upgrade was adjusted to Strength and Agility only.
- A personal-event intervention was moved before the Act III transition lock so the player has time to resolve it.
These notes do not say that every quest, Map, NG+, or dialogue issue is fixed. If a symptom appears in the current list below, treat it as unresolved even when another nearby system changed in the same patch.
Developer-listed issues in 1.0.9
The pinned thread currently identifies problems in these areas:
| Area | Developer-listed symptom |
|---|---|
| Quest results | Timid, Fortunate, Brutal, and Duel attributes may not calculate correctly on the Results screen |
| Intendancy | Knight rumours can stop appearing, especially after New Game Plus or rewind use |
| World Map / NG+ | Several knights may not be recallable from the World Map |
| Map interaction | The Map can become unresponsive while inviting a knight to the Tower or repairing a location |
| Character state | A transformed Arron portrait can be misaligned |
| Pause menu | The menu can become non-interactive when the radial menu is also open |
| Dialogue state | Gideon dialogue can conflict after particular rewind, NG+, dismissal, and recruitment orders |
| Steam connection | A GODOT crash can occur when the game does not consider the Steam connection valid |
| Spoiler-sensitive knight | The developer lists remaining assignment and duplicated-equipment behavior without making it safe to generalize every trigger |
The list is a current developer-maintained snapshot, not a promise that every player will encounter each issue or that unlisted comments are false.
Step by step
1. Confirm the version
Check that Steam has updated the game to 1.0.9. An old report can still describe the same symptom, but it cannot prove the current cause or current fix status.
2. Classify the symptom before acting
Match the problem to one of three states: explicitly fixed in the patch, still listed by the developer, or reported only by players. This prevents a nearby fix from being mistaken for a universal repair.
3. Record the smallest reproducible state
Before rewinding or changing the roster, note:
- the Act and Cycle;
- the quest, knight, or Map location involved;
- whether the run is first-play, rewind, or New Game Plus;
- the action immediately before the problem;
- the result you expected and the result shown;
- the visible game version.
For a resource action such as armor repair, record the values before and after one attempt. Do not keep spending gold to prove the same failure repeatedly.
4. Preserve logs for a crash
The developer's Known Issues post points Windows players to the Godot log folder at %appdata%\AppData\Roaming\Godot\app_userdata\Sovereign Tower (VS)\logs. Copy the relevant log before another launch replaces useful context, then attach it through the official support discussion as requested by the developer.
5. Report through the official support area
Use the developer's pinned thread or the Steam Support & Bug Reports forum. Include the reproducible state and avoid hiding the important step inside a long story recap.
Safe checks by symptom
A Forge repair appears missing: confirm the Forge is unlocked. Version 1.0.9 adds the Round Table Repair button only after that unlock. Use the Forge and armor repair guide to separate unlock state from a failed transaction.
A character or audience changed after rewind: first compare the rebuilt assignments and relationships. Rewind intentionally recalculates downstream state; not every changed audience is a bug. The Demon Power guide lists what remains and what is replayed.
A knight cannot be recalled in NG+: this matches a developer-listed category. Record the knight, Act, Map state, and recruitment order rather than assuming that a normal first-run branch rule explains it.
The Map stops responding: stop making additional state changes and document whether the last action was an invitation or location repair. The developer lists both contexts; the current source does not justify a universal save-edit or file-deletion workaround.
The game crashes around Steam connectivity: preserve the Godot log and record Steam's connection state. The official list identifies this category but does not make every GODOT crash the same issue.
Common mistakes
- Reading a pre-1.0.9 report as proof that the current patch still behaves identically.
- Treating every comment under the official thread as developer-confirmed.
- Assuming a 1.0.9 quality-of-life change fixed every older bug in the same screen.
- Repeating repairs or other paid actions without comparing the before/after values.
- Deleting, editing, or replacing save files before preserving the original state.
- Reporting a symptom without the Act, Cycle, run type, knight, quest, and last action.
Evidence limits
This page was checked for Sovereign Tower 1.0.9 on August 19, 2026. Fixed status comes only from the official 1.0.9 patch notes. Current-issue status comes from the developer-maintained Known Issues thread, last reviewed August 19. The page does not claim that the list is exhaustive, promise a repair date, or convert unverified comment replies into confirmed bugs. Update trigger: recheck this page whenever a new official patch or a material edit to the pinned thread appears.
Sources
- Official patch notes 1.0.9 — fixes and quality-of-life changes released August 14, 2026.
- Developer-maintained Known Issues 1.0.9 — current tracked categories, crash context, and log location.
- Sovereign Tower on Steam — official game and support context.