D&D 5E Older dragons don't seem to do much damage.

Against a small or medium-sized group dragon fear is very different. The dragon can use dragon fear and pick off its enemies during the one hour period.
I deliberately flew Arauthator over the middle of my group and set off his Frightful Presence; I wanted them to scatter in all directions, instead of protecting each other.
One PC - a Ranger/Rogue - got off a CRIT with an Arrow of Dragon Slaying, succumbed to Fright, and missed every other shot until Arauthator decided to depart (low HP); then the PC got the killing shot !
 

log in or register to remove this ad

NPC mook Archers can't have the Sharpshooter feat. That requires level 4. For that matter, they can't even have level 1. Levels are a PC conceit. So are Variant Humans.

If you're theorizing a unit of 100 Level 1 Variant Humans with Sharpshooter, you're basically theorizing a table of 100 players.
 

Dragons being buffed was a common 1e request. Dragon #50 was full of alternative ideas for making your dragon tougher. In an AD&D campaign I played in during 1982, (which included Arduin Grimoire rules) there was a red dragon with over 1000 hit points.

The huge, ancient red dragon in 1E AD&D has 11 HD, 88 hp, an AC of -1. To my knowledge
0 level archers would still need a natural 20 to hit it, but it was still vulnerable to them. More so than 5E where the disadvantage mechanic exists.
 

NPC mook Archers can't have the Sharpshooter feat. That requires level 4. For that matter, they can't even have level 1. Levels are a PC conceit. So are Variant Humans.

Is that like saying that Goblins can't have Cunning Action (Hide/Disengage) because they're not 2nd level Rogues, and hobgoblins can't have Sneak Attack for 2d6 because they're not 3rd level Rogues?

Besides, levels aren't a PC conceit. They're a character feature, and they work equally well for PCs and NPCs. Hence the distinction between "Player Characters" and "Non-Player Characters," which were historically mechanically identical except for who's in the driver's seat. 5E has cautiously introduced some optional rules for making PCs be special snowflakes (inspiration, which a DM can choose to award) but there's nothing unorthodox about having an NPC with class levels.

Having 100 0th or 1st level (Variant Human) Sharpshooters would be a bit much though. I wouldn't do that in-game unless I were trying to model a population based on the Balearic Island peoples during Roman times, of whom it was written, "And their training in the use of slings used to be such, from childhood up, that they would not so much as give bread to their children unless they first hit it with the sling." (I'm betting that's an exaggeration, but in D&D we're allowed to take exaggerated myths at face value.)
 

Is that like saying that Goblins can't have Cunning Action (Hide/Disengage) because they're not 2nd level Rogues, and hobgoblins can't have Sneak Attack for 2d6 because they're not 3rd level Rogues?
Yup. It's exactly like that. :) if a DM wants to assign a ability that works the same way as a feat or class feature to an NPC/monster, he certainly can. But the assumption that NPCs work the same way as PCs, and come with any PC abilities, isn't the recommended way to design NPCs. Adding abilities is a DM-fiat thing.

Besides, levels aren't a PC conceit. They're a character feature, and they work equally well for PCs and NPCs. Hence the distinction between "Player Characters" and "Non-Player Characters," which were historically mechanically identical except for who's in the driver's seat. 5E has cautiously introduced some optional rules for making PCs be special snowflakes (inspiration, which a DM can choose to award) but there's nothing unorthodox about having an NPC with class levels.

Having 100 0th or 1st level (Variant Human) Sharpshooters would be a bit much though. I wouldn't do that in-game unless I were trying to model a population based on the Balearic Island peoples during Roman times, of whom it was written, "And their training in the use of slings used to be such, from childhood up, that they would not so much as give bread to their children unless they first hit it with the sling." (I'm betting that's an exaggeration, but in D&D we're allowed to take exaggerated myths at face value.)
DMs aren't really supposed to use PC levels for NPCs at all. 5e isn't designed to have 0-level or 1st level NPCs. They're designed the same way monsters are. I mean, DMs can do what they want, and for something like a henchman probably even should create PC-NPCs. But it's not the way the system is designed to handle NPCs by default.

All of which makes theory-crafting based on it kind of pointless.
 

DMs aren't really supposed to use PC levels for NPCs at all. 5e isn't designed to have 0-level or 1st level NPCs. They're designed the same way monsters are. I mean, DMs can do what they want, and for something like a henchman probably even should create PC-NPCs. But it's not the way the system is designed to handle NPCs by default.

All of which makes theory-crafting based on it kind of pointless.

The DMG disagrees with you there. Designing NPCs using PHB rules is one of the two primary ways of designing NPCs in 5E--and it's the first one which was published.
 



Having an Arrow of Dragon Slaying does tend to shift the balance somewhat!
Yah, he holds the campaign record for Most Damage in One Blow - almost 100 HP (all those dice, and they rolled well for him). Arauthator had 500 total at the start of the evening.
I was doing a "dragon voice" and had already used "sucker punch to the gut" sound effects and description for the non-crit Arrow. I told him I couldn't voice what happened when the SECOND arrow hit, but something significant clearly had happened.
 

Remove ads

Top