Guide

Turn-based tactics game design explained

Your sniper holds overwatch on the warehouse door. Two enemies peek — one dies instantly, the other ducks behind a crate. You spend your last action point to flank, but the grenadier you forgot about was on overwatch too. Your medic is exposed, and the mission objective timer ticks down. That tension is the turn-based tactics (TBT) contract: every tile and every action point is a bet, and the board state is fully readable once you learn the rules. Unlike real-time strategy where attention splits across the map, tactics titles slow time so players optimize positioning, initiative, and ability combos on a squad scale. This guide covers subgenres (grid tactics, squad tactics, tactical RPG hybrids), movement and action economies, cover and elevation, class roles, overwatch and reaction systems, fog of war at encounter scale, permadeath stakes, a Harbor Vanguard warehouse skirmish worked example, a subgenre decision table, common pitfalls, and a production checklist — complementing strategy game design without repeating its macro-economy focus.

Subgenres: grid tactics, squad tactics, and tactical RPGs

“Turn-based tactics” spans games with different spatial models, squad sizes, and narrative weight. Pick one before tuning numbers:

Grid tactics (Japanese-style) — discrete tiles, often smaller squads (4–12 units), weapon triangles and class promotion. Examples: Fire Emblem, Advance Wars, Triangle Strategy.
Squad tactics (Western-style) — larger maps, smaller playable squads (4–6 soldiers), heavy cover and line-of-sight simulation. Examples: XCOM, Xenonauts, Gears Tactics.
Tactical RPG (TRPG) — grid or free movement with deep character builds, equipment, and story chapters. Examples: Final Fantasy Tactics, Tactics Ogre, Divinity: Original Sin (hybrid).
Roguelite tactics — procedural maps and permadeath runs with lighter narrative. Examples: Into the Breach, Wildermyth, Fell Seal.

The subgenre choice drives everything: a 6×6 Fire Emblem map needs different chokepoint density than a XCOM warehouse with three floors and destructible walls.

Movement and action economies

TBT games answer two questions each turn: how far can I move and what else can I do. Common models:

Action points (AP)

Each unit spends AP from a pool per turn — move costs 1 AP per tile, shoot costs 2, reload costs 1, etc. Leftover AP can bank or expire. XCOM’s model (move + one action, or dash for double move) is a simplified AP system that reduces analysis paralysis for newcomers.

Move + action split

Fire Emblem and many TRPGs grant one move range and one action (attack, item, skill). Some classes get Canto (move again after acting) or Galeforce (act again after killing). These exceptions define class identity — budget them carefully.

Initiative and turn order

Phase-based — all player units act, then all enemies (classic JRPG). Simple but allows alpha-strike wipes.
Initiative queue — speed stat determines order each round; faster units act more often.
Alternating activation — one player unit, one enemy unit, repeat (Into the Breach). Keeps pressure constant and prevents snowball alpha strikes.

Turn order is a hidden difficulty knob: phase-based player phases feel powerful but make enemies swingy; alternating activation is fairer but demands tighter enemy AI.

Spatial design: grids, cover, and elevation

Grid vs free movement

Tile grids make range math legible — a bow with range 3 hits exactly three tiles away. Free movement with grid snapping (XCOM) adds organic positioning while keeping cover tiles discrete. Pure free movement (some TRPGs) trades clarity for cinematic flair; telegraph range with overlays.

Cover systems

Half cover reduces hit chance; full cover blocks line of sight. Destructible cover (XCOM 2) creates dynamic puzzles — the sniper’s wall becomes rubble after a grenade. See cover systems design for snap, peek, and flanking detail; in TBT, flanking often grants bonus damage or ignores cover entirely.

Elevation

High ground typically grants accuracy and vision bonuses; low ground penalizes. Multi-floor maps multiply decision space — stairs become chokepoints, and dropping from a balcony is a one-way gamble. Mark elevation clearly; players who cannot read height lose unfairly.

Chokepoints and flanking routes

Good tactical maps offer a main lane (defensible, slow) and a flank (risky, fast). If only one path exists, overwatch and area denial dominate; if too many flanks exist, cover becomes meaningless.

Class roles, counters, and ability design

Squad tactics live on role differentiation — each unit should answer a distinct question on the board:

Frontline / tank — absorbs damage, holds chokepoints, taunts or zones enemies.
DPS / skirmisher — finishes exposed targets, chases low-health enemies.
Ranged / sniper — high damage at distance, vulnerable when flanked.
Support / medic — heals, buffs, revives; force enemies to prioritize or ignore at a cost.
Control / utility — stuns, slows, smoke, hacking; creates windows for the squad.

Weapon and class triangles

Fire Emblem’s sword beats axe beats lance beats sword is a readable counter loop. Western tactics often use armor types (light vs heavy) or damage types (kinetic vs explosive). Counters should be learnable from one tool-tip, not hidden in a wiki.

Overwatch and reactions

Overwatch (shoot when enemy enters zone) and reaction attacks (counter when struck) add deterrence without extra turns. Budget reaction frequency — unlimited overwatch on six soldiers makes enemy turns feel hopeless. Cooldowns, limited charges, or “one reaction per round” keep tension.

Abilities and cooldowns

Grenades, smoke, psi powers, and class skills break stalemates. Tie powerful abilities to mission-long scarcity (one grenade per soldier per mission) or turn cooldowns. Abilities that skip the action economy (free kills, full-map heals) need sharp limits.

Information, fog of war, and AI

At squad scale, fog of war means unseen enemies are threats, not surprises. Reveal rules matter:

Enemies outside vision are hidden but may fire if they hear gunshots.
Last-known-position markers help players plan without perfect intel.
Scouting abilities (drones, high mobility units) trade actions for information.

Enemy AI should telegraph intent on higher difficulties through posture changes, not read the player’s hidden positions. Cheating AI erodes trust faster in TBT than in action games because players have time to analyze unfairness.

Scale AI in layers: easy AI misses shots and ignores flanks; normal uses cover and focus-fire; hard coordinates overwatch and ability combos. Document AI priorities (kill wounded, protect VIP, hold high ground) per encounter.

Stakes: permadeath, ironman, and meta-progression

TBT games often attach permanent consequences to tactical mistakes:

Permadeath — fallen units leave the campaign (Fire Emblem classic, XCOM ironman). Raises emotional stakes but can cause reload loops.
Injury timers — units sit out N missions; softer than death but still costly.
Rescue / retreat rules — reaching a downed unit before bleed-out creates rescue missions within missions.
Meta-progression — roguelite tactics unlock new units or abilities between runs; keeps permadeath palatable.

Match stakes to audience: casual players choke on ironman; hardcore fans consider anything less “not real XCOM.” Offer explicit difficulty and ironman toggles at campaign start.

Worked example: Harbor Vanguard — Warehouse Skirmish

Harbor Vanguard is a fictional squad tactics game. Mission 3, “Cold Storage,” teaches overwatch, elevation, and flanking in one encounter.

Setup

Map: 24×16 tiles, single floor warehouse with crate stacks (half/full cover), a 2-tile elevated catwalk, and two entry points (main bay door, side loading dock). Squad: 4 units (vanguard, sniper, medic, grenadier). Enemies: 6 raiders + 1 elite on overwatch duty. Objective: reach and hack a terminal in the far corner within 8 turns.

Design intent

Turn 1–2: Main door is a kill zone — enemy sniper on catwalk has overwatch. Players learn to use smoke or side entrance.
Turn 3–4: Side entrance exposes flank but triggers reinforcement spawn (2 raiders) — teaches timing and focus fire.
Turn 5–6: Catwalk accessible via interior stairs; taking high ground flips overwatch advantage.
Turn 7–8: Terminal hack takes 2 turns (medic can defend); last enemies rush — tests whether squad preserved abilities.

Tuning notes

Raider accuracy is 65% in cover, 85% on exposed targets — players feel smart when using crates. Elite overwatch fires once per enemy turn; destroying catwalk cover with grenadier rocket removes the threat permanently. If playtests show >40% mission failure, add a tutorial prompt on turn 1 highlighting the side entrance.

Subgenre decision table

Your goal	Favor	Watch out for
Deep character attachment + story	Tactical RPG with permadeath optional	Grid size vs narrative pacing; cutscene fatigue
Accessible squad management	Western squad tactics (move + action)	Analysis paralysis on large maps
High replayability, short sessions	Roguelite tactics (Into the Breach model)	Procedural maps that feel samey
PvP competitive fairness	Small grid, alternating activation	First-move advantage; mirror-match balance
Mobile / touch-first	Small squads, large tap targets, phase-based turns	Long enemy phases; tiny UI buttons

Common pitfalls

Alpha-strike player phases — letting the player kill every enemy before they act removes tension; use reinforcements, alternating activation, or overwatch-heavy defenses.
Opaque hit formulas — if players cannot predict 72% vs 45% shots, they blame RNG instead of positioning.
Units without a job — redundant riflemen with identical stats waste roster slots; differentiate or cut.
Maps with one optimal strategy — if flanking is always correct, main lanes are decorative.
Enemy AI that knows hidden positions — instant trust killer in a genre built on planning.
Permadeath without telegraphing — one-shot crits from full health feel cheap; show high-damage telegraphs.
Turn length bloat — 20-unit armies with long animations exhaust mobile players; trim or add speed-up.
Ignoring verticality UI — players miss catwalk threats when height is subtle.

Practical checklist

Document AP or move+action costs for every unit action; verify no infinite loops (free moves, zero-cost kills).
Every map has at least two viable approaches (direct + flank).
Cover tiles visually distinct; elevation difference readable at default zoom.
Hit chance preview before committing attack.
Class roles listed in unit select; weapon triangle shown in UI.
Overwatch and reaction rules in a one-screen reference.
Enemy AI debug overlay in dev builds (target priority, cover search).
Mission fail states explained upfront (timer, VIP death, squad wipe).
Ironman / permadeath chosen at campaign start, not mid-save.
Median mission length within target (often 15–30 minutes for squad tactics).

Key takeaways

Turn-based tactics sell readable bets — positioning and action economy must be legible before players trust the dice.
Subgenre choice (grid vs squad vs TRPG) sets map size, squad count, and narrative weight.
Cover, elevation, and flanks create the decision space; one-path maps collapse tactics into puzzles.
Class roles and counters give each unit a reason to exist on the board.
Stakes (permadeath, timers, ironman) amplify tension but must match audience expectations.