Rogue Tower

Tower defense has been creatively frozen for the better part of a decade. The genre calcified around a fixed formula: here is a map, here is a predetermined path, here are your build slots, now optimize. The good ones — Bloons, Kingdom Rush, Defense Grid — iterated on tower variety and enemy composition while leaving the fundamental contract untouched. The map is the designer’s. Your job is to solve it.

Rogue Tower, from the small studio Die of Death Games, tears up that contract on the first wave. You start with one tower and a stubby fragment of road. After each wave clears, the game asks a question no tower defense game has really asked before: which way should the road go next? You pick the direction. You pick the terrain it crosses. The battlefield is not a level you’re solving — it’s an artifact of your own accumulated decisions, and it never looks the same twice.

The market positioning is straightforward, and honest. This is a voxel-styled, single-player, roguelike-structured strategy game that looks like a prototype and plays like a thesis. It arrived on Steam in January 2022, in the post-Slay the Spire wave of “genre X, but with run-based progression and a card reward pool,” a formula that produced a lot of cynical retrofits. Rogue Tower is not one of them. The roguelike structure here isn’t a monetizable content treadmill bolted onto an existing genre; it’s the mechanism that makes the map-drawing idea legible. Randomized reward cards mean you can’t pre-plan a build. Player-authored paths mean you can’t pre-plan a layout. The two systems feed each other.

The reception on Steam has been solidly positive for a game with essentially no marketing, no multiplayer, and no art budget — and, as we’ll get to, an irritating set of quality-of-life omissions the developer was told about loudly and repeatedly.

• Player-Authored Enemy Paths: After each wave, you choose the direction the road extends. The map is procedurally generated and player-directed — a combination that makes every run a fresh geometry problem rather than a memorized solution.
• Terrain That Actually Matters: Elevation grants range and damage bonuses. Water and forest tiles restrict placement. Towers draw power from adjacency and sightlines. Where you build carries as much weight as what you build, which is not true of most games in this genre.
• A Large Upgrade and Unlock Card Pool: Run rewards let you commit to specialization — fire and poison damage-over-time stacking, armor shredding, slow fields, gold generation. The stacking interactions are where the game’s real depth lives.
• Enemies Built to Punish Monobuilds: Healers, sprinters, spawners, and armored variants escalate in composition. A pure single-damage-type tower line will hit a wall, and the game does not apologize for it.
• Experience-Based Meta Progression: Cross-run XP permanently adds towers and modifiers to the reward pool, alongside harder difficulty tiers, an endless mode, and a long list of Steam achievements.

The Gameplay Loop

The loop looks simple and is quietly vicious. Wave spawns. Enemies walk. You spend gold. Wave clears. You extend the road. Repeat, for the better part of an hour.

What makes it work is the tension baked into that road-extension choice. Extending toward open high ground gives your existing towers more sightlines and more elevation multipliers — but it also gives enemies a short, efficient route to your core. Extending into a dense forest chokepoint forces a long winding path that buys you time, but forest tiles block placement, so you’ve built a corridor you can’t properly cover. Every expansion is a trade between path length (time on target) and buildable coverage (damage on target). You will get this wrong. Frequently. The failure will be entirely legible as your own fault, which is the mark of a well-tuned strategy game.

The card system is where the long tail lives. With a pool this wide, runs diverge structurally, not cosmetically. A run that offers early poison-stacking cards becomes a fundamentally different game from one that hands you armor shred and slow fields. The DoT builds are the standouts: layered fire and poison applications that scale multiplicatively against high-health late-wave enemies, ideally mounted on elevated ground where the range bonus lets a single tower service three path segments at once. When it clicks, the satisfaction is chemical — the “one more run” hook is built into the structure itself.

Where the Design Strains

The reward pool’s breadth is also its liability. Deep into the endgame, and especially across the hardest achievements, the variance stops feeling like texture and starts feeling like a gate. Runs at that level can be effectively decided by whether a specific enabling card surfaces in the first several waves. There’s no card-removal mechanic, no reroll economy, no meaningful draft agency to smooth the distribution. A roguelike with this much mechanical depth needs a lever for mitigating bad luck, and Rogue Tower simply doesn’t offer one. On standard difficulty this is a non-issue. On the ceiling content, it’s the main event.

Interface and Onboarding Friction

The UI is functional and ugly, in roughly that order of priority. Information density is decent — a tower’s stats, damage type, and upgrade path are generally findable — but there’s no unified encyclopedia of interactions, and with a card pool this large and a system built on adjacency, elevation, and status stacking, the game asks you to reverse-engineer its math from observation. Experienced strategy players will treat that as a feature. Newcomers will bounce off the first few runs without understanding why they lost, which is the worst failure state a roguelike can have.

The Missing Button

Then there’s the fast-forward problem, and it deserves its own paragraph because it’s the single most consequential decision in the game’s development history.

There is no speed-up button. None. In a game where runs run long, where early waves are trivially resolved, and where large stretches of a run are spent watching voxel enemies trudge along a road you already know they can’t survive, the game gives you no way to compress dead time. This was the most requested feature by a wide margin. The developer declined.

The compounding failure: there is no mid-run save and no cloud save. A run is atomic. You start it or you don’t. That combination — long mandatory runs, no time compression, no interruption handling — is a hostility toward the player’s schedule that no amount of clever design fully excuses. It’s the difference between a game you can slot into a weeknight and one that demands a block of uninterrupted evening. For a large slice of the potential audience, that’s disqualifying.

The voxel aesthetic is a budget constraint wearing the costume of an art direction, and it mostly gets away with it. Blocky terrain reads elevation clearly at a glance, which is functionally important in a game where height is a stat. The color language separates water, forest, and buildable ground without effort. It is not beautiful. It is clear, and for a systems game, clarity is the higher virtue.

Performance is the likely trouble spot, and it’s structural rather than incidental. The game’s core premise — a map that continuously grows — means the late game inevitably ends up rendering a sprawling board with hundreds of simultaneous enemies, each carrying stacked status effects that need per-tick evaluation. An engine built for early-game scale was never re-architected for the endgame the design encourages, so slowdown deep into runs and in endless mode is a reasonable expectation. Combine that with no fast-forward and the late game becomes slow in two independent ways at once: slow by design, and slow by execution.

Steam-exclusive, single-player, mouse-and-keyboard. The good news is that this is the right and natural home for the game. Tower placement on a grid with elevation and adjacency considerations wants a precise cursor and rapid hover-to-inspect, and the mouse delivers both. There’s no controller pretense, no touch compromise, no mobile port dragging the interface toward chunkier targets.

The Steam integration is where the platform story gets uneven. The achievement list gives the meta-progression a spine and gives completionists a genuine campaign beyond the mechanics — a smart use of the platform. But the absence of Steam Cloud saves is indefensible. It’s a checkbox. For a game whose sessions are this long and this fragile, shipping without it and never adding it tells you something about the post-launch trajectory: the developer went quiet after release, and the patch list reflects it. Deck compatibility is workable given the mouse-centric design and trackpad, but the long-session, no-mid-run-save structure fights the handheld use case the Deck exists to serve.

Rogue Tower is the most interesting thing to happen to tower defense in years, and it’s held back by omissions that would have taken a competent developer a weekend to fix.

The central idea is excellent — not clever-for-an-indie, genuinely excellent. Handing the player authorship over the enemy path converts tower defense from a puzzle you solve into a system you negotiate with, and the terrain rules give that negotiation real teeth. The card pool is deep enough to sustain dozens of hours, the enemy escalation is tuned to punish laziness, and the meta-unlock loop does its job without turning into a grind wall.

But a design this good deserved better stewardship. The refusal to add a speed control is the kind of stubbornness that looks like principle from the inside and looks like contempt from the outside. Pair it with no mid-run save, no cloud save, and an engine likely to strain precisely when the game gets interesting, and you have a title that excels at its hardest problem and fails at its easiest ones. The silence after launch is the real disappointment — these weren’t unknown flaws. Nobody came.

We recommend it if the premise excites you and the schedule can absorb hour-long commitments; there’s an enormous amount of strategy here for the money. Skip it if the games need to respect the clock. Either way, someone is going to take this path-drawing idea, give it a speed slider and a save file, and make the definitive version. Rogue Tower will deserve the credit.