Pre-launch · Sep 11, 2026Launch: Sep 14
Creator Chronicles Dungeon Party Guide: Composition, Supplies and Wipe Diagnosis
Build safer dungeon parties with role coverage, recommended levels, supplies and combat-log review.
Updated
Sep 11, 2026
Sep 11, 2026
Quick answer
For your first reliable party, start with a Tank, one damage dealer and a Healer/support member. Then check recommended level, food/potions and gear before dispatch. If a prepared party still loses, use the result/replay information to diagnose the failure instead of immediately grinding random levels.
Official Steam screenshotThe baseline three-role party
| Role | Job | Failure if missing |
|---|---|---|
| Tank | Absorb/control incoming pressure | Damage/healers get overwhelmed or aggro becomes unstable |
| DPS | End fights before sustain collapses | Long battles consume more recovery and expose weak links |
| Healer/support | Restore health and stabilize bad damage spikes | A survivable fight turns into a slow wipe |
Pre-flight checklist
- Check every member against the dungeon’s recommended level.
- Confirm the party is not missing a core role.
- Check potion/food stock and party-specific strategy settings.
- Check equipment and recent mood; do not repeatedly throw a mentally depleted member at the same failure.
- Dispatch, then read the result log before changing the roster.
What a wipe is trying to tell you
Guide illustration
- Long-form footage includes a level-one party wiping around stage three while another party progresses—good evidence that “dungeon unlocked” is not the same as “party ready.”
- The latest update adds a warning for members below recommended level.
- If a well-prepared party repeatedly loses, the game can reveal a remaining dungeon hint.
- Replay/log systems exist specifically so you can inspect causes of defeat rather than guess.
Later: presets and Auto-Run
Guide illustration
- Auto-Run is later content tied to the Griffin Rider Base in the official development notes.
- Presets store supply data separately per party and can prioritize dungeons.
- Treat Auto-Run as a reward for having stable teams; it does not fix a bad roster or empty supply chain.