FAST ANSWER / ACT 2
Do not overwrite the save before you know which event failed.
Create a checkpoint before the Act 2 investigation, record the available suspects and recent assignments, then replay one choice at a time. A missing murder, a prevented murder, and a duplicated investigation are different outcomes.
- Save before the first Act 2 investigation or traitor clue appears.
- Record the cycle, suspects, regional state, recent quest assignments, and dialogue choice.
- Replay one variable only: suspect order, assigned knight, or response.
- Label the result as triggered, prevented, missing, duplicated, or still unknown.
Why the reports cannot be merged yet
Current public reports describe different behaviors: some players are trying to stop the event, some say dispatching every knight prevents it, and others report that the traitor never triggers. Without the same build, cycle, and preceding state, these are not interchangeable solutions.
What to capture for a reproducible answer
A useful replay log includes the exact Act 2 cycle, investigation stage, suspect list, faction state, available knights, previous assignments, and the final result screen. This makes it possible to tell a route condition from a corrupted or duplicated state.
- Triggered: murder or traitor scene appears normally
- Prevented: the scene is replaced by a documented alternate result
- Missing: the expected hook never appears
- Duplicated: two incompatible investigation hooks appear in one run
Baseline source: official Sovereign Tower page on Steam. Additional reference: Public competitor Act 2 walkthrough. / Public competitor Act 2 murder reference. / Steam current discussions. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: August 15, 2026. Changelog: Added a dedicated high-intent page for the Act 2 murder and traitor search cluster. Kept prevention, non-trigger, and investigation outcomes separate because current reports conflict.