Creator Chronicles Party Strategy & Safe Returns

Current reference

What the official sources confirm

• v1.06 adds a stop-after-loss strategy.
• v1.03 saves normal-dungeon strategy changes automatically.
• Gryphon dispatches now require confirmation after the run count is chosen.
• Failed automatic runs consume departures.

Practical use

What to do next

1. 01

   Use a cautious return condition while learning a new encounter.

2. 02

   Check the saved strategy after changing dungeons or editing presets.

3. 03

   Review potions, food and elixirs before confirming repeated runs.

4. 04

   Match the next attempt to the log's failure point, not an arbitrary aggression slider.

Write a strategy you can actually compare

Record the intended attack behavior, healing behavior and potion policy using the options visible in your current game. Add a stopping condition and the weakness you are testing. A plan such as “fix the first Mana shortage while retaining the same damage members” is more informative than changing every setting at once.

After the run, compare the timing of the original problem and the resources left over. More unused potions do not prove that conservation was good if the party died while they were available. Likewise, a safer return can protect a learning attempt without proving the party is ready to clear the dungeon.

Related guides & tools