What the public sources confirm
Sovereign Tower is a single-player, story-driven Round Table management RPG. The confirmed loop is to manage the kingdom, recruit Knights, assign quests, balance relationships, expand the Tower and use the Demon to rewind time when a decision leads to an unwanted result.
The official Steam description currently lists five Knight stats: Strength, Agility, Charisma, Magic and Wit. Some secondary release material references Luck as an additional quest ability, but the official store copy has not synchronized that wording. The safest 1.0.8 guide therefore treats Luck as a documented conflict, not as a confirmed sixth stat for every player.
FIELD NOTE / CONFIRMED — A Knight is not only a number. Public materials also describe traits, equipment, preferences, relationships and personal story as factors that can affect a quest.
How to read a quest pairing
1. Start with the request
Before dispatching a Knight, identify the stat named by the task and compare it with the available roster. The public walkthrough material is useful as an index of minimum values and special outcomes, but its author notes that parts of the material come from game files and are still being tested. Treat exact thresholds as version-sensitive until checked against the current build.
2. Check the Knight around the number
After the visible stat, review traits, equipment and preferences. The official and community descriptions agree that Knights can have positive or negative traits, and that the right match may improve quest results or unlock a special result.
Patch 1.0.8 changed quest scoring by reducing the penalty for insufficient attributes, increasing the bonus for exceeding a threshold and adjusting Dragon Knight difficulty. The complete formula, the full list of hidden traits and every minimum value are still not fully documented for the current build.
3. Use the current community checks carefully
Community material records explicit stat checks for individual quests, but those rows are not official requirements. The source is marked removed or incompatible, and Patch 1.0.8 changed quest scoring, so this page does not reproduce its exact threshold table as guaranteed advice. Test any community value in the current build before publishing it as a requirement.
4. Keep faction affinity in the decision
The researched material identifies six relationship signals: Merchants, Mystics, Scholars, Nobles, People and Treasury. Affinity choices can reshape relationships and future events, so a quest result should be read together with the faction response it creates.
The exact affinity thresholds, the complete faction outcome table and the long-term value of every choice are not fully documented.
5. Understand Unexpected Outcomes
Unexpected Outcomes are documented as unique results connected to a particular Knight, quest relationship or unlocked state. One public example records sending Angelica to the Clean Keeper Goose quest and receiving a special conversation or result. The complete trigger conditions still need in-game verification.
Do not turn a single community report into a universal answer. Record the build, the Knight sent and the visible choice before treating a result as confirmed.
When a rewind is justified
Official material confirms that the Demon can send the player back to the past while preserving knowledge, opening different dialogue, paths, characters and outcomes. A separate public review notes that rewinding removes the original timeline, so a good result from the first route may be lost.
Rewind preserves knowledge and can open new dialogue, actions, alliances and Knight routes, but it also removes the later events of the abandoned timeline. The exact number of rewinds, any fixed penalty and the full list of consequences are not fully documented. Use the system to test a meaningful branch, not to present an unverified route as guaranteed.
Dispatch checklist
- Identify the relevant Knight stat.
- Use the twelve community checks as versioned leads, not official guarantees.
- Compare traits, equipment and preferences before assigning the quest.
- Check the Merchants, Mystics, Scholars, Nobles, People and Treasury signals.
- Treat exact thresholds and hidden conditions as version-sensitive until tested.
- Record which Knight, choice and timeline produced the result.
The safest public conclusion is simple: match the Knight to the request, read the relationship cost, and keep a note of what the current build actually confirms.