Round Table directory

Sovereign Tower Knights & Characters

Use one practical directory for recruitment, six core stats, traits, satisfaction, meals and transformation paths—without creating an empty page for every character name.

Current community-documented roster

Current community guides say the release contains 25 Knights, but the published recruitment list exposes only the 24 names below when The Wolf and Rufus are counted separately. We preserve that mismatch instead of inventing a missing name.

AngelicaGobertoGwendanUrsulaDulahan / DullahanChesterThe WolfRufusSilgurBrunhildaTarcusArronGideonAlwenaLigiaChildericZoltaOliverEpicratesEdithDaguez / DaugezGothildVictoriaAri

How Knights work in Sovereign Tower

Knights are the people who convert your decisions into results. When an accepted request becomes a quest, you normally need to choose someone from the Round Table to handle it. Every Knight brings a different combination of attributes, traits, preferences and story context. Building a strong roster therefore means more than recruiting the largest number of characters: you need enough variety to answer different kinds of problems while keeping the group satisfied and available.

The six visible attributes—Strength, Agility, Charisma, Luck, Magic and Wit—are the first comparison point. A physical threat may suggest Strength or Agility, while negotiation may favor Charisma or Wit. Magical situations naturally invite Magic, and some special results use explicit Luck checks. However, quest text can contain clues that make a less obvious Knight the better choice. Personal experience, a useful trait or a connection to the people involved may unlock an outcome that raw attributes do not predict.

Quick recruitment answers

KnightCommunity-tested triggerImportant warning
AngelicaStarting Knight on day 1.Can be dismissed; several animal quests use her special context.
GobertoAppears on day 2.His death is the known trigger for Dulahan.
GwendanAppears on day 3.His debt route can temporarily remove him and change his state.
UrsulaAppears on day 5.Her transformations and Act II behavior are spoiler-sensitive.
DulahanLet Goberto die; the Bloody Magpie is the commonly tested route.See the full Dullahan guide.
ChesterComplete his three-part goose and egg sequence correctly.Listen to the egg clue; see the full Chester guide.
AlwenaIn Act II, have every Knight away, enter the Round Table and keep a seat open.She normally accepts only one-cycle quests unless travel is shortened.
ZoltaWin or cheat the Kutnar race with an unconventional mount, then pay 250 gold.The Wolf is confirmed by several players; Tarcus is not required.
EpicratesFree him or obtain a not-guilty verdict at his trial.Do not send Tarcus if choosing the prison-break route.
VictoriaFollow her quest series after the murder-related route.Multiple current-build reports say she can still leave despite compliance.

How to compare two candidates

  1. Read the stated requirement. Note which attribute appears most relevant and whether the game warns about danger or damage.
  2. Check availability. A perfect candidate who is already away cannot solve the current problem, and sending every flexible Knight away can damage the next cycle.
  3. Consider traits. Traits may support the task, create risk or explain a special result. Do not treat them as flavor text.
  4. Look for personal context. A Knight connected to a location, faction or subject may respond differently from a stranger.
  5. Review satisfaction. Repeated assignments and ignored relationship needs can change the long-term value of a short-term success.

When both candidates remain plausible, decide which absence is easier for the Tower to absorb. This roster-level question matters because Sovereign Tower can present new obligations before previous assignments have returned.

Recruitment is a condition, not just a location

Some characters may become available through audience decisions, quests, knowledge gained in another timeline or a particular state of the court. A trustworthy recruitment guide must therefore record more than “where” a person appears. It should identify the earliest known opportunity, prerequisite decisions, required knowledge, missable choices and the game version in which the route was reproduced.

This is especially important for highly searched names such as Dullahan, Chester and Zolta. The direct guides give the currently reproducible chain and label the evidence as community-tested rather than official. If a patch changes a trigger, the checked date and warning should change with it.

Satisfaction, meals and affinity

Relationship management supports both strategy and story. Meals and conversations can reveal a Knight’s preferences and create opportunities that are unavailable through quest assignment alone. If you are pursuing a particular relationship, pay attention to when free-time interactions appear and avoid assuming that one favorite meal is enough to complete a route. Affinity may interact with story progress, previous dialogue and character state.

MealKnights listed by the current meal guide
Galette-SaucisseBrunhilda, Daguez, Chester, Dulahan, Goberto, Oliver, Rufus, Silgur, The Wolf
Croque-MonsieurChester, Childeric, Dulahan, Gothild, Gwendan, Oliver, Rufus, The Wolf, Victoria
PréfouAngelica, Chester, Daguez, Dulahan, Epicrates, Ligia, Tarcus, Ursula, Victoria
CrêpeAlwena, Angelica, Ari, Arron, Chester, Childeric, Daguez, Dulahan, Gideon, Gwendan, Ligia, Silgur, Zolta
Butter ShortbreadAlwena, Ari, Arron, Chester, Dulahan, Edith, Epicrates, Gideon, Goberto, Gothild, Tarcus
Lion’s TacoBrunhilda, Chester, Dulahan, Goberto, Ursula, Zolta

The community meal guide reports that a preferred meal adds 1.5 affinity and 0.5 to a quest score. Chester and Dulahan appear across many foods, which matches character-guide descriptions that they are easy to feed.

A useful weekly habit is to review every active Knight in three groups: available and content, away on assignment, and in need of attention. This makes roster pressure visible before it becomes a departure or blocked event. It also helps you distribute opportunities instead of repeatedly relying on the same high-stat character.

Transformations and character states

Sovereign Tower search demand includes character transformations and unusual states. The clearest current examples are Dullahan’s mutually exclusive Almor forms, Gwendan’s debt-driven personality change, Ursula’s repeated-death state, the Wolf-to-Rufus change, Arron’s dragon-heart or baby-dragon paths, and Edith’s sword-influenced change after a lethal assignment. Use a protected save because several states are irreversible within a run.

What every completed Knight record will include

  • Recruitment conditions and the earliest verified cycle or opportunity.
  • Strength, Agility, Charisma, Luck, Magic and Wit as displayed in the checked build.
  • Positive and negative traits with practical assignment implications.
  • Quest preferences, aversions, injuries and special outcomes.
  • Satisfaction signals, meals, conversations and confirmed affinity information.
  • Transformation, romance and ending effects with spoiler labels.
Need help with an assignment?Use this page to compare the person, then open the Quest directory to evaluate the problem. A good match requires both sides of the decision.