Knights are the people who turn a Sovereign Tower plan into an outcome. The official Steam page describes a court of eccentric heroes who can be recruited, assigned to Quests, and managed around the Round Table. A recent PC Gamer feature adds an important practical detail: a Knight’s visible ability score is only part of the decision, because traits and preferences can remain hidden until you learn more about the character. This hub is a roster guide for making those decisions without pretending that an early community table is a permanent database.
Read the roster as several layers
Start with the labels the released game actually shows. The Steam description names Strength, Agility, Charisma, Magic, and Wit as Quest-relevant statistics. PC Gamer also reports Luck in its discussion of mission checks. That difference is a reason to trust the current tooltip over a copied list. Write the exact stat names and values in a personal note, then check whether a mission asks for one stat, a combination, or a requirement hidden behind a story prompt.
The second layer is equipment. A lower-stat Knight may still be a sensible candidate when the right item changes the risk or fills a gap. Equipment can also be scarce, so record who currently holds it before moving the item. The third layer is the Knight’s personal traits and preferences. PC Gamer describes positive and negative attributes that can alter a Quest and separate preferences that influence satisfaction. Keep those effects separate: a favorite meal is not automatically a combat bonus, and a fear or dislike should not be converted into a universal ban without seeing how the game applies it.
Recruitment is a decision, not a checklist
When a new Knight becomes available, note the context that brought them to the tower. Was the character offered during an audience, introduced by a story beat, or found after a Quest? The public sources confirm recruitment as a central feature but do not provide a complete official roster route. That means a guide can teach readers how to evaluate a recruit while leaving exact names and unlock sequences to dated observations.
Before accepting or relying on a new recruit, compare the person with a real need in the current court. A character who covers a missing stat, supplies a new trait interaction, or frees an existing Knight for another mission may be more valuable than a superficially stronger replacement. Check whether the game shows capacity, availability, relationship, or story conditions. If a condition is not visible, label it unknown and avoid telling players to reject a recruit just because a community sheet has not recorded them.
Hidden information and advisors
Hidden traits are a core source of uncertainty. The PC Gamer launch feature says the player can get to know Knights or use an advisor to spy on them, which creates an information choice before a risky Quest. Use that action when the expected cost of ignorance is high: a mission has a narrow requirement, the Knight has an important item, or the story consequence looks difficult to reverse.
Do not reveal a hidden trait in a guide without a source note. Community lists can be useful for cross-checking, but the current Knight-list discussion is a player-maintained fallback and may contain mistakes, missing characters, or data extracted from files that the developer later changes. If you publish an observation, include the Knight name exactly as displayed, the build date, the observed trait, the action that revealed it, and whether the result was tested more than once.
Satisfaction, preferences, and relationships
Preferences matter because Sovereign Tower is not only a stat puzzle. A Knight can succeed on a Quest and still be unhappy with the assignment, the environment, the ruler, or the way the court treats them. The public preview describes character conversations and relationship-oriented play, while the launch feature separates preferences from direct Quest effects. This suggests a planning habit: evaluate both mission probability and the social cost of repeatedly ignoring a character’s needs.
A preference should change the question you ask, not dictate every action. If a Knight dislikes a place but is the only safe answer for a critical mission, send them with a note about the trade-off and plan a better follow-up. If a less obvious candidate can meet the requirement while improving trust or satisfaction, that may be the stronger long-term assignment. Avoid claiming that a romance, evolution, or relationship threshold is guaranteed unless the released game or a well-documented test confirms it.
Building a balanced court
Balance means covering different kinds of problems, not making every Knight identical. Keep at least one dependable candidate for common visible stat checks, one flexible candidate with useful gear, and one character whose traits you are still learning. This leaves room for the unexpected audience request that makes a narrow roster fail. The exact roster size, best Knight, and optimal order are not established by the official page, so this hub intentionally avoids a tier list.
When a mission arrives, compare three questions. Can this Knight satisfy the visible demand? What hidden trait or preference could change the cost? What does sending them prevent the rest of the court from doing? The third question is easy to miss because the dispatch screen focuses on the selected character. A strong-looking assignment can be a bad day plan if it leaves no answer for the next request.
How to keep a roster note useful
Use a table with columns for name, visible stats, known traits, preferences, current gear, source, and last checked date. Do not mix Demo observations with base-game notes: AppID 4422320 is a separate product from the 4113940 release. Mark file-derived claims as community research and in-game observations as tested rather than official. When a patch changes a label, preserve the old note only as history and update the current row.
The community demand for a complete Knight list is real, but a complete list is not the same as a reliable list. This site can safely publish the method first and add verified roster rows later. If a reader reports a correction, request the in-game text, the mission context, the platform, and the date. That evidence is more useful than an unsupported assertion that a Knight is “always best.”
Sources and scope
- Sovereign Tower on Steam is the identity and feature source for the base game.
- PC Gamer’s launch feature reports the daily assignment loop, traits, preferences, stats, and equipment behavior.
- PC Gamer’s preview supplies additional preview-stage context about recruitment, gear, and relationships.
- Community Knight-list discussion is fallback evidence only and is not treated as official.