D&D 5e Tactical Combat Questions for Dungeon Masters

Terrain makes goblins effective when it gives them safe ways to reposition, break line of sight, and force the party to choose where to spend movement and attention. The goal is not to give goblins arbitrary bonuses; it is to build a battlefield where their normal strengths matter.

Use several connected positions rather than one defensive line. Low walls, dense brush, side tunnels, murder holes, rooftops, ledges, crawlspaces, rope bridges, or narrow passages let goblins attack and then move somewhere the characters cannot immediately follow. Cover is useful, but escape routes are what keep the fight mobile.

Add terrain that creates decisions rather than automatic penalties. A muddy slope may be slower but safer than the exposed road. A narrow bridge may provide the fastest route to the archers but leave a character isolated. A barricade might be climbed, broken, burned, or bypassed through another chamber.

Give the goblins a reason to know and exploit the area. They may have prepared warning bells, fallback positions, hidden exits, or places where larger pursuers cannot easily follow. If the party scouts, approaches from another direction, blocks an escape route, or turns the terrain against them, let that preparation pay off.

Good goblin terrain creates a pursuit and positioning problem, not just a higher Armor Class.

Make whips and nets matter by creating situations where controlling movement or restraining someone is worth more than simply dealing the most damage.

Under the current rules, a whip is a 1d4 slashing martial melee weapon with Finesse and Reach. Its mastery property is Slow, which can reduce a creature's Speed when used by a character who can access that mastery. A net is now adventuring gear rather than a weapon: a character taking the Attack action can replace one attack by throwing it at a visible creature within 15 feet. On a failed Dexterity save, an eligible target becomes Restrained until it escapes or the net is destroyed. ([D&D Beyond][1])

Those abilities become valuable when the encounter asks a different question than "Who can remove the most Hit Points?" Use fleeing enemies carrying information, prisoners who must be captured alive, rituals that must be interrupted before someone reaches a location, narrow passages where movement matters, or enemies trying to escape with an object. A restrained courier or a slowed creature ten feet short of the exit can matter more than another damage die.

Do not silently give the whip old-edition abilities such as automatic grappling or limb-pinning. If you want those maneuvers, make them explicit homebrew or adjudicate a particular fictional action separately rather than pretending the weapon's normal statistics grant them.

The easiest way to make unusual equipment attractive is therefore not to inflate its damage. Give the encounter objectives that reward what the equipment already does differently.

Enemies should focus fire when their intelligence, goals, and battlefield information make that tactic believable, but using it automatically in every fight makes the DM's optimization more visible than the creatures' behavior.

Ask what the enemies can actually perceive. Trained soldiers may recognize a dangerous spellcaster, coordinate attacks, and try to remove one threat quickly. Predators may isolate the smallest or wounded target. Mindless creatures may simply attack what is nearest. A proud champion may stay on the opponent who challenged them even when switching targets would be mathematically better.

When focus fire is especially dangerous, telegraph it. Officers shout commands, archers reposition, or hunters surround a limping character. That gives players a chance to react with cover, movement, control effects, healing, or a change in formation instead of experiencing concentrated damage as an invisible tactical decree.

Also distinguish defeating a character from finishing one off. Whether enemies keep attacking a fallen foe should follow motive and circumstance: assassins, starving beasts, and terrified conscripts do not value the same things.

Use focus fire as part of enemy characterization. Varying tactical discipline makes encounters more believable and keeps difficulty from depending only on higher numbers.

Make the docks change what the combatants are trying to do, not just what the battle map looks like. Water, boats, cargo, cranes, narrow piers, warehouse doors, mooring lines, and changing elevation can all create decisions if they affect objectives and movement.

Give the fight a purpose beyond eliminating every enemy. The party might need to stop a ship from leaving, rescue someone from a sinking boat, protect cargo, reach a warehouse before it burns, or capture a smuggler alive. Then choose terrain that complicates that goal: a retracting gangplank, a drifting barge, stacked crates that block sight, slippery edges, or a crane carrying something valuable overhead.

Let combatants use the location intelligently. Dockworkers know shortcuts, smugglers cut lines, ranged attackers seek rigging or rooftops, and frightened civilians create moving obstacles. Introduce one environmental change after the players understand the initial layout: a ship pulls away, fire spreads, a crane collapses, or the tide moves a floating platform.

Avoid turning every feature into a compulsory check. Terrain is most useful when players can exploit it deliberately and when good positioning changes the situation. A memorable dock fight should feel impossible to transplant unchanged into an empty stone room.

Use consistent adjudication for shared rules, but do not require enemies to imitate player tactics or be built like player characters. An enemy should fight according to its own abilities, intelligence, goals, information, and willingness to take risks. Fairness comes from understandable rules and credible behavior, not from tactical symmetry.

If the party discovers a strong tactic, ask whether opponents in the fiction could know about it. A recurring rival who has watched them may prepare a counter. A random beast should not suddenly behave as though it has read the characters’ sheets. That distinction keeps adaptation from feeling like punishment for effective play.

The same principle applies to retreat, focus fire, ambushes, and battlefield control. Trained soldiers may coordinate; frightened bandits may break; an undead guardian may keep attacking despite terrible positioning because its purpose is to hold a doorway.

When an NPC ability works differently from a player option, describe what the characters can observe and adjudicate the written effect consistently. Players do not need identical construction rules to make informed decisions; they need reliable cause and effect in play.

Rules reference: D&D 5e SRD 5.2.1 — Monsters: Parts of a Stat Block.

A morale check is most useful when it answers whether an enemy is still willing to pay the cost of the fight, not merely whether it is frightened. That lets similar stat blocks behave like different creatures because their reasons for fighting are different.

D&D 5e does not need a morale roll in every combat. Treat it as an optional table procedure triggered when the situation changes enough to make continued fighting doubtful. Good triggers include a leader falling, half a group being defeated, an escape route opening, a mission being completed, reinforcements failing to arrive, or an unexpectedly dangerous opponent revealing itself.

Decide what failure means from the enemy's motivation. Mercenaries might retreat when the payment no longer justifies the risk. Predators may abandon wounded prey rather than die for a meal. Guards could surrender once the person they were protecting escapes. Fanatics might ignore casualties but break immediately if the object of their devotion is destroyed.

The result also does not have to be simple flight. Morale can produce surrender, negotiation, a fighting withdrawal, panic, a change of objective, or an attempt to save a wounded ally.

For ordinary enemies, three notes are often enough: why they are fighting, what might break their commitment, and what they do when that happens. Whether the DM resolves the uncertain moment with a house-rule roll or judgment, those fictional triggers matter more than adding another combat ability to the stat block.

Make the underwater lair actions change position, visibility, and the rescue clock rather than simply adding more damage. The fight already has a strong objective—get the captive dragon back to the surface—so the environment should keep forcing decisions about that objective.

One round, a downward current can pull unsecured creatures deeper. Another can sweep a line of piranhas through a marked area, forcing the party to move or accept damage. A burst of silt or bubbles can heavily obscure part of the battlefield, separating the rescuer from allies. You can also create temporary advantages: an upwelling current pushes a creature toward the surface, or an air pocket buys the drowning captive another round.

Telegraph each effect before it resolves. Describe the water beginning to rotate, bubbles racing downward, or fish scattering from an approaching current. That gives players a chance to react instead of treating the lair action as unavoidable punishment.

Most importantly, let character actions alter the clock. Passing the dragon to a faster swimmer, cutting a tether, reaching an air pocket, or forcing the mermaid to release it should matter more than simply reducing enemy hit points. The water then becomes part of the encounter's tactics, not just a blanket disadvantage.

Use miniatures when spatial information will change decisions. They are most valuable when cover, chokepoints, elevation, reach, hazards, movement routes, or the distance between characters matter enough that everyone benefits from seeing the same geometry.

The map should do more than measure squares. Put visible features on it that can be interpreted and exploited: tables to overturn, doors to block, ledges to climb, smoke to cross, mud to avoid, crowds to move through, or machinery to activate. Then moving a miniature produces new fiction instead of only confirming range.

You do not need a grid for every scene. A simple sketch or theater-of-the-mind description is often faster when the exact position will not affect meaningful choices. Switching methods by scene keeps tactical detail from becoming automatic overhead.

Miniatures can also expose consequences the DM did not plan. A retreat route becomes blocked, an ally cannot reach someone in time, or an enemy sees an unexpected path around a defensive line. Those discoveries are a strength: the shared space is contributing to play.

The main warning is to avoid letting the map replace the imagined environment. Describe what the represented objects are, how they feel in the scene, and what characters can plausibly do with them. Position should support imagination, not reduce the world to coordinates.

Scale the opposition before adding a large NPC party. Two player characters have fewer turns, fewer specialties, and less ability to recover when one character is disabled, so simply filling the missing seats with DM-controlled adventurers can make the game feel balanced mechanically while leaving the players as spectators.

Build encounters for the actual number and level of player characters. Reduce enemy count first, especially when several foes can concentrate attacks on one character. Be cautious with monsters capable of dropping a character in a single strong action; losing one of two characters removes half the party’s actions immediately.

If the adventure needs an ally, use one simple supporting NPC with a narrow job: healing, guarding, carrying information, or covering a capability the party lacks. Let the players make the important plans and decisions. The ally should help execute their choices, not solve scenes before they can.

Also create noncombat escape valves. Retreat routes, negotiations, stealth, environmental advantages, and objectives other than “kill everything” give a small party ways to manage danger.

The goal is not to reproduce a four-character party. It is to make two protagonists feel capable while preserving the vulnerability that makes a small-party campaign distinctive.

Make the encounter difficult because the situation demands decisions, not because the enemy takes an excessive number of rounds to reduce to zero hit points. Durability is useful when it gives a fight enough time to develop, but it becomes tedious when nothing changes while the party repeats the same optimal actions.

Add pressure through objectives and changing circumstances. The party might need to stop a ritual before a countdown ends, keep enemies away from an injured guide, reach a mechanism on the opposite side of the battlefield, prevent an escaping messenger from leaving, or decide which of two simultaneous threats they can afford to ignore. None of those requires inflating the main enemy's HP.

Movement and information can also change the problem from round to round. An enemy can retreat to a defensible position, break a bridge, expose a hidden threat, call for help, abandon one objective for another, or reveal that the party misunderstood what mattered. Those changes should follow understandable motives rather than exist solely to frustrate attacks.

If you do give an enemy substantial durability, use those extra rounds. Let wounds, behavior, terrain, objectives, or available tactics evolve as the fight progresses. The question is not simply how long the monster survives. It is whether surviving longer creates another meaningful decision for the players.

Treat the square as a place with traffic, verticality, and people, not as an empty battle map with buildings around it. Start by giving the fight one feature that changes movement, one feature that creates a decision, and one objective beyond reducing enemies to 0 hit points.

A fountain, market stalls, wagons, balconies, statues, stairs, and narrow alleys can divide sight lines and create cover or elevation. Civilians fleeing through those spaces can force the party to choose between the quickest attack and the safest position. A bell tower, gatehouse, burning cart, loose animals, or collapsing awning can make the environment change after a round or two.

Give the enemies a reason to be there. They might be stealing a prisoner, holding a speaker long enough to finish a proclamation, escaping with a relic, or buying time for someone else. That produces movement and makes surrender, pursuit, and failure meaningful.

Keep the number of special elements manageable. Two or three strong features are easier to run than a square full of bespoke rules. Describe what characters can see and exploit, then let players invent uses you did not plan.

Slow the fiction, not the procedure. A combat can feel weighty even when turns move quickly if each decision has visible consequences and the situation changes from round to round.

Use brief descriptions at decision points rather than narrating every swing. When a creature is bloodied, a defense breaks, reinforcements appear, or terrain shifts, spend a few extra seconds showing what changed and why it matters. Give players enough sensory information to picture distance, danger, and intent before asking what they do.

If you want the fight itself to last more rounds, avoid simply inflating hit points. Add objectives that create phases: hold a doorway, stop a ritual, escort someone across the square, reach a lever, or survive until help arrives. Movement, changing goals, and enemy behavior create the impression of an extended struggle without turning it into repeated attack rolls.

Keep turn administration fast. Have the next player ready, resolve uncertain rules quickly, and cut descriptions once they stop affecting choices. The useful contrast is fast table rhythm with deliberate fictional moments: the players act promptly, but the important beats still have room to land.

Create tactical depth through the situation before adding mechanical complexity. A fight becomes strategic when position, timing, target priority, and objectives matter enough that the obvious attack is not always the best decision.

Start by giving each important encounter one meaningful spatial feature. That might be a narrow bridge, an elevated firing position, unstable ground, a doorway that can be defended, or an area the characters cannot afford to abandon. The feature should change decisions rather than merely decorate the map.

Then give the enemies complementary jobs. A durable creature can hold a route while a mobile enemy threatens the back line. A ranged attacker becomes more interesting when another creature makes reaching it difficult. You do not need a complicated new subsystem if the existing pieces create a problem the party must untangle.

Add an objective that competes with dealing damage: stop someone escaping, keep a mechanism operating, protect an NPC, seize an object, or reach a location before the enemy does. Finally, let the situation change once during the battle. Reinforcements arrive, the floor gives way, the target begins moving, or an enemy changes tactics.

A simple preparation rule is enough: one terrain decision, two enemy roles, one competing objective, and one possible change. That creates several interacting choices while leaving the rules themselves familiar. The complexity lives in the battlefield, where players can understand and act on it, rather than in another stack of modifiers and exceptions.

Add complexity to the situation rather than to the character sheets. D&D 5e combat becomes much more tactical when position, objectives, information, and enemy behavior change what the players should do from round to round.

Start with terrain that creates real choices. Elevation, narrow passages, unstable ground, cover, hazards, defensible positions, moving platforms, or separate routes matter only when combatants can exploit them. An archer occupying a balcony is more interesting if someone must decide whether climbing to reach them is worth abandoning another objective.

Then give the encounter a purpose beyond reducing every enemy to 0 Hit Points. Stop a ritual, keep a gate open, rescue prisoners, prevent an enemy from escaping, hold a position for three rounds, or choose which of two simultaneous threats to address. The strongest action may then be movement, interference, or accepting one loss to prevent another.

Enemies should also behave as participants rather than stationary collections of attacks. They can retreat to better ground, protect a leader, concentrate on an objective, call reinforcements, withdraw when morale breaks, or change tactics after discovering what the characters can do.

Finally, let the battle state change. A bridge collapses, smoke fills the chamber, the ritual advances, an ally arrives wounded, or the enemy begins escaping with something important. Tactical depth appears when the players must revise a plan that was sensible one round ago.

That produces much of the intricacy associated with more elaborate combat systems without requiring another layer of modifiers and subsystems.

Treat the tornado as a moving encounter with changing problems, not as one saving throw that decides everything. In 2024 5e, strong wind already gives a useful baseline: it hinders ranged weapon attacks, extinguishes unprotected flames, disperses fog, and can force flying creatures to land or fall. A tornado can escalate beyond that baseline without needing a full monster stat block.

Run it in short phases. First, telegraph the danger with falling debris, pressure changes, panicked animals, and visible movement in the storm. Then give the party a concrete objective: reach shelter, rescue trapped people, secure a wagon, cross exposed ground, or stop a ritual before the funnel arrives. Each round or scene, change the environment rather than merely increasing damage: collapsing roofs, blocked routes, airborne debris, separated allies, or a safe route becoming unsafe.

Use saving throws only when a character is actually exposed to a specific danger, and let good decisions remove or reduce those rolls. The encounter becomes memorable when the storm changes what the characters can do and forces choices under pressure, not when it simply deals automatic weather damage.

Treat the war as a changing environment around the characters, then give them specific objectives that matter inside it instead of resolving every soldier individually. The army creates scale; the characters create the playable scenes.

Alternate between wide and close views. Briefly describe the front moving, cavalry disappearing behind smoke, a defensive line buckling, or troops retreating through streets the party crossed earlier. Then cut immediately to something the characters can affect: hold a bridge during an evacuation, reach a commander before communications collapse, destroy a siege engine, recover a banner that is keeping a unit together, or decide which threatened position receives their help.

Keep changing the battlefield between objectives. Routes become blocked, wounded soldiers arrive from supposedly safe ground, visibility disappears, orders become obsolete, and friendly units move somewhere unexpected. These changes make the battle feel as though it continues when the characters are not looking at it.

Separate local success from the overall result. Saving one flank does not have to win the war, and losing an objective does not have to make the session meaningless. A failed mission might force a retreat, cost an ally, expose new information, or change the next objective. That lets the characters have visible impact while preserving the scale of a conflict larger than four adventurers.

Run the two fights as intercut parts of one larger scene rather than finishing one battle before returning to the other group. The main pacing problem is not making both combats last exactly the same number of rounds; it is preventing either side of the table from becoming an audience for too long.

Switch groups after meaningful beats: a character completes a turn, the battlefield changes, a new threat appears, or someone makes a consequential decision. You can keep separate initiatives if that is easier, but move back and forth frequently enough that both situations feel simultaneous.

Give each side an objective beyond reducing enemies to 0 hit points. The solo character might need to put a spirit to rest, hold a doorway, complete a rite, or survive until something changes. The other group can face a different task that affects the same larger crisis. Objectives let you tune difficulty without relying only on enemy damage.

For a solo fight, avoid swingy designs that can end on one unlucky round. Use fewer enemy actions, telegraph dangerous attacks, and include a way to retreat, bargain, interrupt the threat, or change the battlefield. If possible, let one group’s success alter the other fight so the split feels intentional rather than disconnected.