Knight record
Victoria
Sovereign Tower Victoria is a powerful, route-sensitive Knight whose Enberg and Gothild branches require careful verification.
Victoria Record
Community Tested- Identity
- A formidable Enberg Knight tied to a route-sensitive murder investigation and the Gothild branch.
- Recruitment
- Missable route
- Traits
- Sadistic · Half-Demon · Victoria's Sword · Touchy
- Romance
- Unconfirmed
Recruitment planning
Treat Enberg as a route-state investigation: preserve saves before the trial, assassination, and Gothild decisions. Gothild is a mutually exclusive branch, not a universal prerequisite.
What the Victoria route actually asks you to track
Victoria is not a simple “wait for her audience” recruit. The supplied material places her inside the Enberg murder investigation, where the victim, the possible killer, Knight relationships, and knowledge carried from an earlier timeline can change the next scene. Before accusing anyone, record which Knight is missing, who is being influenced, and which affinity extremes are visible in the current save.
The safest practical approach is to preserve a save before the murder and again before the confrontation. Read the petition and victim details that appear in your own timeline, because another player’s culprit is not a universal answer. This is especially important when testing Victoria and Yohav/Yorhav together: the official patch uses “Yorhav,” while the requested keyword and several guides use “Yohav.”
Recruitment, trials, and the Gothild conflict
The strongest direct recruitment report places Victoria in Act III. At the final branch of her first audience, ask whether a Knight of her caliber would join the Round Table, then complete the trials she assigns and return for the trials-completed audience. The collected guides agree that honesty matters: lying to Victoria or failing one of her requested conditions can close the route, although some reports still describe her leaving after apparently correct play.
Victoria and Gothild should be treated as a branch decision. The supplied sources describe Gothild routes that defeat or assassinate Victoria, including a duel before the investigation closes and an assassination-sponsored route in a later run. Decide whether the current run is testing Victoria’s survival or Gothild’s recruitment before committing to either action; do not treat the two outcomes as a single checklist.
Traits, preferences, and how to use the record
The recurring Victoria profile lists Sadistic, Half-Demon, Victoria’s Sword, and Touchy. The archive also reports a preference for Audacious rule, a dislike of Wise rule, and quest preferences around Duel, Assassination, and Relic Recovery. These details are useful for planning assignments and affinity, but the exact score values vary by source and are intentionally not presented here as fixed universal numbers.
Her sword and Half-Demon identity make her valuable in a route that already contains morally difficult choices. Keep the evidence label in mind: the traits recur across roster databases, while exact timing, trial order, and the effect of every Enberg decision remain community-tested. If Victoria leaves, check the save for incomplete tasks, a dishonest answer, a missing target interaction, or the current-build issue mentioned in the official 1.0.9 notes.
What remains Unconfirmed
No supplied source proves one fixed murderer, one fixed victim, or one universal Victoria sequence across every timeline. A first-run report that prevented the murder through roster timing and Gwendan-related choices is recorded as a community observation, not a guaranteed solution. Likewise, the official fix addresses a Victoria trial mapping problem but does not make every later departure report disappear.
Use this page as a comparison sheet: save before the investigation, document the state you actually see, and separate official patch information from guide claims and comments. That method preserves the most useful part of the Victoria material without turning an unstable route into false certainty.
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 Victoria route spoilers
Official v1.0.9 notes fixed a Victoria trial mapping problem. Community reports still disagree about the simulated-death and assassination sequence, so a fixed trial does not establish one guaranteed recruitment script.