All Star Tower Defense support units create value that ordinary damage rankings can miss. They generate match cash, increase another unit’s output, slow or stop enemies, rewind or push a route, heal or protect the base, and provide manually timed abilities. A support is good when it solves a team problem more efficiently than the damage slot it replaces.
Community unit indexes consistently separate support roles from ordinary attackers, but exact percentages, cooldowns, placement limits, and stacking rules can change. Use the named examples below to recognize a role, then inspect the exact form you own in the current game.
Support role index
The examples are community-indexed discovery names. Match the complete unit label and inspect the current ability text; several character families have multiple forms with different kits.
Economy units and the payback test
An economy unit is not free cash. Placement and upgrades consume money that could have defended the route. Record each investment, each payout, and the wave when cumulative extra cash exceeds cumulative cost. That is the payback point.
In a short Story stage, stop economy upgrades when too few waves remain to recover the cost or when the next enemy requires immediate damage. In Infinite Mode, a stable opener can justify more economy because later scaling has time to repay the investment. Team members should coordinate farm responsibility so everyone does not delay defense at once.
Test economy with the same stage and opening. Compare cash at fixed waves, not just the largest payout shown at maximum upgrade. A cheaper unit that pays back earlier can be more useful than a higher ceiling your run never reaches.
Buffers and coverage planning
A buffer must reach the attackers that matter. Place intended damage units first in a test, inspect the support radius, and find a position that covers several without stealing prime route space. Record which stat changes: damage, range, attack interval, or another property. Then note duration and cooldown.
Do not assume two copies stack. Test one buffer, record the visible unit panel or controlled wave result, then add the second. If the result does not increase, use the extra slot elsewhere. If alternating abilities extends uptime, record the timing sequence and whether both activations can be controlled reliably on mobile as well as desktop.
Buff value scales with the team inside its coverage. Improving several finished attackers can outweigh bringing one more unbuffed damage unit, while buffing weak or under-upgraded units may not justify a slot.
Slow, stop, rewind, and pushback
Control increases the time enemies remain inside attack range. Slow offers sustained tempo, while timestop often creates a shorter emergency or burst window. Rewind and pushback can recover route distance but may have target or immunity limits. The live ability description and one controlled test are essential.
Sustained slow
Prioritize route coverage and uptime. Place it where enemies enter the largest shared damage zone, not necessarily closest to spawn.
Manual timestop
Save it for a boss, a dense dangerous wave, or the moment another ability is ready. Early panic use can leave the cooldown unavailable when needed.
Rewind or pushback
Measure actual route distance recovered and confirm which enemies are affected. Do not assume bosses follow ordinary target rules.
Control chain
Coordinate activations rather than overlapping them. A simple callout order produces more useful uptime than simultaneous abilities.
Control can also alter targeting and attack timing, so compare a full wave outcome rather than multiplying a guessed duration by displayed damage.
Healing and special utility
Healing or base-protection effects matter only when they change the result. Record the base state before activation, the amount or behavior observed, cooldown, restrictions, and whether the effect works repeatedly. If a mode ends on one unrecoverable leak, prevention may still be better than healing.
Other utility can include summons, status removal, enemy debuffs, map effects, or team-wide abilities. Describe the observed effect directly and avoid forcing every special unit into a damage-per-second formula. If the contribution cannot be isolated, label it as a team test rather than a base-stat result.
Build a balanced support package
Start with the failure condition. If upgrades arrive too late, test one economy slot. If a boss exits range, test control. If several strong attackers are already deployed, test a buffer. If the base survives with recoverable damage, test protection or healing. Do not add every support category automatically; each one competes for a team slot and match cash.
A practical Story template is early defender, main area damage, priority or air coverage, economy, one control or buff slot, and one flexible answer. A practical Infinite template shifts toward scaling damage, placement efficiency, economy, a coordinated buff, sustained control, and a boss or emergency tool. Confirm the team-size limit shown by the current interface before copying any six-slot example literally.
Test and record support value
Run the same stage with and without the support. Keep attacker levels, orbs, leader, placements, and upgrade order stable. Record wave reached, boss health, cash at fixed points, leaks, and ability times. A support earns the slot if the result improves consistently and the player can execute its timing.
For current exact values, use the unit’s live panel and date the observation. Community lists are useful for finding names such as Bellma (Money Corp), Salesman, Jeff (CEO), Idol, Flower Magus, Onwin, Skeleton (Artist), Ex-Captain, and ZIO, but names alone do not verify a current percentage or cooldown.
Continue with Unit Stats for the record format, Story Mode Team for short-stage priorities, or Infinite Mode Team for scaling and ability coordination.