Sovereign Tower 1.1.1 Bugs: Quest & Equipment Fixes.

Patch 1.1.1: symptom-specific fixes

The September 17 update addresses Golden Key, Silver Cat, Chester's trial, Moonvale follow-ups and equipment display. The route guides explain the individual boundaries. An official fix does not guarantee recovery of every old save.

Developer-confirmed: Victoria and Gideon

The current developer response says Victoria's interactions and behavior are not working as intended. Players report that even honest recruitment choices can be counted as lies, after which Victoria may leave the Round Table. Gideon's relationship or story follow-up can become unavailable as a consequence.

• This is not currently evidence that the player chose the wrong dialogue
• Do not treat Victoria as a stable recruitment route
• Keep a save before Victoria appears
• Do not assume a Victoria death or a Gideon duel restores the complete route

Official Patch 1.0.10: re-test the old failure reports

The latest official patch narrows several issues that were previously only safe to describe as open reports. It fixes Victoria ambushing herself, Yorhav not resolving correctly after the assassination, several Gideon and NG+ inconsistencies, Oliver recruitment after choosing mercy at the start, and multiple quest-result and trait calculations. This is a version boundary, not proof that every route is now fully confirmed.

• Fixed: Victoria self-ambush and Yorhav assassination resolution
• Fixed: several Gideon/NG+ inconsistencies and a related soft lock
• Fixed: Oliver should be recruitable when mercy was chosen at the start
• Fixed: quest result scores summing incorrectly and several trait calculations
• Fixed: Ligia's Basalt Isles follow-up and lamp/mermaid cure conflict
• Fixed: Goberto and Childeric armor reverting to damaged state
• Re-test before repeating an older 1.0.9 failure report
• Evidence state: official patch note / route-wide verification still pending

Official Patch 1.0.11: save, UI, assignment, and romance fixes

Steam's latest official notes add a new current-build boundary. They fix focus loss when the navigation wheel and pause menu overlap, focus loss after overwriting a save with a controller or keyboard, and confusing save/load UI flow. They also fix several route-adjacent issues, including automatic assignment for Brunhilda Testimony, the inability to trigger Carina romance, sending recruited Victoria on Victoria's Ambush, incorrect stat hints, and a Lost Child inconsistency when Gideon is absent in NG+.

• Fixed: save overwrite and overlapping navigation/pause focus loss
• Fixed: save/load UI flow confusion; still verify the restored state
• Fixed: Brunhilda's automatic assignment to Brunhilda Testimony
• Fixed: Carina romance trigger and recruited-Victoria Ambush assignment
• Fixed: incorrect stat hints and some ultimatum quests lasting longer than one cycle
• Fixed: Lost Child inconsistencies when Gideon is not recruited in NG+
• Evidence state: official 1.0.11 patch note / full route behavior still needs replay

Official Patch 1.1.0: two endings and an NG+ crash fix

The official 1.1.0 notes add two named endings: an Audacious ending for Ambushing the Emperor and a Kind ending for a diplomatic treaty with Angelor's nobility. The same update fixes a New Game+ crash, several conversation issues, and missing rewards from the Mushrooms Invasion quest. It also adds an Alwena death follow-up dialogue and disables the intendancy the following morning; these are current-build facts, not a universal route recipe.

• Added: Audacious ending, Ambushing the Emperor
• Added: Kind ending, Diplomatic treaty with Angelor's nobility
• Fixed: a New Game+ crash
• Fixed: several conversation issues and missing Mushrooms Invasion rewards
• Added: Alwena follow-up dialogue explaining that she stepped away from the knight roster
• Changed: the intendancy is disabled the morning after Alwena's death
• Evidence state: official Patch 1.1.0 / exact route gates and carry-over still need replay

Can't repair damaged towns? Open Map Room from the main menu

A Steam Support thread contains two players reporting that the repair action is missing or disappears when they try to use it. The developer's reply distinguishes the two map entry points: open the Map Room from the room list on the main menu, because the small map icon in the top-right does not expose the repair action. If the button is still missing from the correct Map Room, fully exit the game, verify the installed files in Steam, and reload.

• Open the Map Room from the main-menu room list
• Do not use the top-right small map icon for town repairs
• If the action is still missing, verify installed files and reload
• Record the build, input device, map entry point, and exact repair prompt
• Evidence state: developer response plus two player reports / documented UI path; separate persistence cases remain needs-verification

Current support queue: route, UI, and crash symptoms are different tests

The public Steam support index currently mixes several high-intent symptoms that look similar in search but need different evidence. A missing map action, a Golden Key task that cannot send knights, a startup or dialogue crash, and an NG+ day-37 failure should not be merged into one '1.0.11 bug' claim. Use the dedicated route page when the game still opens, and use a clean-save reproduction when it does not.

• Map Room repair: follow the documented main-menu path first; persistence after reload remains needs-verification
• Golden Key dispatch: record the exact task, roster state, menu path, and visible error; route-not-appearing report / needs-verification
• Lich Quest: capture the quest state, act, result text, and whether a clean reload repeats the report
• Kingslayer requirements: record the visible requirement, preceding choices, build, and exact failure message
• Startup or dialogue crash: record platform, renderer, build, preceding choice, and whether a clean restart repeats it
• NG+ day-37 or instant-death report: back up the save and separate manual load, Try Again, New Game, and Demon Rewind
• Arron or Epicrates recruitment: compare the character route note before calling a missing invitation a build bug
• Evidence state: official guidance for Map Room; Lich, Kingslayer, crash, and NG+ items are community reports / replay pending

Official Patch 1.0.9: partial fixes and open boundaries

The official 1.0.9 notes fix the Victoria trial responses being mapped to the wrong quest, which could make her leave because she was marked as lying. They explicitly leave the Yorhav assassination and other strange Victoria quest behaviour under investigation. The same patch fixes Rufus's repeated stables scene, Alwena assignment problems, and accidental skipping of an Act confrontation.

• Fixed: Victoria trial response-to-quest mapping
• Still open officially: Yorhav assassination and other unusual Victoria quest behaviour
• Fixed: Rufus free-time repetition at the stables and similar knight scenes
• Fixed: Alwena assignment failures and the need to assign her last
• Fixed: accidentally skipping an Act antagonist confrontation
• Also changed: Arron's Dragon Heart upgrade is Strength and Agility only
• Also changed: Ursula's intervention happens before the Act 3 Demon Lock transition
• Evidence state: official patch note / remaining route behavior replay pending

What 1.0.8 fixed—and what it did not

The official 1.0.8 update notes remain the historical boundary for Ligia and Gwendan-related repairs, save/load confirmation, item changes, and Dragon Knight difficulty. Patch 1.0.9 adds the partial Victoria and roster fixes above; the remaining Victoria route behavior stays open rather than confirmed.

• Fixed or improved: follow the official patch notes for the exact repaired interaction
• Still open in this guide: Victoria's false-lie result and the Gideon follow-up
• Version-sensitive: verify whether a later hotfix changes the result before repeating an old route

Community reports to reproduce

Several reports are useful investigation targets but do not yet justify a universal workaround. Test them with a clean before-state and one variable at a time.

• Quest result screen duplication or stale result text
• Arrest the Traitor behavior after a rewind
• Mount-based quest-duration reduction not applying or the UI not updating
• Alwena failing to accept a long quest after a duration change
• Older Ligia task locks that may be fixed in 1.0.8

Virtual Currency and Gwendan: community report only

The current all-quests reference reports that the reformed-Gwendan special result for Virtual Currency does not trigger. No official patch note or independent current-build reproduction was found in this pass, so this belongs in replay pending rather than confirmed bugs.

• Test the quest with reformed Gwendan from a clean before-state
• Compare unreformed Gwendan and a normal knight on the same quest
• Record build, result text, reward, and follow-up state
• Promote the report only after a second independent report or a repeatable local reproduction

Post-1.0.11 report queue: keep the boundaries visible

Patch 1.0.11 narrows several save, UI, assignment, romance, hint, and NG+ reports, but it does not automatically prove every community route. Keep the reformed-Gwendan Virtual Currency result, any remaining Victoria route anomaly, and unverified recruitment or ending conditions in separate test cards with the new build recorded.

• Victoria: retest the recruited-Victoria Ambush guard, then keep any remaining Ambush/Duel and Enberg behavior as separate states
• NG+: record whether the earlier Dragon Knight invitation issue still occurs after 1.0.11 and compare the Gideon-absent Lost Child path
• Save/load: verify that overwrite focus and UI flow are fixed without assuming route state is restored correctly
• Virtual Currency: compare normal knight, normal Gwendan, and reformed Gwendan from the same quest state
• Success means the result repeats or clears in a clean 1.0.11 run; failure means the old report still reproduces
• Evidence state: official fixes / community report / replay pending

New high-intent route reports: do not call them fixes

Today's public discussion scan adds several questions that deserve a place in the bug log, but not a definitive answer. Patch 1.0.9 removes some older Rufus and Alwena reports from the confirmed-open list, but the Act 2 traitor/murder event still has conflicting reports about prevention and triggering. Victoria reports still include Ambush/Duel repetition and Enberg route stalls, and the official notes leave Yorhav assassination behavior open. Other leads mention missing Groom or Pawnbroker invitations and a Rufus/Intendancy dialogue that may still need a clean-build replay.

• Act 2 traitor/murder: compare the reported prevention route against a clean run where the event triggers; record all assignments and the exact act/cycle
• Victoria Ambush/Duel: capture duplicate task text, duel choice, Enberg state, and whether the route advances after reload
• Groom/Pawnbroker: record the invitation prerequisite, visible UI state, and whether 1.0.8 save/load confirmation changes the result
• Rufus/Intendancy: record the preceding recruitment, dialogue choice, and whether a new cycle or rewind releases the scene
• Evidence state: community report / conflicting / replay pending

NG+ failure reports: do not promise a safe reset

Two separate Steam discussions now describe the same high-intent risk area: a forced Demon rewind after a Dragon Knight failure, and an NG+ instant-death state with no clean death option. The reports are useful and recent, but they do not establish one trigger or prove that every zero-reset run is affected.

• Back up the local data before testing a post-ending reset
• Record the build, platform, NG+ reset state, cycle, and Dragon Knight invitation timing
• Separate manual load, normal death, and Demon rewind in the test log
• Mark the result as reproduced only if the same state fails twice
• Do not call a forced rewind a confirmed corruption rule until the counter change is observed

How to report a useful reproduction

Write down the build, platform, cycle, active quest, party, preceding choice, rewind or save action, and the first incorrect result. A screenshot of the result screen or a short video is stronger than a conclusion such as 'the route is broken'.

• Expected result
• Observed result
• Exact steps from a known before-state
• Whether a second run reproduced it
• Whether the result changed after a patch or clean save

New Steam questions: watchlist only

The current Steam discussion index shows several fresh support questions, including a CrossOver 26.3/Mac M4 crash after a dialogue choice, a player who cannot use the map, and questions about missing invitations. These are useful troubleshooting intents, but the index does not provide enough reproducible detail to call them confirmed bugs.

• CrossOver 26.3 / Mac M4: record the dialogue choice, game build, save state, and whether the crash repeats
• Can't use the map: record the act, map screen, input device, and whether the issue survives a reload
• Missing invitations or high-affinity scenes: record roster cap, open slots, preceding event, and cycle
• Act 2 murder and final-battle questions remain linked to their dedicated evidence-limited guides
• Evidence state: single community reports / needs verification