Stages
Normal stages, hard stages, main story, mini story, group story, and event stages.
Stage settings enter stages or combat, so they are high-impact. After changes, run once manually and confirm stage number, count, team, and logs.
Normal and hard stage input uses English commas, for example 1-1-1,1-2-3.
Stage Automation Prerequisites
Normal stage automation follows fixed team movement routes, not only sweep logic. Before enabling it, confirm:
- Auto end turn and auto battle are unlocked in game.
- Normal stage automation is generally more stable from area 4 onward.
- In-game team numbers are arranged from small to large according to the stage requirement; multi-team stages depend on team number for coordinates and move order.
- Team selection logic matches the settings described in Teams.
Event Stages
Before enabling event tasks, confirm event recognition, task type, stage number, server progress, and whether boss handling needs manual work.
Stage Input Rules
Legacy backend input rules are still useful for understanding stage parameters:
| Scenario | Format | Example |
|---|---|---|
| Normal stages | Area or area-stage | 15,16-3 runs area 15 and stage 16-3 |
| Hard stages | Same as normal stages | 15,16-3 runs H15 and H16-3 |
| Main story | Chapter numbers separated by commas | 2,3,6 means chapter 1, chapter 2, final chapter |
Stage automation checks SSS, challenge tasks, and gift collection where applicable. Completed stages are skipped. Some hard stages in chapters 1-13 may be entered more than once to satisfy all goals; later chapters usually finish in one pass.
Main Story Chapter Numbers
Main story uses numeric chapter IDs separated by English commas:
| Number | Chapter |
|---|---|
1 | Part 1 prologue |
2 | Chapter 1 |
3 | Chapter 2 |
4 | Chapter 3 |
5 | Chapter 4 |
6 | Final chapter |
7 | Chapter 5 |
8 | EX chapter |
9 | Chapter 6 |
10 | Part 2 prologue |
11 | Chapter 0 |
12 | EX chapter |
Story automation can handle most route-map flows, but final chapter or special combat may still require manual play. Empty input uses the backend default configuration.
Event Recognition
Event stages are generally stable for Story / Quest / Challenge structures. Challenge stages that are not route-map stages may require manual boss or combat handling.
