Boss Rush tests whether a team can survive repeated boss checks without relying on the generous setup time of a long Infinite run. Community references describe a 30-wave structure with a major boss appearing every ten waves and traits disabled inside the mode. Those rules should be confirmed on the live mode card before spending an entry, because an update can change the rotation, modifiers, rewards, or eligibility.
The important preparation is role coverage. A lineup made only from high-ranked damage units can fail when it lacks early control, boss uptime, or enough economy to reach its expensive upgrades before a checkpoint. Build for the sequence you will actually face, then use the first attempt to record timings rather than expecting a blind clear.
Confirm the current rules first
Open Boss Rush and read the information panel before selecting a team. Check:
- the total wave count and listed boss waves;
- whether traits, familiars, or other account bonuses are disabled;
- the current map, enemy tags, resistances, and special modifiers;
- entry costs or daily limits;
- reward thresholds and whether rewards are one-time, repeatable, or ranked;
- any unit bans, element bonuses, or placement limits.
If traits are disabled, a unit that normally depends on a rare trait may perform very differently. Compare base kits and upgrade curves instead of copying a general tier list unchanged.
Build a five-role team
A stable Boss Rush roster usually covers five jobs, even if one unit handles more than one:
| Role | What it solves | Selection question |
|---|---|---|
| Early defender | Prevents leaks before economy develops | Can it be placed and upgraded cheaply? |
| Main boss damage | Delivers sustained single-target pressure | Does it keep attacking through movement or mechanics? |
| Area damage | Clears escorts and dense waves | Is its coverage reliable on this map? |
| Control or support | Buys time and amplifies the carry | Does the boss resist its effect? |
| Economy or flex | Funds the curve or answers a special tag | Does it repay its slot before wave 10? |
Avoid filling every slot with slow, expensive finishers. If the first boss arrives before the team is online, theoretical endgame damage never matters.
Plan around the boss checkpoints
Treat waves 10, 20, and 30 as budget deadlines when the current mode uses the reported format. Work backward from each checkpoint. Decide which carry upgrade, support placement, and emergency reserve must be ready before the boss enters the most dangerous lane segment.
During ordinary waves, spend only when a leak or timing problem requires it. Entering a boss wave with a cash reserve lets you react to an immunity phase or unexpected escort. After a boss falls, rebuild the plan for the next ten-wave segment rather than upgrading every placed unit automatically.
Placement and target settings
Boss Rush maps reward overlapping coverage. Put the main damage dealer where it can attack the boss across more than one turn, and place support units so their range includes the carry without blocking future placements. Keep a cheap defender closer to the entrance only if it can prevent early leaks without consuming the premium central position.
Target settings matter. A carry set to strongest may stay on the boss but ignore a dangerous fast escort. An area unit set to first can protect the exit while the carry remains focused. Recheck targeting after a boss changes phase, spawns adds, or becomes temporarily untargetable.
Upgrade order
Use an upgrade ladder instead of spreading money evenly:
- Buy the minimum early defense that stops normal enemies.
- Start economy only if it pays back before the first boss deadline.
- Reach the main carry’s first meaningful damage or attack-pattern breakpoint.
- Add support when its buff or control produces more value than another carry upgrade.
- Reserve enough cash for a reactive placement.
- Push the carry toward the next checkpoint breakpoint.
The correct breakpoint is visible in practice: it changes coverage, multi-hit behavior, damage uptime, or the number of cycles needed to finish a target. A small numerical upgrade may wait if it does not change the clear.
Learning from a failed run
Record the earliest decisive failure, not just the final wave. If an escort leaked while the boss remained healthy, the problem was probably coverage or targeting. If the boss reached the exit alone, compare boss damage uptime and upgrade timing. If the team never reached its planned upgrades, reduce early spending or replace a slow economy choice.
Change one major variable on the next attempt. Swapping three units and all placements at once makes it impossible to know which adjustment worked.
Solo and group considerations
In a group, assign jobs before the run. One player can cover early waves, another can build boss damage, and another can reserve a control or support answer. Avoid duplicating support effects until the live tooltip confirms they stack. Communicate boss phase changes and emergency spending.
For solo play, prefer units that compress roles. A carry with credible area coverage or a support that also contributes damage saves a scarce slot. Reliability is more useful than a peak setup that requires perfect timing and a rare sequence of bonuses.
Reward and farming decisions
Do not assume the deepest clear is always the best farm. Compare the time and entry cost required to reach each reward threshold. If an intermediate checkpoint grants most of the repeatable value, a faster consistent route can outperform unstable full clears.
Recheck the reward panel after updates and before using premium resources. Community pages can preserve older rotations, and the current server interface is the source that governs your attempt.
Quick run checklist
- Verify current modifiers, trait rules, rewards, and entry conditions.
- Cover early defense, boss damage, area damage, support, and funding.
- Set cash and upgrade deadlines before each boss checkpoint.
- Place for repeated boss coverage and keep a reactive reserve.
- Record the first real failure and adjust one variable.
Boss Rush becomes manageable when it is treated as three planned damage checks rather than one long battle. Build around the live rules, protect your economy curve, and let recorded timings guide the next run.