Running Large Battles in D&D 5e: Objectives and Scale
A battlefield can contain a thousand soldiers while your table resolves a dozen meaningful turns. The useful preparation is deciding what the characters can change and how their local success affects the wider battle.
This guide uses 2014 D&D 5e for character-scale combat. The battle clock and bridge scenario are original DM procedures. They do not turn groups of soldiers into official swarm creatures or introduce a universal mass-combat subsystem.
Quick answer: resolve missions inside the battle
Define what the armies want, what happens without the party, and two or three objectives the party can affect. Run those objectives using ordinary combat, exploration, and social rules. Describe distant fighting as context unless the group deliberately chooses an army-command game.
A breach, a captured signal tower, or an evacuated hospital can change the battle without requiring an attack roll for every soldier. Make that connection explicit before the players commit.
Choose the scale before rolling initiative
| Scale | Use it for | Resolution |
|---|---|---|
| Background battle | A war surrounding the current adventure | Describe positions and consequences |
| Tactical mission | Defending a gate, breaking a siege engine, rescuing someone | Normal character-scale encounters |
| Strategic command | Deciding where reserves go and which position to abandon | A clearly explained campaign procedure or chosen published system |
| Full unit combat | Players want to command armies directly | One complete, identified mass-combat ruleset |
Do not slide between these scales without explanation. A unit represented by one token for convenience is not necessarily one creature for spell targeting, damage, or conditions.
There is no standard rule that a unit always contains twenty or fifty soldiers, has five times a guard’s hit points, or obeys any character’s bonus-action command within 60 feet. Such mechanics need a named source or a complete homebrew procedure.
Before the session: prepare the battle in one page
| Prepare | Example |
|---|---|
| Attacker’s objective | Capture the river crossing before the defenders evacuate |
| Defender’s objective | Move civilians and supplies across, then raise the bridge |
| Starting situation | Main road contested; river landing still secure |
| Likely result without intervention | Defenders withdraw but lose the supply wagons |
| Party’s opportunities | Hold the winch, disable a siege engine, or recover the signal flags |
| Information | A captain explains which position needs help and why |
| Deadline | The next assault reaches the crossing in four combat rounds |
| Withdrawal | North-bank stairs lead away from the bridge |
| Consequences | Record people saved, supplies retained, and positions lost separately |
Decide which facts are uncertain. The captain may not know the enemy reserve’s exact strength, but should be able to explain the current orders and visible threats. A meaningful choice requires usable information, not perfect intelligence.
Optional battle clock: six ten-minute periods
Use this homebrew framework when several missions happen during one battle and time matters. One battle period is ten minutes, including movement, organizing help, and a local task. Tell the players that the army can hold its starting position for six periods: one hour.
At the start of each period:
- Describe what changed on the visible fronts.
- Offer the current opportunities and their known time costs.
- Let the party choose a mission, reposition, or another action.
- Resolve the local scene at the scale it needs.
- Advance time once and apply the agreed strategic consequence.
A typical short tactical mission plus getting into position occupies one period. If the party takes longer, count the actual additional time. During combat, use normal six-second rounds; do not also tick ten minutes every round. Explain this abstraction before play.
A one-hour short rest normally consumes all six periods if the party begins it at the start of the clock. That is a time tradeoff, not permission to interrupt every rest with an invented attack.
Attach each objective to a particular result
| Mission | Success changes | Failure changes |
|---|---|---|
| Signal tower | Reserves receive the correct withdrawal route | They retreat along a longer road |
| Siege platform | The next breach assault loses its artillery support | The engine remains available |
| Hospital escort | Wounded defenders reach the river landing | Some must be sheltered in the old shrine |
| Winch defense | Supply wagons cross before the bridge rises | Wagons are abandoned or delayed |
Set a plausible combined outcome. For example, the army completes its withdrawal if the landing remains secure; saving the hospital and wagons determines what resources it retains. Do not secretly make every task mandatory while presenting them as alternatives.
Build manageable local encounters
Choose the creatures who can actually participate in the scene. Use the encounter balancing guide for those opponents, then account for terrain, depleted resources, allied help, and time spent on the objective.
A hundred distant enemies are not a hundred active attackers. Conversely, enemies close enough to join the fight soon are not harmless scenery. Write down their distance, route, and arrival trigger.
Use a small number of distinct roles. A few enemies trying to destroy a winch create clearer decisions than several interchangeable squads all taking low-impact turns. If you want a focused major opponent, the boss-fight guide covers staged pressure on a smaller battlefield.
Keep identical creatures organized
The 2014 initiative rules allow the DM to roll once for a group of identical creatures. Track their individual positions, hit points, and actions even when they share initiative.
For twenty off-screen soldiers, narrate the result of the larger plan or use your chosen mass-combat procedure. Do not give a single composite token a huge damage pool and then assume ordinary encounter math still describes it.
Worked mission: hold the bridge winch
Party: four 3rd-level characters. Opposition: three , each worth 100 XP. Task: raise a drawbridge after the last supply cart crosses. The army is fighting elsewhere; no other combatants are active in this scene.
The enemies’ base XP is 300, and the three-monster multiplier gives 600 adjusted XP. For this party, Medium begins at 600 and Hard at 900, so the creature-only estimate is Medium. Spending actions on the winch and defending the mechanism can make the scene harder than that label suggests.
Layout and starting positions
A 20-foot-wide road runs north–south across the bridge. The winch stands on the north bank, behind a waist-high stone barrier that can provide half cover when it obstructs an attack. Two operating stations sit beside the same mechanism, five feet apart.
The party starts within 10 feet of the stations. The orcs approach from the north road, 40 feet from the winch, where the party can see them. The north-bank stairs, 20 feet east of the winch, provide an exit to the river path. Describe these features before initiative.
Objective rules for this example
- The last cart clears the bridge at the end of round 1. Before that, turning the mechanism would endanger the cart, so no useful winch progress can be made.
- Starting in round 2, a creature at either station can spend an action to turn its crank. Each station can contribute once per round; extra attacks do not create extra crank actions.
- The winch needs six total crank actions. With both stations operating, rounds 2, 3, and 4 are sufficient.
- At the end of round 4, the next enemy formation reaches the far approach. If the bridge is raised, it cannot cross. Otherwise, the commander orders the party to withdraw by the river stairs; the remaining wagons cannot be saved through this route.
- The mechanism is a single object with AC 19 and 18 hit points for this scenario. At 0 hit points it jams and cannot accumulate further progress until repaired. Those are assigned object statistics, not a universal winch stat block.
The deadline and progress procedure are homebrew encounter details. Tell the players how the mechanism works; do not require a roll to learn the objective’s essential action cost.
Enemy behavior
The orcs want the bridge usable. They advance using their printed movement and attacks, prioritizing someone operating a crank or the mechanism itself if they can reach it. They have no extra attack for issuing an order, and do not teleport through a defender blocking their route.
If two orcs fall, the survivor attempts to withdraw rather than continue alone. That morale decision is part of this scene’s preparation, not an added orc trait.
Run the choice, then honor the result
The party has a round to position before the cart clears. Afterward, two characters can operate the winch while two defend, or they can prioritize defeating the orcs and accept a narrower timetable. Effects that stop the attackers or protect an operator can be decisive.
If the party eliminates the threat early, finish the remaining winch work without rolling empty combat turns. If the mechanism jams, make the north-bank escape clear. The local failure costs supplies; it need not erase the party’s other achievements in the battle.
Scale before play
For a gentler version, use two orcs: 200 × 1.5 = 300 adjusted XP, Easy for this party. Keep the objective and explain its timing.
For a harder version, two additional orcs may arrive through a prepared reinforcement route. Reviewing all five together gives 500 × 2 = 1,000 adjusted XP, Hard before objective pressure. Establish the signal and travel time in advance, and cancel those reinforcements if the party genuinely prevents the trigger.
Do not automatically multiply enemy numbers because there are more soldiers elsewhere on the battlefield.
Orders, allies, and siege engines
A character can shout ordinary information, but that does not establish a universal bonus-action power to command every allied unit. Decide who has authority, who can hear, and what the allies can realistically accomplish. A distant commander may need a runner or a signal.
If allied creatures join a tactical encounter, use their actual stat blocks and include their contribution in your difficulty review. Giving an NPC to a player to operate can reduce DM workload; agree on its behavior and limits first.
For siege equipment, use the chosen engine’s printed crew actions, range, attack, and damage. A scheduled bombardment at a fixed initiative count is a custom environmental event, not automatically how every siege weapon fires. Telegraph its target area and define whether the party can interrupt it.
If the group wants unit combat
Choose a complete system and identify its status. Wizards’ 2017 Unearthed Arcana Mass Combat, for example, is explicitly playtest material rather than a finished core rule. Do not mix its unit abstractions with improvised hit-point multipliers and present the result as standard 5e.
Before the battle, settle unit size, attacks, morale, movement, command, casualties, and interaction with character spells. A simple procedure that answers those questions is more usable than incomplete statistics dressed as a new creature type.
Using the 2024 rules
The mission-first approach works with revised character rules, but use the exact creatures and encounter budgets you selected. The 2024 combat-building method uses raw monster XP against its budgets, without the 2014 count multiplier. The numerical labels above belong to the 2014 example.
If using revised monsters, check their names, attacks, and other traits. Do not import a legacy orc’s statistics merely because a revised creature fills a similar battlefield role.
At the table: a battle-status note
Track five items: elapsed time, current party objective, active opponents, known reinforcements, and the wider consequence already earned. Keep distant army narration brief enough that players retain the information needed for their next decision.
After the battle, describe both the strategic outcome and the specific people or resources the characters saved. Those concrete changes make the battle feel large while keeping their actions understandable.