Knight record
Yohav
Sovereign Tower Yohav is an Enberg-linked figure whose spelling and route state differ across current official and community sources.
Yohav Record
Unconfirmed- Identity
- An Enberg figure central to an investigation, assassination, and simulated-death route.
- Recruitment
- Route-dependent candidacy
- Traits
- No stable trait set in the current source archive
- Romance
- Not established
Recruitment planning
This is an Enberg investigation record rather than a normal Knight candidacy. The official patch notes use “Yorhav,” while community material often uses “Yohav.”
Yohav, Yorhav, and an investigation rather than a normal recruit
The requested keyword is Yohav, but the official 1.0.9 patch notes use Yorhav. The supplied sources also include Dodd-like community spellings and route labels, so this page keeps the keyword spelling for search while explicitly preserving the official variant. Yohav is best understood as an Enberg investigation figure tied to Victoria, Arlin, Gothild, assassination, and a simulated-death sequence rather than as a conventional Round Table recruit.
The first question is not “who is always guilty?” Community reports say the murderer and victim can differ between saves. Compare the current missing Knight, influence state, affinity extremes, petition, and carried knowledge before accusing anyone. A noble suspect, a Knight under Demon influence, and an early Victoria-linked outcome all appear in the supplied evidence, but none is proven as the only culprit in every timeline.
The quest-data map and why the answer changes
The collected quest archive separates letters investigation, occult investigation, suspect interrogation, and torture. It then lists direct and indirect Yohav outcomes: assassinating Yohav, simulating his death, or following a larger Enberg assassination route. Those entries are useful for understanding what the game can ask the player to do, but their presence in a quest database does not prove that every branch is available in the same run.
Victoria’s route adds another layer. Reports describe learning that she is behind the murder, reaching the victim or petition chain, and then completing severe trials while remaining honest. Gothild can be recruited through routes that defeat or kill Victoria, making Yohav’s investigation part of a wider roster decision. Save before the accusation, before any duel, and before an assassination quest if the objective is to keep Victoria alive.
Arlin, Victoria, and the current patch boundary
The supplied community guide links Yohav with Arlin and the Enberg relationship map. That relationship evidence helps explain why the investigation can feel different after a rewind or a roster change: the suspects are not just isolated names, and previous knowledge can change which dialogue becomes available. Use the current audience text as the primary clue instead of copying another player’s suspect order.
Official patch notes are the strongest source for build status. They confirm a Victoria trial mapping fix and separately retain an unresolved Victoria issue, which means a repaired step should not be read as proof that every later departure is solved. The page therefore treats spelling, culprit, exact quest order, and the effect of simulated death as community-tested or Unconfirmed where appropriate.
A reproducible investigation checklist
Start by recording the cycle, current Knight roster, influence markers, and the text of the victim or petition. Keep one save before the murder sequence and one before the final accusation. If pursuing Victoria, avoid lying and avoid a Victoria-killing branch; if pursuing Gothild, label that intention before choosing the duel or assassination route.
This process answers the search question honestly: there is no safe universal Yohav culprit from the supplied evidence. What you can reproduce is the method—read the state in your timeline, separate official patch information from community route reports, and mark the result Unconfirmed whenever two otherwise credible sources produce different outcomes.
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 Yohav route spoilers
The murder culprit and simulated-death route can respond to prior Enberg state. Follow the evidence shown in your current timeline instead of assuming one culprit from another run.