TDS Reforged Auto Strat & Macros

Auto-strat scripts record tower placements, upgrades, abilities, and skip timings, then replay them on demand. In the TDS ecosystem these range from simple placement macros to complex decision trees that adapt based on wave number. This page explains how auto-strat tools work, what separates a useful recording from a fragile one, and why Reforged’s custom content makes auto-stratting particularly risky compared to official TDS.

How auto-strat tools function

At the core, every auto-strat tool captures a sequence: tower A placed at coordinates X on wave 3, upgraded at wave 7, ability used at wave 12, and so on. When replayed, the script reads back those inputs in order. More advanced tools layer on conditional logic—if wave type is X, skip to placement Y—if enemy count exceeds threshold, sell tower Z—but even these conditionals are brittle when game state deviates from expected parameters.

Reforged-specific tools sometimes surface loadout selectors, map votes, and webhook logging to Discord channels. These integrations are appealing for co-op grinding groups but add attack surface: webhook tokens, executor permissions, and third-party API calls all extend beyond the game itself.

What good strats require

A reliable auto-strat is built on four pillars:

Exact map geometry. The recorded coordinates assume a specific map layout. If the map is revised—even subtly—placements may land in walls, off-path, or in positions that block line-of-sight for other towers. Reforged’s custom map support means maps change more frequently than official TDS.

Matching tower unlocks. A strat recorded with Gladiator assumes Gladiator is unlocked. If your account does not have Gladiator, the script either fails silently or places nothing, leaving you defending with half a loadout.

Updated timings after patch nerfs. Tower damage, attack speed, and range values shift with patches. A strat built on wave-10 Enforcer one-shot kills may find those kills fail at wave 10 after a damage nerf, creating a cascade failure mid-run.

Human oversight on first run. Always watch the first replay in person. A failed placement, a mis-timed ability, or a map vote deviation can be aborted before wasting an entire run.

Reforged specifics

Custom maps and modes mean a recorded strat from a friend’s private mode may not port to the public version, or vice versa. Private server maps sometimes use modified pathing that differs from the public counterpart. Before committing a strat to memory, test it on the public map at least once.

The Custom Gamemode editor in Reforged also lets players author rulesets that deviate from standard wave structures. A strat built for Molten Mode rules will break on a custom authored mode with different enemy scaling.

Recommendation: Learn Solo Hardcore manually first. Understand the economy curve, the sell windows, and the boss timings in your own voice and rhythm. Then—if the risk is acceptable—evaluate whether a recording adds value or just compresses a skill you should have developed yourself.

Workflow if you still decide to proceed

If after weighing the risks you choose to use an auto-strat tool:

1. Read the full Script Safety page before installing anything
2. Install the tool in an isolated executor environment—do not grant broad permissions across all games
3. Start with a dry-run recording: record one standard map, replay it once while watching
4. Abort immediately on path deviations, unexpected enemy types, or tower behavior that differs from the recording session
5. Log which wave and map the strat failed on; discard the recording if failures are consistent
6. Re-record after every patch that touches tower stats, map layouts, or wave compositions

Why strats break after patches

Patches are the primary failure mode. When Vince Games adjusts tower damage, attack speed, placement costs, or enemy HP pools, recorded timings become invalid. A sell signal that fired at wave 18 in the pre-patch version may fire too late in the post-patch version because enemy waves cleared faster or slower.

Secondary failure modes include: map edits that change path geometry, new enemy types introduced mid-patch that were not in the recording, and executor updates that alter input timing precision.

What this wiki does not host

We do not host script files, tool binaries, or executor integrations. We describe tool categories and safety principles—not mirrors for third-party code. If a tool claims to be “official” or asks for your Roblox password, close it and report it.

Related pages

• Auto Farm for farming automation concepts
• Controls — know manual recovery when strats fail
• Patch Notes for post-patch breakages
• Solo Hardcore for the manual baseline

TDS: Reforged is unofficial and not affiliated with Paradoxum Games. Account risk from third-party tools is yours to bear.