The Problem of Hit-Points

The issue of hit-points, and exactly what it is that they represent in D&D, is something that has troubled me over the years.

Not that it's troubled me much, you understand — I certainly haven't ever lost any sleep over it.

Anyway, what are these "hit-points"? To what extent do they represent actual physical damage, and how much is luck, fatigue and so forth?

  • Clearly, they largely reflect a level-based increase in defensive skill, luck, the protection of the gods, or whatever. It's ludicrous to think that an experienced warrior would be able to absorb ten or twenty times as much physical damage as an inexperienced one. Granted, physical training and combat experience does bump up one's ability to soak up the smacking, but not to that sort of extent.
  • Clearly, the loss of a single hit-point must mean that the character (or critter) has taken some physical damage, however slight. Otherwise the venom/poison mechanisms wouldn't work, and would have to be extensively rejigged — and frankly, bugger that for a game of soldiers.
  • Clearly, they have little to do with fatigue. If they did reflect fatigue, a heavily armoured knight wielding a greatsword should take more hits per successful attack than an equally fit but unarmoured yokel with a knife. Also, if hit-points were some sort of fatigue mechanism, the character's fighting ability should decrease as hit-points are lost (i.e. as fatigue builds up). That isn't the case; a character fights as well at one hit-point as they do at full health (although they do gradually become easier to kill, I suppose).

I'm sure you get my point; I won't belabour it any further.

Anyway, the point of all this preamble is really just to introduce the method I intend to introduce for rationalizing hit-points and damage. Note that this method is hardly startling or original; I'm sure there are dozens of systems that do something like it.

THE METHOD:

Hit-points primarily represent luck and defensive ability. The loss of a hit-point does indicate some slight physical damage (so that venoms still work), but it is confined to largely irrelevant scratches and bruises. Apart from making it easier for the next blow to kill you, the loss of hit-points has no mechanical effect. Hit-points are easy to heal.

A character's actual physical resilience is represented by their Constitution, and actual physical damage is taken directly from CON. When a character reaches zero CON, they die. CON damage is hard to heal.

Such situations include:
  • When attacked by surprise in a back-stabbing situation — you'd get a saving throw to take the damage as normal hit-point damage instead.
  • If you are attacked when completely helpless (the old dagger-through-the-visor-of-the-paralyzed-knight trick)
  • When you have no hit-points left. This would be the most common situation; damage is taken point-for-point against CON. If you have 3hp left and take 6 points damage, you'd take 3 points of CON damage.
  • When you take falling damage — damage is determined normally at 1d6 per 10' fallen to a maximum of 20d6; if a die shows a 1 it does no CON damage, 2-5 does 1 point of CON damage, and a 6 does 2 CON damage. This system could also be used when immersed in lava, or doused with acid, bleeding from a Sword of Wounding, or whatever.
This list is not by any means exclusive.

With this method, high-CON characters do get a double-bite at the cherry since they not only get more hit-points, but can also take more below-zero hits without dying. Personally, I don't care about that. So having CON is good, so what?

This system still doesn't address the deleterious effects of fatigue, but meh, shrug. If it's relevant, it's a simple matter to apply a progressive penalty to all die rolls.

Mount Anthracite – finished (probably)

Photos may be clicked upon to embiggenate. Now I've finished flocking Mount Anthracite, and photographed it out in my rather overgro...