If a Knight is assassinated, the current formal-release evidence suggests the killer and victim depend on Knight approval and relationships rather than a fixed cast. Investigate the event, rewind to before it, and look for the changed Alwena noise event; the “Confront the murderer” branch is reported to prevent that round's murder. The full rescue route is still not fully documented.
What the sources confirm
The public material describes the murder and the Demon rewind system. Current community testing reports that the least-liked Knight may become the murderer and a favored Knight or romance target may become the victim. The report is useful for route discovery but does not document the full formula.
How to use this information
Record which Knight was affected, the relationship state and the preceding choices. After rewinding, inspect Alwena's event and compare the available Omniscient options. Do not assume the same killer, victim or outcome will appear in another timeline.
Why this query matters
The player problem is not solved by a fixed save code because the game treats timeline changes as narrative choices. Dynamic relationships, investigation and rewind all matter. That is why this page should describe the current branch logic instead of promising a universal rescue sequence.
Known limits
The approval formula, all possible killer/victim combinations, rescue conditions, number of rewind steps and permanent consequences are not fully documented. The researched sources do not verify a universal “save every Knight” path. Do not invent a fixed timeline order.
Source filter
PC Gamer and DigitalChumps both support the assassination consequence and the role of rewind. Neither gives a complete step list. The page filters those sources into a safe response and marks all specific rescue details not fully documented.
Last checked: August 12, 2026 · Patch 1.0.8. Community routes, exact values and live platform data can change by build.