Sovereign Tower Unexpected Outcomes — What They Mean

Official examples with historical reference1.2.0 notes; August 31 task snapshotSpecific pairings and task records compared October 20, 2026. The older Demo discussion below is not a release-build formula.

What an Unexpected Outcome safely means

Result	Safe conclusion	Unsafe conclusion
Critical Failure	The assignment went badly	One visible stat alone caused it
Critical Success	The assignment went especially well	You have found the whole formula
Unexpected Outcome	A special result occurred	Any future attempt will repeat it

The official game material names the three broad results. The community discussion adds a possible pairing clue, but it should be checked against the result screen in the current game.

For developer-confirmed examples beyond that older discussion, start with the 1.2.0 Knight–quest additions. Named examples are stronger evidence than assuming every pairing is random, but they still do not reveal a universal score formula. Keep the live debrief with the exact quest and Knight when comparing attempts.

Official patch examples1.2.0October 15 announcement checked October 20, 2026; added outcomes not independently replayed.

Three named pairings to check on 1.2.0

• Alwena → The great duel: the official note identifies the duel against Childeric and a changed follow-up audience. A different conversation is therefore part of the documented addition; it does not by itself prove a particular recruitment result. Check Alwena's dispatch preparation if she refuses the task.
• Gideon → Bucolic diplomacy: the older record lists a Gwendan-specific outcome. The developer separately adds one for Gideon, so finding only Gwendan in the old card does not rule out Gideon's newer result.
• Gideon → The silver feathers: the older card lists a Silgur-specific outcome. The 1.2.0 addition is another pairing, not evidence that you must replace Gideon with Silgur to reproduce a newer debrief.

The notes name these pairings but do not publish their rewards or all activation conditions. Use the current debrief for those details; the historical card helps identify the quest, not fill in the newer reward.

Compare the consequence, not just the result label

An older reference example is The silver cat with Angelica. Its special result includes an affinity reward for Angelica that is absent from the ordinary result. That is a reason to compare the actual reward lines when a specific Knight matters; it is not a promised mount drop or a general affinity-farming formula.

For a placement example, the old From plains to summit record distinguishes ordinary second place from a non-equine special win. A successful assignment is not automatically the race result you wanted. The Zolta guide explains the practical recruitment consequence with major spoilers.

Record the useful evidence

Record after the result	Why it helps
Exact quest and Knight	Preserves a possible pairing to test later
Visible stat match	Stops you from attributing everything to one number
Known attributes and equipment	Keeps possible influences visible
Earlier court choice or route state	Helps separate the current timeline from a changed one

Use this as a notebook, not as a calculator. The developer doesn't publish thresholds, percentages, or a universal list of special pairings.

Retry with one change

1. Choose one earlier decision or assignment detail to test.
2. Keep the rest of the known setup as consistent as possible.
3. Re-check Knight availability, equipment, and information after a rewind.
4. Compare the new result with your previous record.

Common mistakes

• Calling Unexpected Outcomes random without checking the result text.
• Treating one community-reported pairing as a complete Verified system.
• Changing the Knight, equipment, and prior Audience choice together.
• Using Demo discussion details as a guarantee for the current release build.

Evidence limit

Official scope: the game page names the result type and 1.2.0 notes identify particular new Knight–quest outcomes. Community-reported scope: the older discussion's explanations of pairing and result-screen clues. Full triggers, numerical weights, and a complete pairing list remain unconfirmed.

For the full assignment checklist, see quest assignment and outcomes. Use Knight stats and traits to separate visible stats from attributes and preferences, then use Demon Power and rewinds to compare timelines.