Part of the satisfying nature of it is exactly in how rarely it gets invoked, like, two or three times per gaming session at most. It definitely throws in just the right amount of unexpected "spice" detail that makes combat exciting, unpredictable, and truly dangerous (without generally encumbering the process or the pacing). It throws a very nice curve ball into the standard d20-and-damage combat sequence, yet it's still an objective mechanic (not just DM fiat). And we have yet to see the exact same "special" result twice in the time that I've been using these tables. One of the things I do is, even after a 1 or 20 are indicated, grant the victim a saving throw to avoid going to the tables -- this nicely avoids oddities like high-level fighters constantly fumbling their sword, makes powerful monsters or established PCs difficult to take down by this technique, etc.
I haven't presented the tables here in the past because they're simply straight out of an old Dragon Magazine article -- a submission by the otherwise unfamiliar name of Carl Parlagreco, "Good Hits & Bad Misses", in Dragon #39 (July, 1980). To my knowledge, this is the only classic Dragon article dealing with the issue of critical hits; I think it was a short time after this was published that Gygax wrote one of his screeds, especially pointing out critical hits as a corruption of core D&D play. But I've found them to be extremely satisfying in my OD&D games. (Note that I almost totally ignore the text rules, but use the tables as written.)
Note how nicely this is laid out, from the era when meaty Dragon articles might only take up 2 pages as shown here (I print this out on one sheet of paper for my DM screen). It even has a thoughtful space left for "Notes" for your own refinements to the system. Here's what I have written in mine:
- On natural "1" or "20", target saves vs. stone (level + 2) or consult appropriate table.
- Fumbles: ignore indicated Dex checks.
- Liberal interpretations necessary: negate/change unreasonable results.
- Delayed death results negated by application of 3 cure light wounds.
- Undead immune to effects except head crushing/decapitation.
Edit 1: Also, consider making the victim roll the d% dice to determine the final critical-hit effect. Holy god, the look of horror on the player's face when they have to do that is unparalleled.
Edit 2: Get a PDF copy extract of these tables here.
The saving throw here is brilliant. I much prefer it to the 3E solution of a confirmation roll.
ReplyDeleteThanks for this post Daniel, I've been meaning to take a closer look at that article for years. I agree with Brendan, the saving throw is a nice touch. I can see now that these tables are much more suited to my game than others I have seen.
ReplyDeleteThanks for the compliments -- I was very pleased with the effect of the saving throw myself, taking confirmation away from the attacker, and making it a function of the proficiency of the defender has worked out very well for me.
ReplyDeleteThis is our DM's favorite critical hit system, although the chances of a critical hit/bad miss have been tweaked up/down based on PC level. tacojohn has brought low many a mighty PC using these charts ;)
ReplyDeleteAllan.
Perhaps I'm mis-remembering, but I thought you used a save vs. death, not paralysis.
ReplyDeleteI'll have to look mine up, but I have that article in a Dragon Mag or maybe annual that was 3 pages long & much more detailed.
ReplyDeleteNow I'll spend the better part of the next hour digging through magazine, lmao
thanks for this post!
Paul -- I bet you're thinking of my zero-hit-point rule, where you do save vs. death or expire.
ReplyDeleteDra8er -- I'd be very interested to see a revised version of that article!
Yup! That must be it.
ReplyDeleteSweet, thanks for posting. Definitely horking this for my own campaigns.
ReplyDelete^ Thank you for suggesting it, actually!
ReplyDeleteI. Can't. Read. It. In any format, its too small!
ReplyDeleteThat's a good point; see "Edit 2" at the bottom of the post for a link to a PDF version. Zoom to your heart's content! Thanks for the observation.
DeleteI prefer to maintain the abstract nature of combat in D&D to tables like these (and I've used them in the past - I remember when that article came out and we loved it!).
ReplyDeleteIn 5e I use the Exhaustion Track instead. Mine is a bit modified:
1: -12 on all ability checks, attacks and saves; can’t take bonus actions
2: Speed halved; can’t take reactions
3: Hit point maximum halved
4: Incapacitated
5: Stunned
6: Unconscious, dying, or other.
Recovery is using the death save mechanic, except for injuries you get one save after a night's sleep. You need at least 7th level healing magic to heal an injury.
Injuries can come from a number of things (like falling), but in combat a Critical Hit forces you to make a weapon damage check (you hit them hard), their armor might be damaged too, it does maximum damage, and the target is injured if they fail their Constitution saving throw.
Critical misses provoke an opportunity attack, or if using a bow the bow or string might break.
Delta, when the chart says things like "limb removed", is the PC effectively maimed/amputated? How does he recover from such a wound? Or is it really badly hurt and unusable until healed? A character who has lost an arm forever is a character to retire.
ReplyDeleteYes, that's pretty clearly the intent. Note the last text paragraph before the tables; in those cases the character is immediately "likely to bleed to death" -- require system shock or immediate unconsciousness, take 1-3 damage/round until bound.
DeleteI assume that _regeneration_ magic would fix those conditions (which isn't immediately available in my non-clerics campaign). I'll confess that I've gotten less thrilled with those over time. At the moment I waive a lot of the upper-body effects at the expense of a character's shield, if they have one.
On the other hand, my friend Paul had a long campaign with PCs taking disfiguring injuries like those when they hit 0 hit points, and he felt it provided a lot of unique character and motivations as a result.
Delete