OFFICIAL STARTER GUIDE · teams
Build teams around failure points, not matching rarity
Three practical team patterns, how to adapt them to each mode, and why a support slot should earn its place.
Give every slot a purpose
A starting pattern is pressure, sustain, and utility. Pressure finishes a target. Sustain keeps useful turns coming. Utility handles a specific enemy mechanic. That is a checklist, not a forced class system: some kits cover more than one job, and some encounters reward extra focused damage instead of more healing.
Use owned units as substitutions. You do not need a particular premium pull to begin thinking this way. Compare the actual skill descriptions, cooldowns and targets in Heroes.
Pattern one: protect the finisher
Pair a damage role with ally protection and a flexible support. Cancer Male or Phantom Knight can offer protection; Cancer Female offers recovery. Choose the actual variant you own. In a manual battle, time a protective skill around the enemy intent and current legal targets. In auto Ladder, watch whether the automatic sequence protects the hero who needs it.
The weakness is tempo. Too much protection can leave you unable to finish a healing enemy. If the battle drags, consider replacing redundant sustain with targeted pressure or disruption.
Pattern two: setup and payoff
Stack-based kits, such as Capricorn Male's enemy-stack pressure or Taurus Female's healing cycle, need turns to prepare. Surround them with tools that keep the plan functioning. Read which hero or target receives stacks; different stack labels are not automatically interchangeable.
The weakness is early pressure and control. If the setup hero falls or loses key turns before its payoff, the theoretical synergy does not help. Try a faster answer rather than assuming higher rarity fixes the sequence.
Pattern three: counter the encounter
Scout the enemy and assign a counter slot. A barrier can help against negative states while it survives. Buff theft or copying can create value against buffs. Focused disruption can matter against a healer. An area attacker may help against groups, but can be the wrong tool when restoration undoes spread damage.
Tower rule 2 gives every hero Guard and Interrupt. Select native utility that complements those controls rather than duplicating a job everyone already has. Against a marked burst, the victim's timing matters more than a generic defensive label.
Respect each mode's roster rules
- Daily Adventures: three to five available heroes of different species. The selector enforces the composition rules.
- Tower: rule 2 uses exactly three owned, available supported units with normalized stats; this is not the unreleased stat-enabled rework.
- Equipment dungeons: three to five different owned species; entry readiness and boss-counter readiness are different checks.
- Auto Ladder: use its own saved team and setup controls; manual turn timing from Tower is not transferable.
Availability matters. If a hero is on expedition, use another legal option rather than planning around an unavailable slot.
Review one loss with a clear question
Who failed first? Which enemy action caused it? Was the problem damage, survival, status pressure, or cooldown timing? Swap the slot with the weakest answer, then compare. A team recommendation is a hypothesis you can test, not a promise that the same lineup clears every mode.
Tested combinations are not a mixing chart
Forge has three evidenced v13 options, Lycan, Storm and Phoenix, plus Lycan-Storm as a bounded attacker substitution. The Phoenix team uses Phoenix Female. Venom and Eclipse retain separately evidenced v12 cores under the unchanged non-Forge compatibility check. Shared heroes and limited substitutions are allowed; recovery is useful but is not a mandatory role in every successful Forge build. Stronger investment may overpower earlier floors. No screened late team qualified as a universal across all three bosses; a finite search does not prove universal teams are impossible.