D&D 5E good rules for PCs vs army units?

Frankie1969

Adventurer
The party is 15th level, and it's time to put them up against a couple hundred soldiers in platoons. What's a good way to make this tactically interesting and take about an hour?

We had a previous battle using standard 5E combat with dozens of individual tokens and it was a tedious slog. I've read that the UA Mass Combat system works best for army vs army with PC support, but not for lopsided PCs vs army.
 

log in or register to remove this ad

dave2008

Legend
The party is 15th level, and it's time to put them up against a couple hundred soldiers in platoons. What's a good way to make this tactically interesting and take about an hour?

We had a previous battle using standard 5E combat with dozens of individual tokens and it was a tedious slog. I've read that the UA Mass Combat system works best for army vs army with PC support, but not for lopsided PCs vs army.

I would suggest using swarms. The enemy units are swarms. Something like what I did for a Vargouille Swarm: Vargouille Swarm

VarSwarm.JPG

I think this works well. You can design different units based on monsters or NPC stat blocks.
 

MNblockhead

A Title Much Cooler Than Anything on the Old Site
An hour‽

My best advice is to look into Matt Coleville's Warfare rules. These are heavily abstracted rules for large-scale battles. It is included in the Strongholds & Followers book but he made this section open content and you can get the open content Warfare rules here:

https://www.dropbox.com/s/l300e96pe8s9pvz/warfare.pdf?dl=0

One issue with these rules for you may be that "individuals don't matter."

If you truly want to have your player's handful of powerful PCs against an army, I would just use the "Handling Mobs" rules in the Dungeon Master's Guide (DMG 250).

Basically, you determine the d20 roll each group needs to hit each PC and there is a simple table that tells you how many hit each round.

The example in the books is eight orcs surround a fighter. The orc's attack bonus is +5 and the fighters AC is 19. The orcs need a 14 or higher to hit the fighter. So if 3 orcs mob the player their is one auto hit.

For PCs they attack as normal. Casters with AOE spells are going to really be important, unless you are giving the other characters access to anti-siege weapons.

For ranged attacks I have no problem saying, well, there are 100 archers with long bows. They have a +6 attack bonus. The fighter as an AC of 21, the cleric has an AC of 19, the Wizard with Mage Armor has an AC of 15, the rogue has an AC of 16. So the to-hit the archers need for each is 15, 13, 9, and 10. According to the chart at DMG 250 that means for every four attackers that hit the fighter, one will hit. 3 attackers for 1 to hit the cleric. 2 for 1 hit on the wizard or the rogue. I would have all the arches go on the same initiative.

I might have them focus fire on the wizard and cleric first to take them out before their AOE spells decimate them.

For melee, however, my players are going to cry foul. I would just go by the rule that (assuming the PCs are medium creatures), 8 creatures can fit in a 5-foot radius around another one.

This will mean that very weak fighters will not be able to scratch a highly armored character. E.g. a commoner would need a 19 to hit, meaning you need 10 commoners to make one hit. What I might rule, however, is that if you have a huge mob of pitchfork wielding commoners, you still get the auto hits as long as 10 or more are surrounding you. Think of it like getting a flanking advantage or morale boost. This allows for a swarm of weak enemies to overtake even the strongest PC if he just wades into the sea of attackers for a melee fight. If the player cries foul, ask them if they'd rather you roll 8 times and apply any crits. Most would accept the trade off of auto hits and a faster combat.
 

77IM

Explorer!!!
Supporter
Welllll... you could do something similar to the swarm rules, but for non-tiny creatures. I think I've seen these called "mob" rules in other games (maybe in 4E?). In a military context, I'd call this creature a "unit." Here's how I'd turn a creature into a unit in 5E:

Unit Template
A unit is a group of 16 medium or small creatures with identical statistics, which moves and fights together as a coordinated force.
Size: Increase the creature's size to Gargantuan.
Hit Points: Multiply the creature's hit dice and hit points by 8. For example, if the creature normally has 11 (2d8 + 2) hit points, a unit of them would have 88 (16d8 + 16) hit points.
Damage Vulnerability: Area effects.
Condition Immunity: Any effect that only targets or affects a single creature.
Unit Movement: The unit can move through any opening large enough for a medium-sized creature.
Unit Health: A unit that has less than half its hit points remaining can't regain lost hit points. When the unit is reduced to 0 hit points, it routs; its members scatter and flee. (If it's important, about half the members of the unit are alive and fleeing, and the rest are unconscious or dead.)
Attacks: Double the creature's normal number of attacks; when the unit has less than half its hit points remaining, don't double its attacks.
Damage: Quadruple the damage of the creature's attacks. For example, if the creature can normally attack with a longsword for 6 (1d8 + 2) damage, then a unit of such creatures would attack for 26 (4d8 + 8) damage.
Challenge: Increase by 4.​

Hmmm, that may be too complex, since I just pulled it out of my ass. But I think you get the idea. You could create stat blocks for such units ahead of the game, and then the party is only fighting about a dozen creatures instead of hundreds. A dozen creatures is still a lot, but should be few enough for you to manage, while still FEELING like a lot.
 

dave2008

Legend
An hour‽

My best advice is to look into Matt Coleville's Warfare rules. These are heavily abstracted rules for large-scale battles. It is included in the Strongholds & Followers book but he made this section open content and you can get the open content Warfare rules here:

https://www.dropbox.com/s/l300e96pe8s9pvz/warfare.pdf?dl=0

One issue with these rules for you may be that "individuals don't matter."

If you truly want to have your player's handful of powerful PCs against an army, I would just use the "Handling Mobs" rules in the Dungeon Master's Guide (DMG 250).

Basically, you determine the d20 roll each group needs to hit each PC and there is a simple table that tells you how many hit each round.

The example in the books is eight orcs surround a fighter. The orc's attack bonus is +5 and the fighters AC is 19. The orcs need a 14 or higher to hit the fighter. So if 3 orcs mob the player their is one auto hit.

For PCs they attack as normal. Casters with AOE spells are going to really be important, unless you are giving the other characters access to anti-siege weapons.

For ranged attacks I have no problem saying, well, there are 100 archers with long bows. They have a +6 attack bonus. The fighter as an AC of 21, the cleric has an AC of 19, the Wizard with Mage Armor has an AC of 15, the rogue has an AC of 16. So the to-hit the archers need for each is 15, 13, 9, and 10. According to the chart at DMG 250 that means for every four attackers that hit the fighter, one will hit. 3 attackers for 1 to hit the cleric. 2 for 1 hit on the wizard or the rogue. I would have all the arches go on the same initiative.

I might have them focus fire on the wizard and cleric first to take them out before their AOE spells decimate them.

For melee, however, my players are going to cry foul. I would just go by the rule that (assuming the PCs are medium creatures), 8 creatures can fit in a 5-foot radius around another one.

This will mean that very weak fighters will not be able to scratch a highly armored character. E.g. a commoner would need a 19 to hit, meaning you need 10 commoners to make one hit. What I might rule, however, is that if you have a huge mob of pitchfork wielding commoners, you still get the auto hits as long as 10 or more are surrounding you. Think of it like getting a flanking advantage or morale boost. This allows for a swarm of weak enemies to overtake even the strongest PC if he just wades into the sea of attackers for a melee fight. If the player cries foul, ask them if they'd rather you roll 8 times and apply any crits. Most would accept the trade off of auto hits and a faster combat.

Thank you for sharing - I was interested in the warfare rules and didn't realize they are free content. I also forgot about the MOB rules. However, that being said I am not sure either of those rules do what the OP asked. I think some version of swarm/unit rules would work the best.
 

dave2008

Legend
Welllll... you could do something similar to the swarm rules, but for non-tiny creatures. I think I've seen these called "mob" rules in other games (maybe in 4E?). In a military context, I'd call this creature a "unit." Here's how I'd turn a creature into a unit in 5E:

Unit Template
A unit is a group of 16 medium or small creatures with identical statistics, which moves and fights together as a coordinated force.
Size: Increase the creature's size to Gargantuan.
Hit Points: Multiply the creature's hit dice and hit points by 8. For example, if the creature normally has 11 (2d8 + 2) hit points, a unit of them would have 88 (16d8 + 16) hit points.
Damage Vulnerability: Area effects.
Condition Immunity: Any effect that only targets or affects a single creature.
Unit Movement: The unit can move through any opening large enough for a medium-sized creature.
Unit Health: A unit that has less than half its hit points remaining can't regain lost hit points. When the unit is reduced to 0 hit points, it routs; its members scatter and flee. (If it's important, about half the members of the unit are alive and fleeing, and the rest are unconscious or dead.)
Attacks: Double the creature's normal number of attacks; when the unit has less than half its hit points remaining, don't double its attacks.
Damage: Quadruple the damage of the creature's attacks. For example, if the creature can normally attack with a longsword for 6 (1d8 + 2) damage, then a unit of such creatures would attack for 26 (4d8 + 8) damage.
Challenge: Increase by 4.​

Hmmm, that may be too complex, since I just pulled it out of my ass. But I think you get the idea. You could create stat blocks for such units ahead of the game, and then the party is only fighting about a dozen creatures instead of hundreds. A dozen creatures is still a lot, but should be few enough for you to manage, while still FEELING like a lot.

That is the basic idea behind my swarm version. Though I agree that calling it a unit for an army works better. I have created demon "hordes" and devil "legions" with this swarm concept. They seem to work well. One thing I like about this concept is that at some point they break down into individual monsters / soldiers (which is a good time for them to run away) and the use of "legendary" actions simulates multiple initiatives without having to roll and track it several times.
 

Quickleaf

Legend
The party is 15th level, and it's time to put them up against a couple hundred soldiers in platoons. What's a good way to make this tactically interesting and take about an hour?

Tactical complexity is at odds with brevity. You can sacrifice one for the other, but you can't have both.

The more tactical choices presented to players/DMs, the longer rounds take. That's why you have very abstracted mass combat rules in BD&D – the emphasis there was not on tactics but on troop composition, the objective being arriving at a resolution reasonably quickly.

We had a previous battle using standard 5E combat with dozens of individual tokens and it was a tedious slog. I've read that the UA Mass Combat system works best for army vs army with PC support, but not for lopsided PCs vs army.

I ran a roughly 3-hour long fight with the PCs (and aarakocra allies) facing off against 21 gargoyles. The PCs had very limited access to magic weapons. It could easily have been a slog.

However, despite the length, it turned out to be one of the most gripping intense sessions we've had. One player commented that he could envision the whole scene taking place like a Lord of the Rings film or fantasy anime.

I accomplished this with a couple steps:
  1. I was well-organized with all the stats/notes/abbreviated tactics I'd need on just 2-3 printed pages.
  2. I also took specific notes on potential random actions for the gargoyles. See below.
  3. I framed the scene vividly. Aarakocra summoning an air elemental while their leader performed a ritual. At night, one of the PCs noticed the moonlight coming through clouds glinting off stony form of many gargoyles on the wing. A brief volley of longbows and other long-range attacks, and then the battle as rain and winds pelted the cliffside aarakocra settlement the PCs were defending. Many choices of the PCs came from how I framed this scene.
  4. I created a table of developments/twists that I rolled on every even round. I've pasted this below. Doing this kept the fight fresh & helped up the tension.
  5. Lastly, I incorporated Dungeon World GM moves as a table of "complications" – I rolled when players failed key checks, when players dawdled, when players tried to “brute force” a challenge (rather than engaging with the narrative & playing smart), or when play presented a golden opportunity. This also helped keep the fight fresh and make failure interesting.

GARGOYLE RANDOM ACTIONS (d6)
  1. Attack & terrorize the weak.
  2. (aarakocra young, Na, unconscious characters, pets/familiars).
  3. Desecrate the Cleansing Chamber.
  4. Disrupt the air elemental summoning of the monks.
  5. Grapple a dangerous foe in pairs, then drop that foe off the cliffs.
  6. Hunt down Mwaxanaré to abduct her.
  7. Raid Asharra’s library or the scavenger’s market, stealing valuables.

DEVELOPMENTS (d8 on even rounds)
  1. Na is missing! Is he trapped? Hiding? Taken by gargoyles? Trying to help?
  2. Mwaxanaré – not heeding Asharra’s warnings – goes to use a golden egg.
  3. Plummeting dead gargoyle breaks a 15-foot stretch of walkway.
  4. The air elemental is destroyed! Any gargoyles it was facing enter Kir Sabal.
  5. Wounded aarakocra is falling to death unless PC uses reaction to intervene.
  6. Building crumbles from magic missiles, 4d6 bludgeoning, dust, and cover.
  7. A RANDOM NPC/PC (d12) is overwhelmed and needs help!
  8. An aarakocra youngling brings arrows or a healing potion in the nick of time, but needs a window to escape to safety.

Regardless of the particular mechanics you settle on, I'd consider incorporating aspects of my approach.
 

Stalker0

Legend
For quick and easy, I think mobs work best. If you want casters do them in smaller units (like 4-5). Keep in mind that in 5e mass units beat strong units. Armies are very scary with 5e mechanics.


If you want to go "nuts", what I did for my last 20th level super adventure, is I put it all in excel. At one point I literally had the party face 400 archers. I just put every archer as a random roll on the excel sheet, put in the damage. And then I would assign each party (whose AC I knew...also factored in advantage and disadvantage as pertinent) a certain number of attacks. And the sheet would tell me how much damage they took. The nice thing about that was it was "true damage", crits, misses, random damage rolls, the whole shebang. And of course I reduce the archers as damage was applied.

I wouldn't recommend that for normal fare, but if you are trying to make it special that is one option. And once you make the sheet you can recycle it for other entries and the like.


I will also say that I did a similar thing to what QuickLeaf mentioned. I had a random roll every round for some special traps in the area that would go off, and that keeps it fresh. I think that's very important to keep long fights interesting.
 

aco175

Legend
I have run large encounters where the little people only need one hit, especially if the PCs are level 15. Fireball can take out groups at a time and make the casters feel powerful. The fighter slogs around killing 2-3 little monsters each round and that starts to become boring. Introduce several big monsters where they are captains of the littles. I had the PCs focusing on the giant and not on the goblins that they were getting shot each round once or twice so eventually the PCs needed to pull back.

You can speed up slogs by having the players roll to hits on themselves or other PCs. I find that the players like to attack each other when they can say that it is the monster actually attacking.
 

When I run large scale battles, I divide the battlefield into sections. The players only one part of the battle. I roll, or determine ahead of time the outcome of the other sections of the battle.

Example. You are defending a city wall and there are 5 weak points. 4 to start but a 5th will open up because of sappers. I roll to see how the defenders do at each weak point and determine if they hold and, if not, how long it will be before the weak section falls.

Then I run an encounter for the PCs with piles of people fighting all around as a backdrop. I’ll have lots of NPCs h loping or hindering. Depending how they fare, they might fail to hold a section and fall back to another point. Or they might succeed on routing an enemy then leave it to some NPCs to defend and they’ll go help another section of the city. The sappers might be a set piece or complication.

In short, I run it as a series of the encounters with the here success or failure effects the entire battle.
 

Remove ads

Top