Quick answer
There is no single universal fix for a Creator Chronicles party that does not return from a dungeon. The official patch notes say the issue has multiple causes: some have been resolved, while other causes remain open. First confirm that you are testing the current launch build, preserve the affected save, record the dungeon and party composition, and use the official Help Developers or save-report path if the party remains stuck.
Do not delete the save, overwrite every backup, or apply an unrelated system workaround before capturing the state. The report is more useful when it keeps the exact dungeon, party members, difficulty and last visible screen together.
This page owns the stuck-party troubleshooting task. Use the dungeon party strategy guide for repeated combat losses, not as a substitute for the official report path when characters fail to return.
Preserve the affected state
Before changing several things at once:
- Stop repeated reloads that could overwrite the same save state.
- Keep a backup or separate copy of the affected save if the game exposes one.
- Write down the dungeon, difficulty, party members, supplies and whether the run ended in victory, defeat or an unexpected transition.
- Record whether the party is absent from the town screen, still shown in a dungeon result, or blocked by a loading or travel state.
- Capture the current version/build label and the time the run began.
These details help separate a return-state issue from a party, save or travel symptom. They also give the developer a reproducible starting point instead of a generic “stuck” report.
Safe checks before escalation
Use only reversible checks that do not destroy the evidence:
- confirm the client finished updating;
- return to the main menu only when the game offers its normal save path;
- reopen the affected save once and note whether the state changes;
- check the in-game log or result screen if it remains available; and
- compare a separate backup or earlier save only if the game already provides that option.
Do not assume that reinstalling, changing operating-system files, editing save data or repeatedly forcing the process closed will repair the cause. Those actions can remove the state the developer needs and are not a universal answer to this issue.
Use the official developer-help path
If the characters still do not return, open the game's Help Developers route and send the save report through the available in-game flow. Include:
- the current build label;
- the dungeon and difficulty;
- the complete party composition;
- the last action before the party failed to return;
- whether a party member died or the run ended normally; and
- the affected save or report attachment requested by the official flow.
The official notes specifically ask for save data because the issue has more than one cause. That request is the supported next action when the safe checks do not restore the party.
What this page does not promise
An older patch may have fixed one return path while leaving another path open. A party that returns correctly once does not prove every dungeon, difficulty or composition is clear. Conversely, a single stuck run does not prove that changing every party setting will repair the save.
Keep this page separate from current dungeon death penalties. A level reset or departure rule describes what happens after a death; it does not explain a party that never returns to town.
Current launch boundary
The official Steam record checked on September 14, 2026 reports the full release as available. The official launch announcement says demo save data does not carry over to the full version, so preserve the correct live build and save context when reporting a current problem.
Frequently asked questions
Is there a universal fix for a Creator Chronicles party stuck in a dungeon? No. The official notes describe multiple causes and partial fixes. Preserve the save and use the Help Developers or save-report path if the problem persists.
Should I delete my Creator Chronicles save when characters do not return? Do not delete the only copy before recording the state and using the normal save or backup options. The developer's official report request needs the affected context.
What information should I include in a stuck-party report? Include the build, dungeon, difficulty, full party, supplies, last action and whether the run ended in victory, defeat or a death. Attach the save/report requested by the in-game Help Developers flow.
Could party strategy settings be the cause? They can be relevant to a normal combat result, but they are not a universal explanation for a missing return state. Use the party strategy page for behavior settings and the official report path for a return failure.
Sources
- Difficulty Update: New Beginner & Conqueror Modes Added! — official multiple-cause return issue, partial fixes and save-report request; checked September 14, 2026.
- Patch Notes ver. 0.06 — earlier official return-state troubleshooting request and fix boundary; checked September 14, 2026.
- Officially Launches on September 14! New Content & Demo Update Revealed — official launch and demo save-data boundary; checked September 14, 2026.
- is officially out now! — latest official full-release announcement; checked September 14, 2026.
Last verified: September 14, 2026. Recheck the in-game Help Developers labels and save-report flow in the live client if a later patch changes them.