Sovereign Tower NG+ Guide: Try Again & Carry-Over.

No Try Again or NG+ after the ending?

No universal fix is verified. An October 3 Steam report describes a manually saved run with no Demon Power use, Angelica obtaining the Golden Key and an Epicrates ending, but no NG+ afterward. A single report cannot identify the cause or establish a hidden prerequisite; neither manual saving nor that route should be called the culprit.

• Keep the original completed save and an offline copy before trying a menu action
• Record the installed build, platform, ending title and every option actually shown on the ending screen
• Distinguish an absent Try Again button from a button that crashes, a Day 1 restart, or a manual load returning to the ending
• If a pre-ending backup exists, compare the same final choice and menu in the same build without overwriting the original
• Do not select New Game as an assumed fix: separate reset reports exist
• Evidence state: single community report / cause and recovery needs-verification

Try Again is not the same as Demon Rewind

Demon Rewind changes the current run's timeline. Try Again is the ending-screen restart flow reported to begin a new Day 1 route. Keep their counters and consequences separate when documenting NG+ behavior.

After the best ending: Try Again versus the original save

After an ending, Try Again and New Game are different menu actions. The Steam discussion below contains conflicting reports about retained contacts and access to the original completed save. Keep an offline backup before either action; a Day 1 restart alone does not prove that the original run remains recoverable.

• Back up the local save and note Steam Cloud state before the ending-screen action
• Record the ending title, roster, contacts, upgrades, Demon Power, and save slots
• Choose Try Again and compare Day 1 dialogue, map, roster, contacts, and rewind options
• Reload the backup in a separate test to distinguish manual restore from Try Again
• Repeat the same check twice in the installed build before changing the evidence label
• Evidence state: community reports / conflicting / replay pending

Starting a new game during NG+ is a high-risk reset report

A separate Steam Support discussion reports that selecting New Game while already in NG+ reset the entire progress and saved games. That report is a useful warning for the exact query 'does starting a new game erase NG+?', but it does not prove that every build or menu path behaves identically. Keep New Game, Try Again, Demon Rewind, and a manual save restore as separate actions.

• Do not select New Game on the only copy of an NG+ run
• Back up the complete local Godot app-data folder and record Steam Cloud state first
• Capture the exact menu wording, build number, visible slots, Day 1 state, contacts, roster, and Demon Power
• Compare the ending-screen Try Again flow separately from New Game and Demon Rewind
• Repeat the action from a disposable backup in the installed build; success means the original slot and NG+ state remain recoverable
• Evidence state: community report / conflicting with other save-state reports / replay pending

NG+ day-37 crash: isolate the support report before changing the route

The Steam Support index currently lists a report that the game crashes when sending knights on a quest around day 37 in NG+. The index does not establish whether the trigger is the quest, the party, a prior save state, or the build, so keep this separate from the broader New Game reset and Try Again questions.

• Back up the local save before reaching the reported day
• Record the quest, party, roster state, preceding dialogue, platform, renderer, and build
• Compare the same dispatch after a clean reload and from a disposable backup
• Success means the dispatch completes twice in the same build; failure means the crash repeats from the same before-state
• Evidence state: Steam Support community report / needs-verification

Official Patch 1.0.11: Lost Child with Gideon absent

The official 1.0.11 notes fix inconsistencies in the Lost Child plotline when Gideon has not been recruited in New Game Plus. This is a specific NG+ plot fix, not confirmation of every carry-over flag, recruitment invite, or ending condition.

• Fixed: Lost Child inconsistencies when Gideon is absent in NG+
• Retest the same Gideon-absent state in build 1.0.11
• Compare dialogue, quest availability, and follow-up outcome
• Keep roster, contact, item, and rewind carry-over as separate tests
• Evidence state: official NG+ plot fix / wider carry-over remains unverified

Official Patch 1.1.0: New Game+ crash boundary

The official 1.1.0 notes now fix a New Game+ crash. This narrows the current support risk, but it does not prove that every older day-37, Dragon Knight, Try Again, or save-state report is resolved. Re-run the exact before-state in build 1.1.0 and keep crash behavior separate from carry-over behavior.

• Fixed: a New Game+ crash
• Re-test the previously reported crash state in build 1.1.0
• Record cycle, quest, party, preceding dialogue, platform, and save origin
• Compare a clean reload, Try Again, and Demon Rewind as separate flows
• Evidence state: official crash fix / wider NG+ behavior remains replay pending

Carry-over ledger

Before and after the reset, compare five groups: knowledge/dialogue, contacts, roster and recruitment access, tower upgrades and items, and Demon Power or rewind state. Do not assume that a character appearing in dialogue means the entire route is retained.

• Day 1 dialogue and omniscience options
• Map contacts and early recruit invites
• Roster cap, known knights, and route flags
• Annexes, equipment, treasury, and consumables
• Demon Power count and visible ending consequences

True-ending caution

The community often recommends a no-rewind NG+ run for the Epicrates or Last King route. Keep that as a strong route lead, not a universal condition, until the same build reproduces the ending with the exact recorded state.