The best support is the one that changes the wave where your team fails. Current community builds frequently discuss Helper Bot, Cola, ITrapped/control and Dusekkar-related endgame packages, but names alone do not establish a tier. Radius, cost, uptime, stacking rules, boss immunity and the number of developed towers affected decide whether support deserves a slot.
Support role bands
These bands tell you what to test. The live tower card and a same-condition run are the authority for exact percentages, cooldowns and stacking.
Measure support value
Count how many developed damage placements stay inside the radius during their useful firing window. Record the cash spent on support and the extra wave, boss time or coverage it produces. For control, measure actual extra seconds on path and confirm whether bosses or special enemies resist the effect. For buffs, compare the whole supported cluster before and after placement.
Do not rate support by its own damage screen. Also do not assume two identical effects stack. Test one support, then the second, under the same wave and watch whether the relevant stat or outcome changes. If the UI is unclear, treat stacking as unconfirmed.
Place support after the carries
Reserve the best overlapping damage positions first. Preview the support radius and move it until it reaches at least two important towers without displacing them from the path. On a split map, two smaller clusters may outperform one prestigious support that reaches the wrong lane.
Upgrade the support when its next breakpoint improves the current cluster more than the same cash spent on a carry. Early in a run, direct damage can be safer. Late in Endless, a percentage or uptime effect touching several maxed placements can scale harder.
Pick by failure type
- Groups escape together: slow, stun, AoE amplification or wider cluster coverage.
- Boss survives alone: damage amplification or control confirmed to affect it.
- A carry loses contact: range or time-on-path support if currently available.
- One property cannot be targeted: detection support or a flex tower.
- Board space is full: a role-compressing hybrid can beat another narrow slot.
- Cash is the problem: compare support cost with a direct upgrade before buying.
Patch-safe checklist
Confirm tier, path, radius, target restrictions, placement limit, cooldown and stacking in the current server. Record the map and modifier. Retest after balance updates. A support deserves a high tier only when it improves a real, repeatable team outcome—not because it appears beside a strong carry in a screenshot.
Support package worksheet
Write down the support’s placement and upgrade cost, the carries inside its radius and the exact effect shown live. Compare the same cluster without support, at the first useful support breakpoint and at the planned final upgrade. Record the wave gained and whether the decisive boss or property was actually affected.
If two supports are proposed, test them separately before combining them. A second buff that does not stack consumes a loadout slot, cash and board space for no result. Two different effects can still be poor if one misses the carries or arrives too late.
Placement questions
Would moving the support reduce a carry’s path coverage? Does a split map require a second cluster? Can a hybrid provide detection or damage while supporting? Answer with range previews and a repeatable wave, not labels. In short modes, direct damage may beat an expensive buff; in Endless, a scalable effect touching several developed carries can become the better purchase.