All Star Tower Defense Trials are documented community challenge activities harder than ordinary Story stages and historically associated with an Infinite/Trials area. Older documentation also reflects category changes between trials, raids, and challenges. That history makes the current menu label essential: verify what the original game calls the activity now before applying an old unlock or reward table.
Find the current trial list
Join a fresh server and locate the Infinite, Trials, challenge, or miscellaneous activity area shown by the current lobby. Open each relevant panel and record the exact trial name, entrance, unlock message, level requirement if displayed, difficulty, party limit, objective, enemy hints, reward, and availability.
If a historical trial is absent, mark it historical or unavailable rather than inventing a hidden entrance.
Build for the trial rule
Start with a balanced Story team, then replace the flex slot according to the observed challenge. If the mode emphasizes a target type, bring matching coverage. If the map is short or split, choose affordable units and route coverage. If a boss dominates, prepare focused damage and control.
Unknown first run
Bring broad ground and air coverage, an affordable opener, measured economy, and one control option. Use the run to record enemies and breakpoints.
Damage check
Establish enough early defense, then concentrate upgrades on the attack type and route that caused the previous loss.
Control check
Confirm whether slow, stop, rewind, or pushback affects the dangerous enemy. Save manual abilities for the main damage zone.
Co-op check
Assign opener, economy, boss damage, buffs, and control. Record the party because a solo setup may differ.
Do not assume a general tier list accounts for the trial’s rule. Compare exact forms under the current mode.
Run and record
Before starting, note trial, difficulty, party, team limit, leader, orbs, and intended role for each unit. During the run, record enemy types, lane layout, wave pressure, placement restrictions, and any rule that changes normal behavior.
Track placement and upgrade order. Buy the opener first, then only enough economy to reach needed breakpoints. Reserve emergency Cash if the trial panel did not reveal every target type.
At failure, record wave, enemy, route point, remaining health if visible, Cash, upgrades, and cooldowns. Change one variable before repeating.
Verify rewards
Read the reward preview before entry and compare it with the completion screen and inventory change. Some trials have historically awarded orbs or other valuable items, but current item, quantity, chance, and repeatability must be confirmed.
If the reward belongs to an orb or evolution recipe, inspect that live recipe first. A reward can be real and still be irrelevant to the target you are building. Use Orbs and Materials for those checks.
Do not estimate a drop rate from one clear. Log several comparable results and keep first-clear rewards separate.
Handle renamed or reclassified content
Community pages preserve older labels and can show that raids or challenges once appeared under different categories. Use this history to recognize an activity, not to create duplicate current routes. The live selection panel determines whether it belongs under Trials, Raids, or another menu today.
Record old names as aliases in private notes only when the game identity is clear. Avoid mixing World 2 raids with trials simply because both were once reached from a nearby lobby area.
Improve and repeat
If the first waves fail, reduce economy or choose a cheaper opener. If a special enemy leaks, add matching coverage. If a boss survives, improve focused damage and ability timing. If the team clears but farming is slow, compare run time and repeat reward with another live source.
Use Story Mode Team for the base formation, Raids for activities labeled as raids, and the Modes hub when the current interface classification is uncertain.