The short answer
The Act II murder is not locked to Angelica, Gideon, or any other single pair. Players comparing different runs report that both the culprit and intended victim change with the relationship state of that timeline. That is why guides naming one universal killer are unreliable.
The repeatable solution is:
- Allow the first timeline to reveal who died and who was responsible.
- Use Demon Power to return to a cycle before the murder.
- Choose the knowledge-based option that confronts the culprit.
- After the audience phase, check the character-event indicator at the Round Table and finish that conversation.
Why the murderer changes
Community reports consistently describe this event as relationship-driven. A commonly reported pattern is that the Demon influences a poorly regarded knight and targets a highly regarded or romantic knight. That pattern helps explain different screenshots, but it is not an official Affinity formula and should not be used as a fixed numerical threshold.
Use the names shown in your own failed timeline. If your victim is not the person named by a forum post, your save is not broken—the game selected a different pair from your relationships.
Step by step
1. Record the failed timeline
When the murder fires, note three things before rewinding:
- who was killed;
- who the story identifies as the culprit;
- the cycle immediately before the event.
The bad result supplies knowledge that the Sovereign did not have beforehand. Rewinding before you know the culprit can leave you without the informed response needed to change the event.
2. Rewind to before the murder
Open Demon Power and choose the latest available cycle before the killing. Going back farther is usually unnecessary and increases the number of assignments, audiences, injuries, and relationship changes you must reproduce.
Demon Power operates within the current Act. If you have already advanced beyond Act II, the ordinary rewind menu should not be treated as a free cross-Act save selector. Read the Demon Power guide before moving forward.
3. Confront the culprit
Replay toward the event and use the newly available response that confronts the character your first timeline exposed. Player reports describe slightly different dialogue requirements: one player could confront immediately, while another needed a response compatible with their current Archetype or approval state.
That disagreement is why this guide does not publish fake button text or an Affinity number. The dependable signals are the culprit's identity from your timeline and the appearance of an informed confrontation option after rewind.
4. Complete the follow-up character event
After audiences resolve, inspect the Round Table for the character-event notification, reported at the lower-left area of the interface. Open the conversation and finish the intervention. Players who followed the confrontation route report reaching a result with no replacement death.
Do not stop after selecting the audience response. The follow-up event is part of the rescue flow.
5. Confirm the whole roster survived
Advance only after checking both the original victim and the rest of the knight roster. If the intended victim survived but another knight vanished, you most likely took the lock-door diversion rather than resolving the culprit's action.
If the confrontation option is missing
Work through this order:
- Confirm that the murder already happened once and the culprit was explicitly revealed.
- Confirm that you rewound to a point before the murder, not merely before its aftermath.
- Replay the relevant audiences and inspect every knowledge-marked response.
- Check whether your current Archetype or relationship state exposes a differently worded confrontation.
- If only a “lock the door” style warning is available, do not assume it is the complete rescue route.
There is not enough verified evidence for a universal stat build that forces the confrontation. Rebuilding the learned timeline is safer than changing random stats in search of an invented threshold.
Common mistakes
- Following a solution that hardcodes Angelica as the victim or one knight as the murderer.
- Rewinding before the first timeline has revealed the culprit.
- Warning only the victim and causing a different knight to die.
- Ignoring the Round Table character event after the confrontation.
- Rewinding farther than needed and changing the relationships that selected the pair.
- Treating a player's lowest/highest Approval theory as an official numeric formula.
Evidence limits
This route was checked for Sovereign Tower 1.0.8 on August 12, 2026. The official store establishes time rewriting as a core system. Two independent Steam discussions agree on the investigate → rewind → intervene structure and on a route where nobody dies. They also show that names and some dialogue conditions vary, so this guide preserves the common procedure instead of inventing one fixed script.
Sources
- Sovereign Tower on Steam — official Demon Power and consequence premise.
- How to Save discussion — variable pair, lock-door diversion, confrontation, and follow-up event.
- Act 2 Traitor/death discussion — independent rescue-route cross-check and dialogue-condition conflict.