Sovereign Tower Victoria: Stats, Route & Bug.

Victoria's current roster profile

The available community roster lists Victoria from the City of Enberg at level 13 with armor 7 and reported Strength 13, Agility 13, Charisma 9, Magic 13, Wit 10, and Luck 9. The page marks Assassination as a known signal and Sadistic as a trait to keep separate from the raw numbers.

• Start with Assassination when the request explicitly points there
• Use the broad stat profile to shortlist, not to skip the quest conditions
• Record whether the trait changes the reward, relationship, or follow-up scene

Check Crowd and Diplomacy conditions

A high starting profile can still be the wrong choice when a quest has a special crowd, diplomacy, relationship, or story condition. Compare Victoria with one alternative from the same preceding state and keep the condition visible in the note.

• Write the visible condition before dispatch
• Keep party, equipment, and timing fixed for the first comparison
• Separate the quest result from the relationship or resource consequence

Do not turn raw stats into a tier list

The purpose of this page is to shorten the decision, not to declare Victoria best for every quest. A result that changes after a dialogue choice, faction state, or party change should be published as state-specific evidence rather than a permanent ranking.

Current route warning

The developer has acknowledged that Victoria and her related quest interactions are not working as expected. Patch 1.0.9 fixes one specific issue where responses to Victoria's trials were mapped to the wrong quest and could make her leave because she was marked as 'lying'. The same official note says the Yorhav assassination and other strange behaviour in Victoria quests still need more testing, so this is a partial fix rather than a stable route.

• Do not use Victoria as the only plan for a Gideon run
• Prefer honest, non-deceptive dialogue while testing
• Do not treat sending Gideon to duel Victoria as a proven workaround
• Save before Victoria appears and record the exact build
• If testing a pre-emptive Victoria death, label it as an unverified workaround
• Check the same state after a patch or fresh run

Patch 1.0.10: the main bug boundary moved

The official 1.0.10 notes add fixes for Victoria ambushing herself and Yorhav not resolving correctly after the assassination. Together with the 1.0.9 trial-response mapping fix, these narrow the old failure reports, but they do not prove that every Victoria route, relationship follow-up, Ambush/Duel state, or Enberg branch is stable.

• Fixed by 1.0.9: Victoria trial responses correspond to the correct quest
• Fixed by 1.0.10: Victoria self-ambush and Yorhav assassination resolution
• Retest whether Victoria stays after the exact trial sequence
• Keep any remaining Ambush/Duel repetition and Enberg stalls as separate replay targets
• Record build 1.0.10, dialogue, result, and whether Gideon's follow-up advances
• Evidence state: official partial fix / route replay pending

Patch 1.0.11: recruited-Victoria Ambush guard

The official 1.0.11 notes fix an issue where Victoria could be sent on Victoria's Ambush while she was already recruited. This closes one invalid assignment state, but it does not confirm the whole Victoria route or erase post-patch reports about departure, Enberg, or other event ordering.

• Fixed: sending recruited Victoria on Victoria's Ambush
• Still test: the exact recruitment sequence and follow-up quests
• Keep Ambush/Duel, Enberg, and false-lie reports as separate replay states
• Record build 1.0.11, save age, NG+ status, and event order
• Evidence state: official assignment fix / route behavior remains replay pending

Post-1.0.10 residual reports: Victoria still says you lied

A Steam discussion opened after Patch 1.0.10 contains several separate player reports that Victoria still rejects the recruitment route: one report describes an older save and a later NG+ attempt, another describes a fresh run with the expected event order, and a further reply reports the same skipped mercenary quests. These reports do not prove a universal regression, but they are strong enough to keep the residual route visible.

• Record whether the run is old-save, NG+, or a completely fresh save
• Log the wounded-man appearance day and whether the two mercenary quests appear
• Capture the exact Victoria choices, the Yohav quest order, and the point where she says you lied
• Repeat once with the same event order and once with the suspected overlapping Yohav/Victoria timing
• Success means the same route completes recruitment in build 1.0.11; failure means the accusation or skipped quest repeats
• Evidence state: multiple community reports after an official partial fix / current-build replay pending

Ambush and Duel: new route reports

Today's monitoring notes add reports of a repeated Victoria Ambush/Duel task and an Enberg route that can stall. These reports fit the developer-confirmed boundary that Victoria interactions are not working as intended, but they do not identify a stable trigger or a workaround. Keep duplicate task text, duel choice, Enberg state, and post-reload behavior in separate fields.

• Record whether the Ambush task appears twice and whether the objective changes
• Test the duel choice from a checkpoint before Victoria's scene
• Capture whether Victoria leaves, remains, or changes relationship state
• Compare a clean run with a prior Gideon/Victoria information state
• Evidence state: community report / replay pending

What still needs verification

The public roster reference does not establish a complete Victoria route, hidden-trait trigger, or guaranteed ending. If a new scene or route appears, capture the exact preceding quest and choice so another player can reproduce it after an update.