Sovereign Tower Knights: Roles, Routes & Roster
There is no universal best knight. Choose for the request, then track loyalty, satisfaction, traits, preferences, equipment, and route consequences.
Start with the role framework, then open a recruitment page only when you are ready for route spoilers and version boundaries.
Pick by job, not by tier
- Early generalist: useful when the request is not yet fully understood.
- Wit or specialist: useful when the visible requirement is narrow.
- Diplomacy or combat: compare the request’s attribute mix rather than a single stat.
- Special outcome: keep room for hidden traits and event-specific changes.
- Low maintenance: consider loyalty and satisfaction as part of the cost.
Why loyalty belongs in the choice
A high-stat assignment that loses the character may be worse for the next timeline than a safer match. Keep satisfaction and loyalty in the same note as the quest result.
Roster boundary
A research list reports 24 possible knights, but it is a verification queue rather than an official complete cast list. Use the character page for the current role map and keep route-specific names behind the relevant spoiler warning.
The multi-factor knight system is established; exact values, recruitment flags, and the complete roster still need formal-version checks.
Verification status
Still to confirm: Build a versioned role matrix and replay each recruitment route before publishing a definitive tier list.