Sovereign Tower Assassinated Knights: What to Track
An assassination result is a timeline state, not just a lost unit: it can alter satisfaction, roster capacity, relationships, quest coverage, and later choices.
Before committing to a risky quest, record the knight, visible danger, faction context, and whether a rewind could preserve a different outcome.
Treat death as a state change
- Record the final task and assigned knight.
- Note faction, relationship, and satisfaction context.
- Check whether the death removes future quest coverage.
- Save the last decision before the result if a rewind is available.
- Compare the later timeline instead of assuming a reload-like recovery.
What not to promise
A high attribute is not proof that a knight cannot be assassinated. The current evidence does not establish one universal bodyguard, dialogue choice, or resource threshold that prevents every reported death.
Show the test plan
A safer verification route
Use one controlled run to reproduce the reported result, then rewind once and change only the suspected choice or assignment. Keep the patch and end-screen wording in the note so a future guide can separate route logic from coincidence.
The research supports assassination as a meaningful route consequence, but it does not establish a universal trigger table or prevention recipe.
Verification status
Still to confirm: Replay the highest-risk death reports and record the exact task, choice, version, recovery, and epilogue effects.