Running Combat Encounters as a Game Master
Combat is where preparation meets improvisation, and where a game master's decisions have the most immediate, visible consequences at the table. This page covers the mechanics and judgment calls behind running tactical combat — from initiative tracking and action economy to encounter pacing and the moment a GM decides whether a monster fights to the death or runs. Whether the system is Dungeons & Dragons 5th Edition, Pathfinder 2e, or something rules-lighter, the underlying craft translates.
Definition and scope
A combat encounter is a structured conflict between player characters and one or more opposing forces, resolved through a game system's mechanical rules rather than pure narrative description. The scope extends beyond "rolling dice to hit things." It includes the GM's design decisions before the first sword is drawn — terrain placement, enemy composition, encounter difficulty calibration — and the live decisions made mid-fight: when enemies act tactically, when they break, and when the GM fudges nothing and lets a natural 20 decapitate someone important.
The history of tabletop RPG shows that combat has been central to the hobby since Gary Gygax and Dave Arneson adapted Chainmail's wargame rules into what became Dungeons & Dragons in 1974. Decades later, the basic architecture — turn order, attack rolls, hit points, saving throws — remains the structural spine of most systems, even as design philosophy has shifted dramatically.
Not all systems treat combat identically. Narrative vs. rules-heavy RPG systems diverge sharply here: Powered by the Apocalypse games like Apocalypse World resolve violence in 2–3 moves with minimal tracking, while Pathfinder 2e's three-action economy and 13 condition types reward tactical depth across encounters that can run 45–90 minutes per fight.
How it works
Most combat-heavy systems share a common architecture, even when the details differ:
-
Initiative — Players and enemies roll or draw to establish turn order. D&D 5e uses a d20 + Dexterity modifier. Pathfinder 2e uses Perception. Some narrative games skip initiative entirely and let the fiction determine who acts first.
-
Action economy — Each combatant gets a defined set of actions per turn. In D&D 5e, that's one Action, one Bonus Action, one Reaction, and movement. In Pathfinder 2e, it's 3 actions — a system that rewards players who understand three-action combos, since a move-move-Strike sequence differs strategically from move-Strike-Strike.
-
Attacks and defenses — Most systems resolve attacks through opposed rolls or a target number (Armor Class in D&D, Armor Class or Defense in other systems). Damage is applied against hit points or an equivalent resource.
-
Conditions and status effects — Blinded, stunned, prone, frightened — conditions multiply tactical complexity and are where many GMs underutilize enemy abilities.
-
Encounter end states — Combat ends when one side is defeated, flees, surrenders, or is incapacitated. A GM who only ends fights through total party victory is running a narrower game than the rules support.
The GM's primary mechanical task is running all non-player combatants simultaneously while tracking initiative order, HP pools, and environmental effects. In a 5-player D&D session with 4 enemies, that's up to 9 active trackers at once.
Common scenarios
Three encounter shapes recur across most campaigns:
The attrition fight — A prolonged engagement designed to drain player resources. The GM populates it with 6–10 low-difficulty enemies rather than a single powerful one. The danger isn't any individual hit; it's the cumulative cost of spell slots, hit points, and abilities that won't recover before the next fight.
The setpiece boss encounter — A single powerful enemy, often with legendary actions or lair actions (per D&D 5e's Monster Manual framework). These encounters emphasize dramatic pacing. A GM who kills the boss in round 2 because the dice said so has failed the moment, not the rules. Game master prep techniques address how to design these encounters with built-in flexibility.
The ambush or asymmetric encounter — Players are outnumbered, outpositioned, or missing key resources. The design goal isn't fairness; it's pressure. These encounters test whether players will fight, flee, negotiate, or improvise. From the getting started with tabletop RPG perspective, ambushes often teach new players that running away is a legitimate tactical choice — sometimes the only one.
For players looking at the same moments from the other side of the screen, tabletop RPG combat strategy for players covers action economy optimization and positioning in detail.
Decision boundaries
The hardest GM decisions in combat aren't mechanical — they're about intent and fairness.
Enemy intelligence — Does the goblin archer target the wounded rogue or the heavily-armored fighter? Monsters with Intelligence scores of 3 fight stupidly. Veteran soldiers do not. Playing every enemy at maximum tactical efficiency punishes players who make any mistake; playing every enemy at zero intelligence is boring. The realistic middle ground: enemies pursue their goals, not optimal win conditions.
Fudging dice — Some GMs roll behind a screen and adjust results to protect narrative momentum. Others roll in the open and commit to outcomes. Neither is wrong, but the choice should be deliberate and consistent. A GM who fudges only when PCs are losing has made a silent promise about consequence that shapes player trust across the entire campaign.
Retreat and surrender — The tabletoprpgauthority.com home reference treats these as legitimate encounter outcomes, not failure states. An enemy who flees becomes a recurring antagonist. An enemy who surrenders opens negotiation. Both options make the world feel more alive than a room that resets to empty after every fight.
The how to be a game master resource frames this well: the GM's job in combat isn't to win or to lose — it's to make the outcome feel earned.