Sovereign Tower Patch 1.1.0 — New Endings & Fixes
See the two new Sovereign Tower endings in patch 1.1.0, plus Gideon romance, Family Disaster, New Game Plus, and recruitment fixes.
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Last verified
- 2026-09-08

Official patch notes1.1.0Developer announcement published September 7, 2026; checked September 8, 2026. Fixes are developer-reported, not independently reproduced playthroughs.
Which endings were added?
The announcement adds an Audacious outcome involving an Emperor ambush and a Kind outcome involving a treaty with Angelor’s nobility. Our endings guide records the announced outcomes and separates those additions from the still-unverified complete ending count.
The patch does not publish a choice-by-choice route. Before testing either outcome, record your build, act, archetype, and major decisions. Keep the resulting ending scene alongside those notes so a later comparison has more evidence than the archetype label alone.
Which players should check their routes again?
| If this affected your playthrough | Developer-reported change | Continue with |
|---|---|---|
| Gideon’s epilogue did not match your marriage or Lost Child outcome | Corrections to those ending scenes | Romance guide |
| A departed romanced Knight lost affinity | Correction to that relationship behavior | Romance and favorite meals |
| Family Disaster failed to unlock | The blocking bug has been fixed | Achievement index |
| Map Room invitations failed for Arron or other characters | Invitation fixes | Recruitment guide |
| New Game Plus crashed | A crash fix | Rewind guide |
The update also addresses other character-state and dialogue problems. Consult the official 1.1.0 announcement for the full list.
Before retrying an affected save
- Confirm Steam has finished updating the game, then record the version you are testing.
- Keep a separate save before the affected decision when possible, so you can compare the scene without losing your earlier record.
- Note the exact character, quest, or achievement and whether the result changes after updating.
The announcement does not promise that every affected old save repairs itself or that achievements unlock retroactively. If a problem remains, report the build and the steps that reproduce it; a repeated failure alone does not reveal a hidden route requirement.
Find announcement and support entry points in official links and community.
For broader planning, return to the first-cycle walkthrough or beginner tips.