Sovereign Tower All Knights: Who to Send, Recruit & Stats.

Answer first: choose a shortlist, not a favorite

If you landed here from a search result, do not begin by reading all 24 rows. Read the quest pressure point, choose one specialist, and use the condition column to decide whether the assignment is safe. The roster becomes useful when it narrows a decision rather than adding another lore wall.

• Physical pressure: start with Daguez
• Scouting or agility: start with Ari or Silgur
• Magic pressure: start with Edith, Epicrate, or Ligia
• Wit plus armor: start with Childeric
• Route or recruit question: open the relevant character note before dispatching

Knight stats and tier list: rank by task, not by hype

There is no independently confirmed universal best-knight tier list. Use the visible six-stat profile and specialist signals to build a task-based shortlist: a knight can be excellent for one quest pressure point and a poor choice for another. Treat starting stats as a roster reference, not a promise that every result will succeed.

• Physical pressure: compare Strength and armor before using a general tier label
• Scouting or speed: compare Agility, relevant traits, and the quest's party requirement
• Magic or ritual work: compare Magic, Wit, and any named-knight branch
• Diplomacy or relationships: include Charisma and the relationship cost
• Evidence state: community roster reference / no universal tier list confirmed

Hidden attributes, favorite meals, and transformations

Two current public roster references expand the lookup beyond recruitment: Raider King's community list covers hidden attributes, stats, favorite meals, and portraits, while an independent GG Guides roster guide organizes recruitment, transformations, and favorite meals. Use these as practical community references when deciding who to send, but verify the exact trait, meal effect, portrait state, and transformation in build 1.1.0 before treating them as guaranteed mechanics.

• Hidden attribute: check the trait against the quest pressure point
• Favorite meal: record the visible meal or affinity change instead of assuming a universal bonus
• Transformation: keep the trigger and the resulting state in the same knight record
• Portrait or stat change: capture before and after values when a route changes the roster
• Evidence state: two public guide references / verify in build

Patch 1.0.11: roster lookup remains task-based

The official 1.0.11 notes do not publish a new all-knights list or universal ranking. They do include smaller presentation and gameplay corrections, including Arron's portrait alignment and a Papillon stat change. Keep those patch notes separate from recruitment routes, hidden traits, meals, transformations, and the reported 25-knight achievement target.

• Use this page for who-to-send, recruit, and stats lookups
• Treat official patch corrections as version boundaries, not a tier list
• Record any Arron portrait or Papillon stat change separately from a recruit trigger
• Keep hidden attributes and transformation conditions as community reference / verify in build
• Evidence state: official patch scope / complete roster mechanics remain unverified

Patch 1.1.0: Alwena's departure now has follow-up text

The official 1.1.0 notes add follow-up dialogue after Alwena's death explaining that she stepped away from being one of the knights, and disable the intendancy the following morning. This clarifies the visible state after her departure, but it does not establish a new recruitment, dismissal, or hidden-attribute rule.

• Added: Alwena follow-up dialogue after her death
• Clarified: she stepped away from the knight roster
• Changed: the intendancy is disabled the next morning
• Retest the roster, open-slot, and intendancy state in build 1.1.0
• Evidence state: official patch note / wider recruitment and attribute mechanics remain verify in build

How to use the table

The table is a first-pass dispatch tool. Read the six stats in the order shown, then use the known likes or signal to break ties. A question mark means the source reports a variable value, not a zero.

• Use Daguez as a physical specialist, not a generalist
• Use Ari or Silgur as early agility-and-scouting candidates
• Use Edith, Epicrate, or Ligia when Magic is the pressure point
• Use Childeric when armor and Wit matter together
• Treat Victoria as a late, high-profile candidate rather than an automatic answer

Conditions worth checking before you commit

Several rows carry a branch condition rather than a simple recruitment answer. The community reference reports Dulahan after Goberto's death, Arron's Dragon Knight story progression, and special gear or mount effects for several knights. Recent corrections also add a Goberto tournament evolution, an Alwena recruitment condition, and possible Edith and Oliver story changes. These reported triggers are not guaranteed in every build.

• Record day, location, open table slot, and preceding quest
• Capture the first appearance or follow-up scene
• Check whether a rewind reproduces the same trigger
• Keep a missable or death condition marked as a player-reported lead until verified

Do not turn story upgrades into duplicate knights

Keep base and upgraded states in the same roster row. The source reports Arron gaining Dragon Knight and Gwendan moving from Noble Soul toward True Noble Soul. Newer community corrections also point to a Goberto tournament upgrade, an Alwena recruit state after Act 1, and story-dependent changes for Edith and Oliver. These are useful leads, but the exact requirements and wording should be checked against the current game build.

• Trigger: what exact event caused the change?
• State change: what trait, stat, or ability changed?
• Payoff: which quest first became easier?
• Confidence: in-game verified, community reference, or unknown?

Fresh community corrections to test first

The latest discussion adds several high-intent questions that the original roster missed. One player reports that Alwena can become a knight after Act 1 when the current knights are away and a table slot is open. Other replies describe Goberto's tournament evolution and possible Edith and Oliver story evolutions. Keep each one as a separate test card instead of combining them into a single promise.

• Alwena: after Act 1, send all current knights away and keep a table slot open
• Goberto: test the final tournament duel and record armor, stats, and party protection
• Edith: test the reported kill-quest personality change and any lost negative perks
• Oliver: check whether the mage state is a story evolution and when it appears

Detailed knight reports: lookup, then verify

The public Steam Meet the Knights discussion adds player-reported traits, route timing, and assignment behavior that are useful for an all-knights lookup. It is not an official roster table or balance specification, so use it to choose the next test and compare the result with the visible in-game roster.

• Use the report to identify a candidate knight, trait, or route question
• Record the exact quest, cycle, open table slot, and preceding assignment
• Compare the reported behavior with the current build's menu and result screen
• Keep hidden attributes, favorite meals, transformations, and recruitment gates labeled community reference / verify in build

Daguez recruit: low People satisfaction is a lead, not a threshold

Two public Steam discussions point to the same practical question: Daguez may appear after a civil-unrest or rebellion event when People satisfaction is low, followed by the choice to knight one of the rebels. The reports disagree about whether this is Act 2 or Act 3 and whether the trigger is below 20, below 30, or a larger gap from other factions. Do not ignore every urgent quest or rely on a fixed threshold; record the state and reproduce the prompt instead.

• Track People satisfaction before and after urgent quests, alongside the other faction values
• Record the act, cycle, visible event title, and all three response choices
• If the knight-one-rebel choice appears, capture the exact wording and Daguez result
• Compare below-20, below-30, and relative-gap states from protected checkpoints
• Evidence state: conflicting community reports / needs-verification / replay pending

Roster pressure: dismiss, bench, or open a slot?

A current Steam discussion asks for more knights or a way to dismiss them. That is a real roster-management intent, but the discussion itself does not establish a universal dismiss or bench mechanic. Test it separately from the Alwena open-slot lead so an unavailable knight is not mistaken for a removed knight.

• Record the roster count and open slots before sending everyone away
• Check whether the game offers dismiss, remove, bench, or only temporary unavailability
• Compare the next recruitment opportunity with a full roster and an open slot
• Capture the exact menu wording and build before marking the behavior confirmed

Hidden recruit routes to test

Several high-intent searches ask for a recruit name, but the real answer is a branch state. These reports have enough concrete actions to test while still needing current-build confirmation.

• Alwena: after Act 1, send current knights away and keep a table slot open; record whether she offers to join
• Brunhilda: protect the Gavault branch, then compare the arrest-mother and abandon-revolution choices
• The Wolf / Rufus / Silgur: use the Groveshire beast choice and Angelica assignment as separate route tests
• Edith: ask in the Moonvale route about a knight who understands both dragons and magic; the exact option is disputed
• Oliver: avoid killing the prologue attacker, then treat the Act 2 appearance as a lead rather than a fixed cycle
• Zolta: use the strongest current lead—The Wolf plus Cheat in the third/final Kutnar quest, accept the lowest-tax result, check next cycle, and keep 250 gold

Recruit route, cheat route, and patch notes are separate

The latest material combines three different question types. Zolta recruitment asks how to make her appear and pay 250 gold; the cheat achievement asks which choices were used across the three Kutnar matches. Ursula's 1.0.9 timing change and Ligia's 1.0.8 lock fix are version notes, not recruitment recipes.

• Zolta recruit test: use The Wolf or a Mathilda's Lion rider in the final match, then check the next cycle
• Zolta cheat test: compare Tarcus in match one, the two-knight trap in match two, and Wolf/Lion in match three
• Keep the 250-gold payment and the Steam pop-up in separate evidence fields
• Ursula: retest summon timing after the 1.0.9 intervention change
• Ligia: keep the father-survival condition as a community route until reproduced
• Evidence state: official patch note plus community route reports / replay pending

1.0.9 conflict queue: Zolta, Oliver, and Dulahan

New community observations are useful because they change what a player should test, but they do not replace the existing route labels. Keep the no-cheat Zolta report, Oliver's cross-run recruitment report, and Dulahan's helmet stat report separate from the stronger roster facts.

• Zolta: compare the established final-match Cheat route with a normal-win route; do not write either one as the only condition
• Oliver: record whether a prologue death still blocks recruitment after Try Again or a new run; the current report is not independently reproduced
• Dulahan: capture before/after WIT, LUCK, and CHA values for the helmet route; do not infer them from the human-body route
• Evidence state: conflicting community reports / verify in build

Zolta: a usable Kutnar route lead

The strongest current community reports use the third/final Kutnar Derby quest: send The Wolf, choose Cheat, accept the lowest-tax outcome, and check the next cycle for Zolta. The reported recruitment cost is 250 gold. Second-round or any-round cheating remains a weaker alternative report, while the current route does not require Tarcus. Treat the route as near-confirmed community evidence until the site has a direct current-build reproduction.

• Reach the third and final Kutnar tournament quest
• Send The Wolf and choose Cheat
• Accept the lowest-tax result if that branch appears
• Check for Zolta the next cycle
• Keep 250 gold available
• Do not add Tarcus unless comparing the alternative route
• Capture the recruit screen and the exact cycle

The next verification pass

Use the table to choose three high-intent checks: one conditional recruit, one story upgrade, and one disputed hidden trait. Those checks will improve the guide more than adding another page of generic questions.