1. Start with a target and an owned-roster audit
Write one task, such as finishing a specific story battle or completing a selected boss difficulty. Record solo or party play, the encounter rules shown in-game, and any entry cost. A setup that works in one task still needs checking in another.
For each owned hero you are considering, record the equipped weapon, upgrade state, relevant unlocks and exact skill conditions from the live client. Use the official announcement directory to locate release information, then check it against current in-game text.
- Damage job: who deals damage during the opening you can actually reach? Record which attack or skill you intend to use.
- Enabling job: does an owned member's stated effect satisfy a condition needed by that damage plan? Write the condition and who receives the effect.
- Survival job: if an owned kit has a relevant recovery or protection effect, can you use it before the repeated failure? If no such option exists, change the action plan and record that limitation.
- Remaining job: choose it for a requirement you can name, such as handling another target or enabling a missing interaction. Leave it provisional if you cannot explain its contribution.
These are planning jobs, not mandatory game classes or a universal formula. One hero may cover more than one job. Do not assume that sharing an element proves synergy, that every support helps every damage role, or that a rare hero supplies a missing function.
