Quick answer

Use the current Party Strategy settings to configure each party's potion use, healing behavior and attack behavior for the dungeon job it is about to perform. Origin Studio's official update describes these settings as stored per party, so you can build different strategies for different compositions and content. The live client remains the authority for the current menu labels and exact behavior.

Start with one change: set potion usage and healing around the party's sustain need, set attack behavior around its target or pressure job, then check the preparation screen for remaining supplies and under-level warnings. Do not change the whole roster and all settings at once; you need to know which decision altered the result.

This page owns party preparation and behavior settings. Use the dungeon death penalties guide for the consequence of a death and the stuck-party troubleshooting page if characters fail to return.

Configure one party for one job

Before opening the settings, name the party's immediate job:

  • Learning or Beginner clear: prioritize readable behavior and enough recovery to see what the dungeon is testing.
  • Conqueror challenge: account for the level-reset and possible departure risk before choosing an aggressive setting.
  • Repeated-loss diagnosis: change the setting tied to the failure instead of replacing every member.

The official notes say each party can have its own strategy. That means a setup that makes sense for one composition or dungeon does not automatically transfer to every preset.

Potion usage

Use potion settings to answer one question: should this party spend its available recovery supplies early, late or only under the current configured condition?

Check the remaining potion quantity on the preparation screen, then compare it with the dungeon's risk and the party's ability to recover without help. A party that spends everything on the first difficult room can enter the next section without a recovery path; a party that never uses supplies can lose the run while carrying them.

The official update also says health and mana recovery potions are prioritized for classes that actually use them, while strategy conditions and available stock affect the choice. Read the current UI after setting the rule rather than assuming every class consumes the same resource.

Healing settings

Healing behavior should match the party's job and the consequence you are willing to take:

  1. Check who can heal and who needs healing.
  2. Set the party's healing condition in the current menu.
  3. Verify that the required potion or mana stock is available.
  4. Run the same dungeon or a comparable section.
  5. Record whether the party failed from missing recovery, bad timing, damage pressure or a separate issue.

If the party is on Conqueror, connect the healing choice to the current death rules. The right setting is the one that protects the run's actual objective, not the one that looks most aggressive in a menu.

Attack settings

Attack behavior is a decision about how the party spends its combat window. Use the current attack setting to make the party's intended job explicit, then observe the battle log or result screen:

  • Is the party reaching the intended target?
  • Is it spending attacks while healing or repositioning would have been safer?
  • Does the setting fit the party's composition and the dungeon's current threat?

Change one attack condition at a time. The official notes support per-party behavior control, but they do not publish a universal setting that clears every dungeon with every composition.

Preparation screen and warnings

Before departure, inspect the current preparation screen for:

  • remaining preparation-item quantity;
  • party member level and role;
  • the active dungeon for that preset; and
  • any warning about a member below the recommended minimum level.

The official update notes describe these visibility and warning improvements. In the live release, use the current preparation screen as the authority for the labels and warnings shown to your party.

A controlled retry loop

When a party loses repeatedly:

  1. Keep the same dungeon, difficulty and core composition.
  2. Capture the current potion, healing and attack settings.
  3. Change the setting most directly connected to the failure.
  4. Run again with the same preparation target.
  5. Compare the result screen and supplies before choosing a second change.

If a well-prepared party repeatedly loses, the official update says it can obtain one of the remaining dungeon hints. Use that in-game feedback rather than inventing a permanent tier list.

Current launch boundary

The Steam listing checked on September 14, 2026 reports the full release as available, and the latest official launch announcement says the full version is officially out now. The official update notes are the source for the Party Strategy feature context; the live client is the authority for current menu labels and exact behavior.

Frequently asked questions

What are the Creator Chronicles Party Strategy settings? The official update describes per-party potion usage, healing and attack settings that let each party behave differently around its composition and content.

Should every party use the same potion and healing settings? No. The feature is per party, and the correct choice depends on composition, supplies, dungeon and difficulty risk. Use one controlled change when diagnosing a loss.

Why is my party still losing after changing attack settings? Attack behavior is only one part of a run. Check supplies, healing, member level, dungeon difficulty and the result screen before changing the whole preset.

Can Party Strategy fix a party that does not return from a dungeon? It can help with ordinary combat preparation, but it is not a universal answer to a missing return state. Use the official stuck-party reporting checklist for that symptom.

What should I check before leaving for a dungeon? Check the active dungeon, party levels, remaining preparation items, potion and healing conditions, attack setting and any under-level warning shown by the current preparation screen.

Sources

Last verified: September 14, 2026. Recheck Party Strategy labels and behavior in the live client if a later build changes them.