All Star Tower Defense raids are documented community activities associated historically with World 2 and an Adventure building, with unit or evolution-related rewards. Exact active raids, world access, party limits, wave counts, entry requirements, and drops can change. Confirm the current original-game panel before farming or assembling a party.
Find and verify the raid
Check whether the current lobby provides world travel, an Adventure building, a raids panel, or another route. Record the exact world and entrance labels, unlock message, raid name, difficulty, party limit, objective, enemy hints, reward preview, and availability timer.
If the entrance is missing or under maintenance, mark the raid unavailable or needs testing. Do not substitute an All Star Tower Defense X raid.
Assemble a party by job
Choose an affordable opener, area damage, boss damage, economy, buff support, and control according to the displayed team and party limits. In a larger party, distribute jobs instead of asking every player to bring the same complete loadout.
Opening player
Places reliable defense immediately and calls when the route is stable enough for economy.
Economy player
Funds their planned units without leaving the opening player unsupported. Stops investing before the danger window.
Damage players
Cover ordinary groups and the raid boss with upgrade breakpoints matched to the route.
Support caller
Coordinates buffs, slow, timestop, rewind, or pushback so abilities do not overlap wastefully.
Record which player supplies each role. A clear depending on a specific borrowed unit is not a solo recipe.
Scout enemies and the map
Use the first run to identify lanes, placement zones, air or other target types, durable groups, and the boss path. Reserve positions where several lanes overlap and where support can reach multiple attackers.
Do not spend every placement near spawn. Raid bosses and late groups may need a second damage zone. Keep emergency Cash until the current enemy behavior is understood.
If the raid has an unusual rule, test it directly. Do not infer immunity or weakness from an old guide. Record which attacks connect and whether control works on the boss.
Upgrade and coordinate
Stabilize the opening before economy. Build area coverage before maxing one expensive unit. Reach behavior-changing upgrades before small increases. Save manual abilities for the boss or the wave that caused the previous failure.
Use voice or simple chat callouts for buff and control order. Record cooldowns from the exact forms. If two supports do not stack, alternate them. Keep support coverage inside the main damage zone.
At failure, record wave, enemy, boss health, route distance, Cash, upgrades, and cooldown state. Change one variable for the retry.
Verify raid drops
Compare the reward preview with the completion screen and inventory. Separate guaranteed, chance, first-clear, repeat, and milestone rewards. A community recipe linking a material to a raid is a discovery clue, not live proof.
For a material target, open the current evolution recipe first. Record exact ingredient and quantity, then log several raid results. Do not claim an exact rate from a small sample.
For a unit reward, verify the exact form and whether it is granted, dropped by chance, or purchased with a raid currency. Lock the result before managing inventory.
Decide whether to farm
Compare success rate, run time, attention, entry cost, party dependency, and repeat reward. A difficult raid can be the correct progression clear but a poor repeat farm. First-clear rewards should not be multiplied into hourly income.
If the required party is unavailable, check whether another live source exists before forcing solo attempts. Preserve the current mode status and date; a later update may rotate or reopen a raid.
Use Materials to manage the recipe, Support Units for party utility, and Trials if the current lobby classifies the activity as a challenge rather than a raid.