FAST ANSWER / RESULT SCREEN
Unexpected Outcome: record the branch before rewinding.
There is no confirmed universal trigger for an Unexpected Outcome. Capture the result screen first, separate the label from the meter or stat hint, then log damage, reward, follow-up, and build so the next run tests the quest branch instead of guessing from the label.
- Record the quest, party, visible requirement, result label, meter or hint, and build.
- Add damage, reward, named-knight change, and follow-up scene as separate fields.
- Check the All Quests map for a named-knight or special-result lead before changing the party.
- Rewind only after the capture, change one variable, and compare the two result screens.
Result-screen lookup: keep five fields separate
A result that feels wrong is easiest to investigate when the screen is treated as a record, not a verdict about the formula. The visible class, meter or hint, damage, reward or follow-up, and build can change independently; keeping them separate prevents one surprising label from becoming a universal rule.
- Outcome: Critical Success, Critical Failure, Unexpected Outcome, or the exact visible label
- Signal: meter position, stat hint, requirement text, and any warning shown before dispatch
- Cost: damage, armor, relationship, treasury, or item change
- Payoff: reward, named-knight state, and follow-up scene
- Context: quest, party, preceding state, platform, and build
What is actually confirmed
The game presents quest outcomes as Critical Success, Critical Failure, or Unexpected Outcome, and the result screen includes a large gauge or meter. Players have specifically asked what the gauge represents and which factors move it; the developer acknowledged that the presentation needed to become clearer. No official public percentage formula is available in the sources checked for this page.
- Use the result class as confirmed output
- Use the visible debrief details as evidence
- Treat the bar's exact numeric meaning as unconfirmed
- Do not turn one successful run into a fixed success rate
Patch 1.0.11: incorrect hints are fixed, not the formula
The official 1.0.11 notes fix cases where incorrect stat hints were displayed, along with some ultimatum durations and duplicated requirement text in Volga Camp Serial Killer options. This improves the information shown by the interface, but it does not publish the underlying score formula or prove that every result label maps to a specific story branch.
- Re-check the visible stat hint before dispatch in build 1.0.11
- Separate a corrected hint from a changed quest result
- Record the quest, party, visible requirements, result label, and damage
- Keep the scoring formula and plot effect as needs-verification
- Evidence state: official patch note / formula still unavailable
Unexpected Outcome: what it means right now
For the direct Unexpected Outcome search, the honest answer is that the label is a visible result class, not a confirmed universal trigger. A named knight, hidden condition, relationship state, or story branch may be involved, but the public evidence does not prove one formula. Start with the result screen, then use the All Quests map to identify the branch worth testing.
- Record the visible result label, meter or hint, and damage
- Check the quest's named-knight or special-result lead
- Compare the same quest from the same before-state with one changed variable
- Check reward, named-knight result, and follow-up scene separately
- Evidence state: result class visible / trigger and plot effect unverified
How to run a useful meter test
Start from the same preceding state and keep the quest, knight, equipment, and timing unchanged. Record the result. Rewind, change one variable, and record the new result. Repeat before deciding that a stat, trait, item, or potion caused the change.
- Baseline: quest, party, visible requirements, result
- Test A: change one knight or one stat contribution
- Test B: restore the baseline and change one item
- Compare both the gauge presentation and the final outcome
Equipment and potion stacking
Community feedback specifically raises uncertainty about which equipment and potion effects stack and which appear to cancel. Until the interaction is reproduced in the current build, compare your exact equipment combination rather than assuming a universal stacking rule.
- Name the item or potion and the affected stat
- Record whether the effect is shown before dispatch or only after debrief
- Test the combination with the same knight and quest
- Label the result as verified, player-reported, or unknown
What a trustworthy answer looks like
A useful guide does not need to pretend the system is fully reverse-engineered. It should tell the player what the screen confirms, what the community suspects, and the safest next test. That is more valuable than a made-up percentage that breaks after an update.
COMMUNITY SCREENSHOT / PUBLIC REFERENCE
What the screenshot actually shows
Visually reviewed September 19, 2026. These are externally hosted player screenshots, not our own gameplay tests. Capture versions are not displayed; route verification remains pending.
Read the result label and the marker together: this screen shows Critical Success for Victoria duel with Goberto assigned. Arlin's note is a separate explanation of the outcome.
Show player screenshot (spoilers)
SEARCH QUESTIONS / SHORT ANSWERS
Common questions
What does the Sovereign Tower quest result meter show?
It summarizes the quest calculation and visible result, but the public sources do not provide a confirmed percentage formula. Read the debrief and test one modifier at a time.
How do you get an Unexpected Outcome in Sovereign Tower?
There is no confirmed universal trigger. Check the quest's named-knight or special-result lead, record the visible result, damage, reward, follow-up, and build, then compare one changed variable from the same before-state.
Did Patch 1.0.11 fix incorrect Sovereign Tower stat hints?
Yes. The official notes fix cases where incorrect stat hints were displayed. That does not confirm the underlying score formula or every story effect, so compare the hint and result screen separately.
What should I record before rewinding a failed Sovereign Tower quest?
Record the quest, party, visible requirements, result label, meter or hint, damage, reward, follow-up, preceding state, and build. Then change one variable and compare the new result instead of guessing from the label alone.
How do I get a Critical Success in Sovereign Tower?
There is no confirmed public success-chance formula. Match the visible requirement, check named-knight or trait signals, capture the stat hint and result screen, then test one party or modifier change at a time. A Critical Success label should not be treated as a guaranteed plot result.
Baseline source: official Sovereign Tower page on Steam. Additional reference: Steam result-meter discussion. / recent community all-quests correction. / official Patch 1.0.11 notes. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: September 8, 2026.