Knight record
Ursula
Sovereign Tower Ursula is an immortal, route-sensitive Knight whose deaths, affinity, and story state can change over time.
Ursula Record
Community Tested- Identity
- An immortal, musically inclined Knight whose deaths can alter her long-term state.
- Recruitment
- Route-dependent candidacy
- Traits
- Jaded · Immortal · Ritual Subject · Loner · Musician
- Romance
- Available (community-tested)
Recruitment planning
Her immortality means a death is not always a conventional permanent loss, but repeated deaths can change her condition. Track each return instead of assuming the same state.
Recruitment and the value of an unusual Knight
Ursula appears early at court as a wandering Knight from Brizh who is bored by ordinary work and wants unusual experiences. The supplied recruitment guides describe an audience built around that boredom: accept her request to join the Round Table, or use the Map Room fallback if the audience is missed. The exact fallback cost is a reported value, not a promise that every build uses the same economy.
The recurring profile lists Jaded, Immortal, Ritual Subject, Loner, and Musician. Ursula likes Audacious rule and dislikes Wise rule. She likes Relic Recovery and dislikes Diplomacy and Magic Involved in the supplied quest tables. Use those signals as planning aids, while checking the current quest sheet before sending her because the route archive also records special outcomes that can change her state.
Affinity scenes reveal the immortal route
The first heart scene uses a strange drink and Firetwig to test whether the Sovereign will share an experience. The supplied guide records affinity gains for recognizing the drink, asking what Ursula is running from, and committing to a second drink, along with Audacious or Tyrannic style changes. The second heart scene turns to music, her lute, Ironluth, and the hidden Musician trait; quiet listening is treated as a valid route into the conversation.
The third heart scene connects Ursula’s childhood in Moonvale and Pinemaze Forest with a curse associated by the source with her mother. Her marks, her decision to leave, and the later sense of belonging in Brimwood are all part of the same personal history. The fourth heart scene is death-gated: the supplied guide says Ursula must have died at least once and reached a high affinity state before the memory-loss conversation appears.
Death, return, and the cost of experimentation
Ursula’s Immortal trait means that one death does not necessarily remove her permanently. The collected sources describe a return and then a worsening state after repeated deaths, including a Zombie Ursula outcome after three deaths in one guide. That transformation is why the page says “immortal” does not mean consequence-free: the character can come back while losing important qualities of the original state.
The romance event continues the moon, snow, and Moonvale imagery into an explicit commitment. A player can remain quiet, stand beside her, remove a snowflake, and choose whether to reciprocate. The supplied romance material supports Ursula as a partner, but the exact relationship penalties for overlapping romances are reported in comments and are not promoted as an official formula.
Current-build caution
The official 1.0.9 material provides a useful patch boundary, yet the supplied archive still includes reports of inconsistent death, return, and investigation behavior. Do not infer that every transformation or affinity gate must appear in exactly the same cycle. Capture the current state before intentionally killing Ursula, sending her on a long quest, or using a Demon rewind.
For a stable comparison, keep a living save, a first-death save, and a later-route save. This preserves the strongest part of the research: Ursula is a high-Magic, relationship-heavy Knight whose route is designed around novelty and mortality, while the full transformation matrix remains Unconfirmed where the sources disagree.
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 Ursula route spoilers
Route accounts describe changing post-death forms and relationship consequences. Exact death thresholds and every transformation rule are not consistently reproduced.