Field guide
Demon Power Guide
How rewinds change choices, and why corruption is not consequence-free.
How to use a rewind purposefully
The official Steam description presents the Demon as a way to return after a reign goes wrong while keeping knowledge. The useful question before rewinding is specific: which audience, quest outcome or county choice do you want to revisit?
- Record the decision you want to change and what happened afterward.
- Revisit the earlier point through the Demon when the game offers it.
- Look for dialogue reflecting knowledge gained in the previous timeline.
- Check the new quest and audience sequence before assuming the changed choice completed the whole route.
For an example, Gideon's origin route uses knowledge of Gavault and Groveshire to seek reconciliation. Learning a fact and recruiting a Knight are different states, so one new dialogue option does not guarantee every later scene.
Does Demon Power have consequences?
Yes. In the Steam discussion about endings and corruption, the original poster first describes a harmless interpretation, then later says that interpretation was wrong because the corrupted-Sovereign flag affects some branches and choices.
That correction takes precedence over repeating the initial reassurance. It does not document every affected dialogue or establish that every use immediately produces a visible penalty. The supported conclusion is narrower: do not plan a route on the assumption that corruption has no gameplay consequences.
What carries over?
| State | What the evidence supports |
|---|---|
| Learned information | The official premise explicitly supports revisiting events with knowledge and new choices. |
| Inventory and Golden Key | No universal carry-over rule is established here; check the new timeline's inventory and quest state. |
| Knight recruitment, relationships and county alliances | Re-read the current state rather than assuming a complete roster carries over. |
| Every Sovereign stat | Patch 1.0.10 fixed an issue involving stats not resetting; an old bug is not a permanent mechanic. |
The Golden Key guide should be checked against the current quest and completion report after revisiting an earlier point. Knowing where a route leads is not the same as already owning its reward.
Reported Demon epilogue thresholds
Show Demon epilogue thresholds
Raider King's ending guide reports the following older pattern:
| Reported uses | Reported epilogue pattern |
|---|---|
| 0 | No Demon epilogue |
| 1–19 | A lighter Demon scene |
| 20 or more | The lighter scene plus a darker scene |
The guide treats Tower Destruction as an exception to the normal epilogue sequence. These thresholds are a community account, not a complete official rule for corruption, and they have not been retested by this wiki on 1.1.0. The available evidence does not establish a universal reset scope for every counter.
Read the political endings and character layers separately. Avoid collapsing a final Demon scene, a corruption flag and the main political choice into a single good-or-bad ending meter.
Patches that change older rewind advice
The official 1.0.10 notes fix Oliver failing to join after a previous kill was followed by mercy in another run, a Gideon NG+ softlock, and the Sovereign-stat reset issue. They also correct some persistent Knight armour and judgment state.
Those fixes invalidate advice that presents the affected old bug as an unavoidable permanent lock. For Oliver, the practical foundation remains sparing the opening attacker in the timeline being pursued.
Patch 1.1.0 adds ending branches and corrects character-route issues. A route account written before those patches needs its date considered even when the broad rewind idea remains useful.
Before spending another use
Choose a decision worth revisiting, record the current roster and relevant quest state, and leave time to read the resulting audience. Use the early walkthrough for a concrete example of one author comparing assignments; use the Knight directory when the intended change is a recruit or transformation.
Sources
The official store supplies the rewind premise. The Steam discussion supplies the original poster's correction. Raider King's ending guide supplies the attributed epilogue thresholds. None of these sources alone establishes a complete, current-version carry-over table.