Ch.3: The Unstoppable Unit Is Bad Game Design

0:00 Welcome to Learning Podcasts. RTS Game Design: Why No Unit Can Win Every Matchup. Picture this. The player finally gets the unit that looked unstoppable. It wins the first fight, marches across the map, meets the wrong target, and the whole plan falls apart in about 12 seconds. Honestly, I've been that player. My first thought is always that I built the wrong number of them, not that the unit itself has a job description. Right. And that's the lesson sitting underneath the loss. Strength isn't a property of the unit.

0:32 It's a property of the matchup. Yeah. And that's the actual lesson. A unit can be powerful without being universal. In a good RTS, no single answer quietly deletes scouting, adaptation, and army composition. So the design problem here has a name. It's called a dominant strategy. One choice that's so reliable, so efficient, and so low-risk that the player should just keep picking it. That sounds convenient for the player and, Terrible for the game. Yeah, exactly. If one unit beats infantry, armor, buildings, air, harassment, and timing attacks, the roster collapses into a shopping list with 1 item on it.

1:15 Build the good one. More of the good one. Maybe, you know, a dramatic amount of the good one. Classic. And the moment a player figures that out, the game stops being strategy and starts being a build order. Right. Strategy needs multiple viable answers. Counter design is how the roster tells the player, this unit has a job, but it doesn't have every job. Okay, let's unpack this. A hard counter is the clean version. Clear answer beats clear threat. Anti-air beats air. Siege punishes static defenses.

1:49 Fast raiders punish undefended economy. The upside is legibility. Yeah. The player sees the threat, knows the answer, and gets a decisive pivot if they prepared correctly. Okay, but I've seen hard counters that feel almost too sharp. Where you scout the threat, build the answer, and the fight is basically over before it starts. Yeah, that's the failure mode on this side. If the answer deletes the threat instantly, with no scouting burden and no execution demand, the interaction stops being strategy and starts being, Matching icons.

2:24 Hard counters are good when they create clarity. They're bad when they remove play. Soft counters are the other half of that picture. A soft counter gives an advantage without making the fight automatic. Range can pressure melee. Mobility can avoid slow damage. Splash can punish clumps. Armor type can bend the numbers. So the better unit isn't guaranteed to win. Right. Terrain, upgrades, positioning, focus fire, numbers, and timing can all change the result. I love that, because soft counters preserve skill expression.

2:59 The player who reads the matchup well gets an edge, and the player who controls the fight better can still matter. That's the sweet spot, honestly. The matchup tells you who has the advantage, but it doesn't tell you the outcome. A roster also needs role overlap. Two units can both fight light units, but one arrives earlier, one scales better, one's cheaper, and one is safer behind a wall of other units. Without overlap, the counter chart gets brittle. Yeah. The player is forced into one prescribed answer.

3:29 With useful overlap, they're choosing between timing, cost, risk, tech path, and control difficulty. So overlap isn't redundancy if the tradeoffs are real. Exactly. Redundancy says these two units do the same thing. Design overlap says these two units answer a similar problem in different strategic languages. That's a great way to put it. The first phrasing flattens the roster. The second one keeps the decisions alive. Here's where it gets really interesting. Cost is one of the quietest counter systems in the whole genre.

4:03 A powerful unit can be allowed to win many straight fights if it's expensive, slow to replace, tech-gated, or bad at covering the whole map. Wait, really? So the counter might be economic, not tactical? Yeah. You don't always beat the expensive unit by winning a front-on fight. You might force it to defend two places, trade cheaper units into its support, or attack before the investment pays back. So value isn't just who wins one clean arena fight. Right. The real question is what the unit costs the player in timing, attention, flexibility, and risk.

4:39 I've lost more games to this than I want to admit, where the expensive unit wins every fight and I still lose because it never got to where it needed to be. Oh, interesting. I've been there too, honestly. The unit is undefeated and the match is already over. And timing is where counter design really starts moving. A unit can be oppressive now, fine later, and underwhelming after upgrades arrive. So the unit's strength has a half-life. Pretty much. Early aggression can punish greedy tech. Midgame units can own the map before late-game answers exist.

5:15 Late units can be strong, but, They arrive after the opponent has had chances to scout, pressure, or expand. So the counter lives on the clock. Exactly. A matchup isn't just unit A versus unit B. It's unit A at this minute, with this economy, against unit B that may or may not exist yet. And that's the part new players miss. They lose to a unit at minute 8 and think they need that same unit. The real fix is usually 3 minutes earlier. Counters only become strategy if the player can discover what's coming.

5:49 If the threat is completely hidden until it arrives, and the answer had to be started a minute earlier, the counter is theoretically correct and practically useless. Oh, man. That's the worst feeling. I know the answer, but the game didn't let me know the question. Right. Scouting cues are part of counter design. Tech structures, map movement, missing units, unusual resource choices, attack timing, even where the opponent isn't on the map. So the player needs information trails. Yeah. Fog of war should create uncertainty, not pure surprise with no recovery path.

6:26 I didn't realize how much I was missing until I started watching replays from the opponent's side. Half the time the information was sitting there, and I just wasn't looking. I think every player goes through that phase, honestly. Execution is what keeps counters from becoming spreadsheet answers. Range matters only if the player can kite. Splash matters only if the opponent clumps. A fragile unit can counter something powerful only if it's protected. And focus fire can reverse a lot of lazy assumptions.

6:55 Yeah. A counter should create pressure toward good play. It shouldn't always skip the fight. But isn't that hard to tune? If execution matters too much, the counter disappears for normal players. If it matters too little, the matchup becomes automatic. That's the whole problem. The best counters give the player a plan, then still ask them to execute it. There's no clean answer. The map is part of the matchup. A unit that's terrifying in open ground may be awkward in a choke. A short-range unit may love corners.

7:26 A fragile ranged unit may need retreat space. So the same army composition can be correct on one map area and wrong on another. Yeah. Elevation, ramps, open fields, bridges, base entrances, and expansion spacing all change what counters what. That's why a roster can't be judged only in a blank test arena. Test arenas are useful, but real RTS fights happen in places. The place changes the value of range, mobility, splash, and escape. And the better players know which fights to take where. The unit doesn't change. The ground underneath it does.

8:03 Now here's where it gets really interesting, in a dark way. A counter becomes oppressive when it removes recovery. No scouting cue, no alternate answer, no micro window, no timing weakness, no cost exposure. Oh, man. That's the nightmare version. It really is. The player loses not because they read the game badly, but because the correct response was invisible or unavailable. That would be a disaster for any competitive game. Oppressive counters often feel like the game saying, you should have known, without showing how.

8:36 Exactly. Sharp counters are allowed. Surprise is allowed. Punishment is allowed. But the player needs a credible path from information to decision to response. Otherwise the lesson isn't adapt faster. The lesson is memorize the trap. And the opposite failure is just as bad. A counter that exists only on paper. It's too expensive, too late, too fragile, too hard to access, or too narrow to justify building. Hold on. So the unit technically answers the threat, but nobody actually wants to make it?

9:09 Right. That's not a real answer. If the counter loses unless everything is perfect, the dominant unit may still control the game. I've shipped that bug in my own designs, actually. Not in RTS, but the same shape. The fix existed, on paper, and nobody used it because the cost was wrong. Yep. Designers have to watch usage, timing, and opportunity cost, not just one isolated fight. A counter has to be reachable in the actual match flow. If the answer arrives after the damage is done, it's a museum exhibit, not a tool.

9:39 So zooming out, a good roster isn't a line of isolated units. It's a network of roles and answers. Some units punish massing. Some punish greed. Some punish immobility. Some punish bad scouting. Some create windows instead of ending the game. That network shape is the balance. Yeah. You want each unit to have a reason to exist, a reason not to mass it forever, and at least one meaningful way the opponent can respond. So the counter chart is only the sketch. Right. A unit that's only a counter can be fragile design too.

10:14 If it exists for one narrow punishment and nothing else, it disappears the moment that threat isn't common. The best units usually have a main job, pressured matchups, and reasons to combine with other units instead of replacing them. The real design includes cost, timing, information, map context, execution, and how all those relationships shift as the match develops. So pulling all of that together, counter design isn't just rock-paper-scissors. It's how an RTS roster preserves choices. Hard counters create clarity. Soft counters preserve control.

10:50 Cost and timing create exposure. Scouting turns counters into decisions. Terrain makes the matchup local. And no unit gets to win every matchup, because the moment one unit solves everything, the rest of the roster becomes decoration. Next, we look at fog of war: how hidden information creates tension, bluffing, and the moment a player realizes the army they prepared for is not the army coming across the map. Thanks for listening to Learning Podcasts.