All Star Tower Defense Units

All Star Tower Defense units are not interchangeable damage numbers. Every useful comparison starts with the job a unit must perform, the mode it will enter, the cash available during the match, and the conditions used to record its stats. The official game describes summoning units with unique abilities and upgrading troops during battle. That means ownership is only the first decision; placement, upgrade order, support coverage, and team fit decide whether a unit actually helps.

This hub connects three practical tools: a searchable-minded Unit List, a consistent Unit Stats comparison method, and a role-based Support Units guide. Use them together instead of treating rarity or a single damage screenshot as a complete verdict.

Start with the role, not the star count

Rarity still matters because it often reflects acquisition or evolution progression, but it does not answer whether the unit fits your current stage. A difficult-to-build 7-star may be a long-term goal, while an affordable lower-rarity unit can solve today’s early-wave problem.

Read a unit card in the right order

First identify the exact version of the unit. Similar names can represent different rarities or evolved forms, and community nicknames may not match the inventory label. Record the displayed name, star rarity, evolution state, and source. Lock the unit before experimenting so it cannot be sold or fed accidentally.

Next inspect placement type and attack behavior. Ground, hill, hybrid, area shape, target priority, and special abilities determine what a damage number can reach. A unit with strong output but poor route coverage may need a different map position. A support ability with a long cooldown needs a planned trigger, not automatic use as soon as it lights up.

Then read the upgrade path. Note placement cost, each upgrade cost, damage, range, attack interval, attack type changes, and newly unlocked abilities. A maximum-upgrade total is useful for endgame planning, but Story Mode often tests whether the first two or three upgrades are efficient.

Finally identify modifiers: unit level, leader slot, orb, buffs, debuffs, mode effects, and duplicate restrictions. Community stat tables may use a fixed level such as 175 and may exclude support or active-ability damage. Label the baseline before comparing it with your own inventory.

Build a six-question unit record

Unknown values should remain blank in a record. Guessing a cooldown or percentage makes every later comparison worse, while a clearly empty field tells you exactly what to test next.

Choose units for the mode

For Story Mode, prioritize reliable early defense, affordable upgrades, route coverage, and enough economy to reach the final waves. Read the Story Mode Team guide for role templates. A slow-starting maximum-damage unit can be excellent elsewhere and still be a bad opening choice.

For Infinite Mode, value scaling, placement-limit efficiency, control uptime, buff coverage, and coordinated ability timing. The Infinite Mode Team guide explains how to transition from a safe opener into a late-wave formation.

Trials, raids, Tower Mode, and Gauntlet may add enemy rules, entry requirements, fixed routes, or mode-specific rewards. Check the current mode panel before applying a general tier. A unit’s usefulness can change when air enemies, bosses, immunities, or restricted deployment alter its job.

Improve an owned roster before chasing another unit

Sort your inventory into the six roles above. Identify the empty job rather than the lowest rarity. If you have damage but cannot survive early waves, improve the opener. If a boss escapes, add focused damage or control. If upgrades arrive too late, repair economy and upgrade order before spending more summon currency.

Test one change on the same stage. Keep map, difficulty, leader, unit levels, orbs, and placement positions stable. Record the wave where the formation fails, the cash held, and the cause: leak, air target, boss health, ability timing, or lack of upgrade money. That result gives a more useful next action than copying a showcase team you cannot reproduce.

Use duplicate units carefully. Some may be needed for evolution recipes or future collection goals. Lock one working copy, inspect the live evolution menu, and only then decide whether extras are safe to use as experience. Event or capsule units can become difficult to replace when their source closes.

Evidence and update discipline

The official Roblox page confirms the core summon-and-upgrade loop and rotating Summon Gate. Community indexes help discover names, roles, and historical sources, but several community unit and evolution pages identify themselves as incomplete or under revision. Treat them as navigation aids, then confirm values in the current game.

Every stat snapshot should carry a check date and baseline. Every source label should say whether it was seen in the current banner, recipe, shop, or completion screen. When an update changes a unit, preserve the old observation as historical rather than silently combining it with a new maximum value.

Recommended next step

If you are identifying an unfamiliar inventory, open the Unit List. If you are comparing two candidates, use Unit Stats. If your team already has damage but lacks economy, buffing, or control, go directly to Support Units. For a mode-specific decision, continue to the Meta hub after the role is clear.