All Star Tower Defense Modes

All Star Tower Defense modes ask different questions of a roster. Story Mode tests campaign progression and affordable wave defense. Infinite Mode tests scaling. Trials and Raids can add challenge rules or reward-specific runs. Tower Mode focuses on floors and season state, while Gauntlet is documented as a survival activity with its own reward economy.

The official Roblox description directly confirms Story Mode and Infinity Tower. Community mode pages document the other named activities, but current entrances, unlock levels, party limits, wave counts, rewards, and open or maintenance status must be checked in a fresh original-game server.

Mode selector

Verify a mode before building for it

Join the official experience at Place ID 4996049426 and use a fresh server after an update. Locate the entrance, then record its current label, world or lobby location, unlock message, team-size limit, difficulty options, objective, enemy hints, reward panel, event timer, and maintenance notice.

Do not infer a missing entrance from an old map screenshot. Lobby layouts and mode classifications can change. Community Trials documentation notes that older raids or challenges were reorganized at different points, so the current menu name is more reliable than a historical category.

Confirm product identity. All Star Tower Defense X is a separate experience and may have modes or systems with familiar names. This hub covers only the original game.

Match a team to the objective

Use the Story Mode Team and Infinite Mode Team templates as starting structures, then adjust for the live rule.

Read rewards correctly

Separate participation, wave, first-clear, repeat, milestone, leaderboard, event, and shop rewards. Record what the mode panel promises and what the completion screen actually awards. A first-clear bonus belongs in progression, not a repeatable hourly estimate.

For random drops, log several comparable runs. Keep raw observations and do not publish an exact rate from a small sample. For shop currencies, record the earned amount, store price, stock, and reset timer. For unit rewards, confirm the exact form and whether the source is still open.

If a reward is needed for an evolution, verify the live recipe first through Materials. Do not farm a historically associated raid merely because an old recipe page lists it.

Record a reproducible run

Keep mode, world, stage or floor, difficulty, party size, team limit, unit forms, levels, leader, orbs, placements, upgrade order, abilities, time, result, reward, server date, and confidence. For a failure, record the first leak, enemy type, boss health, cash, and cooldown state.

Change one variable before repeating. This reveals whether the roster, placement, economy, or ability timing produced the improvement. In co-op, record who supplied economy, buffs, and control because another party composition may not reproduce the run.

Current uncertainty map

Story and Infinity Tower have first-party existence evidence. Trials, World 2 Raids, Tower Mode, and Gauntlet have dedicated community documentation and therefore credible entity evidence. Their live availability and exact rules remain needs testing until seen in the current client.

Unknown does not mean absent. It means the site will not invent a current floor count, level requirement, wave total, multiplier, reward quantity, or shop price. Record those fields when the interface shows them.

Pick the next page

Choose Story Mode for campaign order and clear procedure, Infinite Mode for push and farming decisions, Trials or Raids for challenge and evolution routes, Tower Mode for floor checks, or Gauntlet for survival and its store loop.

Before entering, write one sentence that defines success. “Unlock the next Story act,” “confirm whether this Trial still awards the displayed orb,” “measure a repeat Infinite reward,” and “inspect the current Gauntlet store” are different goals and need different stopping points. This prevents a scouting run from turning into an expensive push with no useful record.

After the run, update only facts that were actually visible: entrance, requirement, rule, enemy behavior, completion state, and reward. Keep missing values blank. A dated partial record is safer and more reusable than a complete-looking table assembled from several incompatible updates.