Knight record
Gwendan
Sovereign Tower Gwendan is a Gavault-linked Knight whose debt, affinity, and romance outcomes depend on early decisions.
Gwendan Record
Community Tested- Identity
- A noble-born early Knight whose arrogance, debt, and possible reform shape his route.
- Recruitment
- Route-dependent candidacy
- Traits
- Noble Soul · Arrogant · In Debt
- Romance
- Available (community-tested)
Recruitment planning
His early debt and attitude scenes shape whether the route reads as reform, indulgence, or dismissal. Wise answers are the clearest preference signal in the collected material.
Preferences
- Wise Sovereign
- Dislikes Audacious rule
Early candidacy and the debt question
Gwendan is an early Act I Knight associated with Villador, noble status, sword skill, and a very large self-image. The supplied direct guides describe a candidacy that can appear without a special recruitment quest; if you decline or later dismiss him, the Map Room is reported as a fallback. The archive records the fallback cost as source-specific rather than presenting it as a guaranteed current-build value.
His route becomes more complicated because “In Debt” is not just background flavor. The collected sources connect debt payment or resolution with a humble, reform-minded direction, while leaving the debt unresolved supports a pretentious version. Treat those as two narrative states, not as a simple good/bad label: the choices affect later conversations, quest suitability, and the tone of his relationship scenes.
Preferences and route planning
The recurring profile lists Noble Soul, Arrogant, In Debt, Seductive, and Fear of the Dark. Gwendan likes Wise rulers and dislikes Audacious rule in the supplied character sheet. The quest archive favors competition and reports problems with Relic Recovery, Assassination, and some unreformed assignments. A practical court plan therefore gives him visible, social, or competitive work while keeping an eye on whether the reform route has changed his performance.
The guide material also reports a Gwendan-related murder investigation. Some runs intervene by paying debt, investigating the tower event, or dismissing a Knight and then using the next timeline to test a different state. Those steps are not interchangeable with ordinary recruitment, so preserve a save before the murder sequence instead of assuming that a debt payment alone protects the entire roster.
Affinity and romance evidence
The first heart scene places Gwendan on the Sovereign’s throne, where listening to his ideas can raise affinity and dismissing him can lower it. The second heart scene centers on his complaint about Tower soup and opens background material about fear of darkness and a traumatic childhood memory. The supplied route reports distinguish wise, kind, and tyrannic responses, so read the response labels instead of choosing only by tone.
Later scenes split into pretentious and humble paths. The pretentious version keeps his charm and self-satisfaction in the foreground; the humble version connects debt with Brimwood, imprisonment, and found family. The archive supports a romance route for Gwendan, but it does not publish one official affinity threshold or one universal cost table. If a number appears in a community source, treat it as a tested observation for that run.
What to mark Unconfirmed
The official character introduction is strong evidence for Gwendan’s Villador identity and noble framing, but it does not document recruitment mechanics. Exact debt amounts, murder-protection timing, and the order of every humble-path scene conflict across the supplied guides. Keep those details visible as route reports rather than silently merging them into one script.
For a reliable first pass, recruit him early, note whether the court presents debt dialogue, and save before paying, dismissing, or investigating. Then use the romance page for cross-route warnings: Gwendan’s relationship state can interact with other Knights, and the collected material reports penalties without proving one universal multi-romance formula.
How to read this Knight record
Facts repeated by an official announcement, a patch note, or more than one independent roster source are presented as the stable profile. Recruitment steps, affinity choices, and transformation claims are separated because they come from different evidence classes. A community-tested label means the supplied material describes a repeatable player result; it does not mean the developer has published the rule.
When a page says Unconfirmed, keep the claim visible but do not build an entire run around it. The safest comparison is to note the cycle, county or city state, living roster, current quest text, and whether Demon Power has been used. That record lets you compare two saves without turning a route report into a promise.
A practical save plan
Make one save before the first recruitment gate, one before any quest that can kill, dismiss, transform, or relocate the Knight, and one before a romance or political commitment. Read the next audience after the cycle advances before loading an older file: several supplied routes depend on what the game remembers, not only on the choice that appears on screen.
This approach also protects the evidence boundary. If your result differs from the route report, record what changed instead of silently correcting the page in your head. The wiki can then distinguish an official fix, a high-confidence repeated result, and a single-run observation while still giving you a usable next step.
Show Gwendan route spoilers
Players report that paying or resolving the debt can lead to a reformed outcome, while dismissive choices can end the relationship path. Exact affinity thresholds are not exposed by an official ruleset.