Sovereign Tower All Quests: Conditions & Unexpected Outcomes.

Coverage: outcome categories, not a complete quest checklist

The six score rows below describe result categories, not six quests or a complete quest list. Use the quest finder for individual requests and All Knights for dispatch attributes. Missing conditions are unknown, not guaranteed success rules.

• Historical official boundary: Patch 1.0.10 corrected some quest-score sums and trait calculations; this is not a published scoring formula.

Fast lookup: what to record before sending

A long quest table becomes useful when each row answers the same dispatch questions. Before sending a party, copy the visible request into a small record and keep source claims separate from what your build shows.

• Quest identity: exact name, location, cycle, and story state
• Dispatch: requested party size, visible stat pressure, named knight, and available candidates
• Outcome lead: reported threshold, special result, and source or evidence label
• After dispatch: result class, damage, reward, follow-up, and any roster or relationship change
• Replay note: the one variable to change next, with the current build recorded

What the new quest map adds

The latest community guide is useful because it treats the game as a collection of quest states rather than a simple stat checklist. It maps reported success conditions, possible result classes, and special outcomes tied to particular knights or story states. The author says the map was built from game files and then checked in-game, so it is richer than a purely anecdotal list, but it can still contain errors or version-specific behavior.

• Use it to locate the relevant quest and outcome
• Keep file-derived values separate from what the current build visibly confirms
• Treat comments and corrections as new leads, not automatic truth
• Record the exact build when a result matters

How to read one quest entry

Break each entry into four questions: what stat or trait is being tested, what minimum is reported, what outcome class is possible, and whether a named knight or story state changes the result. That structure turns a long quest list into an actual dispatch decision.

• Pressure point: Strength, Agility, Charisma, Magic, Wit, Luck, or a hidden trait
• Threshold: the reported minimum or the range that still needs testing
• Outcome: Critical Success, Critical Failure, or Unexpected Outcome
• Branch: knight, relationship, evolution, location, or story state

Critical Success is not automatically a plot branch

A recent community correction reports that Critical Success mainly lowers damage and does not necessarily change the quest's story result. Keep that as a community report rather than a universal rule: compare the result class, damage, reward, and follow-up scene separately before treating the outcome as confirmed.

• Record the visible Critical Success label and damage first
• Compare the same quest from the same before-state with a normal success
• Check reward, named-knight result, and follow-up scene separately
• Do not use Critical Success alone to explain an Unexpected Outcome
• Evidence state: community report / second source or in-build reproduction needed

Official Patch 1.0.11: quest timing and hint cleanup

The official 1.0.11 notes fix some ultimatum quests that lasted longer than one cycle, incorrect stat hints, and duplicated Damage Risk or Stat Requirements text in Volga Camp Serial Killer options. These are interface and quest-flow corrections; they do not establish a universal scoring formula or confirm every special outcome.

• Fixed: some ultimatum quests exceeding one cycle
• Fixed: incorrect stat hints
• Fixed: duplicated Volga Camp Serial Killer damage-risk and stat-requirement text
• Re-test the visible hint, duration, and result screen in build 1.0.11
• Evidence state: official patch note / formula and named outcomes remain unverified

The practical order of operations

The supplied 1.0.8 notes recommend checking a quest in layers: special result first, then the required number of knights, then every visible stat requirement, then traits, equipment, food, and quest preference. This prevents a high average from hiding a missing requirement.

• Check for a named knight or special-result branch first
• Send the requested number of knights instead of padding the party with weak candidates
• Meet all visible stat requirements before comparing traits or equipment
• Use quest preference to improve affinity only after the outcome is safe

Direct answers worth testing first

The most useful entries in the supplied notes are not generic questions; they are warnings that can prevent a bad route. Keep these as separate test cards so a patch can update one condition without rewriting the entire quest map.

• The Clean Keeper Goose: Angelica can lead to the special result, 25 gold, People +1, and Goose Part 2
• The Clean Keeper Goose Part 2: test Wit 3, Luck 4, Cheese, Horse, or an unreformed Gwendan before the Chester check
• The Bloody Magpie: the notes warn against sending Goberto because the reported result is a full-party death with no reward
• The Great Duel / Useful, At Last: two public community references converge on sending Goberto while the dragon escapes, which can lead to Almor armour and a special final result; replay the exact preceding setup before calling it confirmed
• Knife Throwing Tournament: Victoria is the reported special-result candidate for 300 gold

Virtual Currency: Gwendan is a replay target

The current all-quests map reports that the reformed-Gwendan special result for Virtual Currency may be bugged and does not trigger. This is a public guide's community report, not an official patch note or a second independent reproduction, so keep it as an unverified current-build test target. The same source lists Villador / Research, AGI 3, WIT 6, LUCK 3, one knight, one cycle, and reported damage of 1–2 as the ordinary task profile; treat those values as source notes until the result screen confirms them.

• Reach Virtual Currency with Gwendan in the reformed state
• Record the ordinary result and whether the special result appears
• Compare the same quest with an unreformed Gwendan and a normal knight
• Reported ordinary result: Nobles +1 and 35 gold; normal Gwendan report: Nobles +1 and 30 gold
• Reported reformed-Gwendan expectation: Nobles +2, 120 gold, and local tax +5; current report says this special result is bugged
• Capture the build, reward, result text, and follow-up state before calling it a bug

Useful, At Last: Almor Great Duel lead

Two independent public community references now point to the same Almor branch: send Goberto in The Great Duel, do not complete the preceding Fight the dragon setup, and allow the dragon to escape. The reported result sets the Almor dragon-escaped state, gives Goberto Almor armour, and continues to a special final outcome. This is strong community evidence, not an official condition or a local reproduction.

• Reach The Great Duel / final Almor stage
• Send Goberto and record the preceding Almor choices
• Do not merge this lead with the older Perfect Armour numbers until the in-game result text identifies them as the same reward
• Capture the dragon result, Goberto's equipment, follow-up scene, and build before repeating the test

Attribute-triggered special results

Some special results are tied to a threshold rather than a named knight. The supplied notes report Magic, Wit, Luck, Charisma, Strength, and low-Wit triggers across several quests. Keep the exact number labeled as reported until the current build reproduces it.

• Magic ≥ 14: Repel the Dragon
• Wit ≥ 12: Suspects Interrogations
• Luck ≥ 11: In Search of the Gem
• Magic ≥ 10: The Lich Will Not Return and A Thesis Thief
• Charisma ≥ 10: The Vampire of Clovermont
• Strength ≥ 10: Animal Bodyguards
• Wit ≥ 8: Diplomatic Meeting and Slugs Invasion
• Magic ≥ 7: Hydra Hunt and The Possessed Reverend
• Wit ≤ 3: The False Bank

Unexpected outcomes are the reason to keep a log

The community material specifically emphasizes that some quests change when a particular knight is sent. A result that looks like a failure in a generic guide may be a deliberate character branch, an evolution trigger, or a state-dependent outcome. Keep the special knight and preceding state in the note instead of flattening it into a universal best choice.

• Record the assigned knight, equipment, party order, and quest state
• Capture the result and any new scene or trait
• Compare the same quest with a different knight only after restoring the baseline
• Mark a suspected bug or impossible branch as unresolved

The safe verification loop

Use one checkpoint for one question. Start from the same preceding state, test the reported candidate, and write down the result before rewinding. If the result changes after an unrelated dialogue choice, day, party member, or upgrade changes, split the note by state rather than publishing a single rule.

What we will not publish as fact yet

A file-derived minimum is not automatically a player-visible guarantee, and a single successful run is not proof of a universal outcome. This page will keep exact conditions behind an evidence label until they are reproduced in the current build or supported by an official explanation.