Sovereign Tower All Endings Guide: Best, True & NG+.

Write the fork before choosing

Record the day, active quest, party, resources, relationship state, and the choice you are about to make. If the result changes the run, you can reproduce the comparison instead of relying on memory.

• What is already known?
• Which character, faction, or resource is at stake?
• What would count as a better outcome on the next loop?

Keep knowledge separate from outcomes

Use three columns: decision, result, and lesson. The result may change after a rewind; the lesson should tell you what to test next. Mark a route as confirmed only after the same condition reproduces.

NG+ Try Again is not Demon Rewind

The current community route describes a post-ending Try Again action that returns the run to Day 1, unlocks additional omniscient dialogue, can expose earlier Act 2 or Act 3 recruitment opportunities, and resets the new run's Demon Power count. Treat this as a useful NG+ lead, not an official carry-over specification: the exact roster, contacts, inventory, relationships, and true-ending eligibility still need a current-build check.

• Finish a run and choose Try Again from the ending flow
• Confirm the new run starts at Day 1
• Record which omniscient dialogue and early recruit options appear
• Keep Try Again separate from using a Demon Power rewind inside the new run
• Test the true-ending route without assuming the community's Epicrates conditions are mandatory
• Evidence state: community route / replay pending

After the best ending: protect the original save

A recent Steam discussion asks what to do after a best ending. One player reports that Try Again returns to Day 1 while retaining some knowledge or contacts; another reports that the best-ending save was erased or that the run could not be restarted. These statements conflict, so this page treats the question as a save-state investigation rather than a safe carry-over promise.

• Back up the local save and record whether Steam Cloud is enabled before choosing Try Again
• Capture the original ending title, recruits, contacts, upgrades, Demon Power, and visible save slots
• Choose Try Again and compare Day 1 dialogue, roster, contacts, map, and rewind options
• Test manual load from the backup separately from Try Again
• Evidence state: community reports / conflicting / replay pending

1.0.10 NG+ checkpoint: re-test the Day 2 Dragon Knight invite

Patch 1.0.10 fixes several NG+ inconsistencies and an early Dragon Knight instant-kill case. A previously reported Day 2 invitation dialogue failure is therefore a re-test target, not a current-build rule: keep the checkpoint, record the exact line, and check whether the failure still reproduces.

• Back up before the Day 2 invitation
• Record the exact dialogue text and whether the run enters combat immediately
• Compare the same invitation after a clean Try Again reset
• Do not use an older report to claim that every 1.0.10 NG+ run is corrupted
• Evidence state: official fixes / older community report / current-build replay pending

1.0.11 NG+ boundary: Lost Child only

The official 1.0.11 notes fix inconsistencies in the Lost Child plotline when Gideon has not been recruited in New Game Plus. This is a narrow plot fix, not confirmation of the complete NG+ carry-over list, the Try Again rewind count, or any best, true, or secret ending gate.

• Fixed: Lost Child inconsistencies when Gideon is absent in NG+
• Retest the same Gideon-absent state in build 1.0.11
• Compare the dialogue, quest availability, and follow-up outcome
• Keep roster, contact, item, relationship, and ending carry-over as separate tests
• Evidence state: official patch note / wider route remains unverified

Official Patch 1.1.0: two new named endings

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. Add these to the working ending map, but keep their preceding route requirements separate from the official announcement; the patch names the outcomes without publishing a complete gate checklist.

• Added: Ambushing the Emperor under the Audacious ending
• Added: Diplomatic treaty with Angelor's nobility under the Kind ending
• Update the working map from five earlier families to seven named main outcomes
• Keep character slides and Demon Power epilogues separate from the named ending count
• Record the visible ending title, choice, achievement pop-up, build, and reset state
• Evidence state: official Patch 1.1.0 additions / exact route gates need replay

Best ending vs true ending: what the evidence says

Players use best ending and true ending as shorthand for the most complete or favorable outcome. The new public material improves the ending map, but it still does not establish one official universal route or prove that Epicrates is a separate main ending. To compare outcomes, compare the five main families, then confirm the ending title and achievement in your own build.

• Best ending: compare the final outcome, alliance state, and surviving characters
• True ending: do not assume it is identical to The Last King of Brizh until the result is reproduced
• Spoiler-light index pages should link here; exact final choices belong in the full-spoiler sections
• Record the build and Last checked date when a route changes

New evidence: five main ending families

Two public sources now converge on the same high-level structure. Raider King’s August 12 guide describes five main endings—War, Peace, Marry, Surrender, and Tower Destruction—while a separate Steam discussion published the same day reaches the same five-family map from a public decompilation/code-reading pass. This is stronger than the earlier single-thread ending guesses, but neither source is an official patch note or a current-build reproduction of every gate.

• War: the military victory branch
• Peace: the negotiated settlement branch, with Golden Key variants reported
• Marry: the Emperor proposal branch
• Surrender: the voluntary or defeat-flavored submission branch
• Tower Destruction: the branch that skips the usual epilogues
• Character/servant slides and the Demon Power epilogue should be tracked separately from the five main endings
• Keep exact stat thresholds, cycle gates, and Epicrates/Golden Key prerequisites marked as verify in build

September ending-count conflict: do not turn a competitor claim into a fact

A public competitor page updated on September 5 now describes six main endings and lists additional named variants. That conflicts with the five-family map supported by the two public analyses already documented above. The new page is useful for spotting search language and candidate branches, but it does not provide an official developer definition or a current-build achievement record, so this site keeps the count conflict visible instead of replacing five with six.

• Existing evidence: two public analyses converge on five main families
• New conflicting reference: competitor lists six main endings and additional variants
• Do not merge character slides or Demon Power epilogues into the main count without a reproducible rule
• Verification target: trigger each distinct final title in build 1.0.11 and record the Steam achievement or ending screen
• Evidence state: conflicting public references / needs-verification

How many endings? Separate official additions from community counts

Patch 1.1.0 officially names two added endings; it does not establish the game's total ending count. Our earlier five-family community map plus those additions is a navigation aid, not seven officially confirmed endings. Public guides also report nine outcomes, but multiple pages on one website are not independent corroboration. The total remains needs-verification until distinct final titles, achievement pop-ups, and epilogue variants can be compared in the current build.

• Official boundary: Patch 1.1.0 names two added endings
• Community lead: public guides report nine total or main outcomes
• Do not count character slides, farewell cards, or Demon Power epilogues twice
• Verification target: reproduce each distinct final title in build 1.1.0 or later
• Evidence state: official additions plus conflicting community reports / needs-verification

Reported final-choice map: use as a test matrix

The latest community notes place the main ending choice at the Emperor's final negotiation, reported around cycle 45. They associate Audacious with a marriage proposal, Kind or Wise with surrender possibilities, and Wise with the broadest set of choices. They also report that Peace can vary with Golden Key and Victoria's presence, while 1–19 versus 20+ Demon Power rewinds can change the epilogue. These are route signals, not official hard gates.

• At the final negotiation, record the actual cycle and the visible choice set
• Compare Kind, Wise, and Audacious choices from separate checkpoints
• For Peace, record Golden Key state and whether Victoria is present
• For Demon Power, log the rewind count, ending title, character slides, and epilogue separately
• Evidence state: community report / replay pending

Wise options and romance cards: do not merge the outputs

The latest public discussion includes two separate questions: Wise players can see different final options, and players are unsure whether romance changes the ending card. Treat the main ending title, character or romance slides, and Demon Power epilogue as separate outputs. A favorable romance slide does not by itself prove a best or true ending route.

• Record the visible Wise menu before choosing
• Record the main ending title separately from romance or character cards
• Compare Victoria, Epicrates, Golden Key, alliances, and romance state one variable at a time
• Keep the missing TD option and romance-card relationship marked community report / needs verification

Epicrates ending: strongest current test route

The current community lead connects The Last King of Brizh with Epicrates or Serpent Knight, Angelica and Golden Key, broad regional alliances, and limited Demon Power use. These signals are useful for planning a test run, but they are not yet a single confirmed formula.

• Keep Angelica available and test the Golden Key branch
• Track the number of allied regions instead of assuming all 10 are mandatory
• Record whether Demon Power was used and how often
• If Epicrates is freed or cleared at trial, record which route was used
• At the final decision, capture the exact choice and visible ending name

Ending leads worth testing

Current community discussions repeatedly point players toward Peace, at Last, Capitulation, An Audacious Solution, The Last King of Brizh, and a Serpent Knight or Epicrates ending. The useful page-level answer is the test matrix, not a single promised best ending: record the final choice, Angelica and Golden Key state, regional alliances, Demon Power use, and whether the ending actually triggers.

• Peace, at Last: test the negotiation, peace, and winning-result sequence
• Capitulation: test the Act 4 unconditional surrender choice
• An Audacious Solution: track Audacity and the Emperor relationship route
• The Last King of Brizh: compare Epicrates, Golden Key, Demon Power, and alliance variables separately

NG+ and Demon Power: what is known

The new Raider King guide and the public Steam code-analysis thread both describe Demon Power as an additional epilogue layer rather than a standalone main ending: no rewind skips that layer, one or more rewinds adds a lower-corruption version, and a higher rewind count adds a darker version. The Steam author later corrected an earlier claim that the corruption flag was purely cosmetic, so some branch effects remain unresolved. Treat the reported 1–19 and 20+ thresholds as strong public leads, not as reproduced current-build facts.

• Before resetting, record the current ending, recruited knights, contacts, upgrades, and Demon Power state
• After the reset, compare the Day 1 roster, map, contacts, knowledge, and rewind options
• Test one carry-over claim per run instead of changing several variables
• Keep Steam Cloud and local backup behavior as a separate save test
• For Demon Power, record rewind count, visible epilogue, character slides, and any changed dialogue separately

New NG+ failure reports: keep the route unconfirmed

Two separate Steam discussions now point to the same high-intent problem area, but they do not establish one reproducible trigger or a fix. One player asks whether using the forced Demon rewind after a Dragon Knight death contaminates a zero-reset NG+ run; another reports an instant-death fail state in NG+ where the game does not offer a clean death option. Keep this as community report / replay pending rather than promising a safe route.

• Back up the local save before testing a post-ending reset
• Record the game version, NG+ reset state, cycle, Dragon Knight invitation timing, and exact fail screen
• Separate a manual load, a normal death, and a Demon rewind in the test log
• Success means the same route can continue without a forced corruption increment or soft-lock
• Failure means the same build reproduces the fail state and only offers a rewind or a new run

A safe ending test log

Use a small matrix for each ending attempt: build, cycle, alliances, Angelica state, Golden Key state, Demon Power use, final choice, visible ending title, achievement pop-up, and whether the run was reset. This prevents a post-ending clue from being mistaken for a hard prerequisite.