Hp is as old as roleplaying, along with combat rounds, attacks per round, and plenty of other things. Hp can encompass many things, including luck. Many people point to the name: a hit is a hit, and hp can be restored with spells such as cure wounds, which they believe would make no sense for hp representing luck in battle. They therefore reject the idea that hp is an abstraction. Reality is more complicated. It matters whether hp includes some of the damage-reducing effects of parrying, battlefield luck, and the like that are not modeled elsewhere, or whether we also include effects that avoid damage entirely and many other things. Both involve abstraction and simplification; only in the first case do we understand why healing hp damage is logical.  

What Does the Player's Handbook Say?

Some things should not need spelling out. One is the provision in the Player's Handbook: until you lose half your hp, you look roughly uninjured; below that, bruises and cuts appear. The wound that reduces you to 0 hp is a direct hit and causes, for example, a bleeding wound, significant trauma, and so on. In other words, the Player's Handbook specifies exactly when there is a clearly visible injury. Of course, that does not stop a fan troll from declaring a player stupid because their GM described it that way. It is just very strange that people arguing for D&D 5E, when faced with an injury described in such a situation, call everyone who holds this position an idiot—apparently including the system's own creators. Never mind.

But suppose you have read this. Ask yourself: if a fighter whose maximum would be 13 hp still looks uninjured at 7 hp, do you heal them after the fight? How would it affect the party's chances in the next fight if most of them started at 50% of maximum hp plus 1, instead of full hp? Under the rules, how could someone realize the fighter needs healing because nearly half their hp is missing, if they still look uninjured and we are not metagaming, bringing outside information into play, or aware of what hp is or how much they have? Abstraction has always been part of D&D, but most earlier editions lacked guidance like that on page 197 of the fifth-edition PHB. So while in earlier hp systems it was a reasonable GM decision to say the abstraction incorporated factors reducing the severity of an injury, the situation is no longer so clear in fifth edition.

Roleplaying 101: In Character and Out of Character

Precisely because hp is complex, however, there is a small problem to solve. Depending on how the abstraction is used, at least six situations can arise. These could be subdivided further, but even the scenarios in this table show that certain states need thought and are best avoided in a simple hp system:

Table 1: HP and Injuries
  No physical injury Physical injury present
No HP loss 1. The situation is clear: the character is naturally uninjured. Every system has this; great, “maximum hp.” 2. Two anomalies arise: how can the character be at full capacity despite the injury? And an in-character decision would prompt healing, but that wastes a spell.
HP lost, but recovers on its own 3. No problem: rest is needed, a roleplaying solution. Provided not every loss of hp is handled this way and serious injuries need healing. It helps if the character can feel it... 4. Easy to describe if the injury is a tiny, unnoticed scratch that heals quickly. Treating serious injuries this way would be a problem.
HP lost, healing needed 5. How would a bandage heal lost battlefield luck? Without an apparent reason, why cast cure light wounds? Forced metagaming? 6. Generally relatively easy to describe at lower levels. At high levels, a more experienced GM handles it.

Four of the six cases in the table work well: the in-character and out-of-character situations present similar pictures and lead to similar decisions. Two are problematic, because we see entirely different things in character and out. But two of the good solutions depend on the system handling injuries that easily heal by themselves well. Even where temporary hp loss existed, it was often tied to weapons, such as fists, or combat options, rather than generally improving how the hp system worked. If we do not distinguish this damage and give it a separate system, the healing rate will not necessarily be right. Many things therefore point toward treating hp uniformly, which has many advantages. But in that case, only situations 1, 2, 5, and 6 remain available. 

The real trouble lies in the two italicized situations.

Clearly, both share the premise that “hp is not meat points,” while we nevertheless imagine the situation. The in-character information from the imagined world is entirely different from the out-of-character information. It is also a fact that the PHB guidance above plays a part in both cases.

A Metagaming Problem

Obviously, for someone who wants any attention paid to roleplaying, it is not a good solution for the PC to know through metagaming that, despite there being no injury, bandages will restore battlefield luck and relieve fatigue. So when people open with a sneering “not meat points,”  we immediately need to ask: have they ever reached the end of a fight with an uninjured person missing plenty of hp, and what did the player do, and why? If not, what is all the big talk for? If so, why is there no solution behind their arrogant pronouncement?

Let us put it this way: if the character appeared uninjured, then chances are either metagaming occurred or the character's condition was never described and the imagined scene was missing. Fine; you can play that way. The problem is that if we describe the character as uninjured and they therefore do not heal, the consequences can be nasty: roleplaying leaves you short of hp, so the system effectively punishes roleplaying. Calling that a good roleplaying system would be strange. The “hp is not meat points” jibes demonstrate a total failure to understand the problem. Can a DM or player who has never ended a fight with a character in such a condition, raising the question of why healing would happen, really be experienced? Do they know the system? 

At higher experience levels, it is easy to say that if we do not lose half our hp in one battle, hopefully the next will not be a problem either. The difficulty is primarily at lower levels. If a fighter has 7 of their 13 hp left and we describe them as nearly uninjured according to the guidance, there is no guarantee that the expected hit in the next fight will deal “only” 6 hp. If the outcome begins with unconsciousness, Second Wind will not work while unconscious, and the party's chances fall considerably. Alternating minor skirmishes with challenging fights can likewise have fatal consequences at higher levels. With an abstraction that reduced injury severity, the character had a reason to heal, so these problems did not necessarily arise. 

Although it is not appropriate to retell stories from a closed group with names attached, I found it odd that a group administrator was surprised a former moderator was not as good a roleplayer as he claimed, or as his many years of experience suggested. If the situation above never occurs over decades of D&D and AD&D—if hp has never been lost while the descriptions still leave the character uninjured—there are three possible reasons. Either you always described a wound and the “hp is not meat points” argument is bogus; or you ran very few games and avoided it; or descriptions and the imagined scene somehow fell away, leaving bare hp numbers. But no imagined scene and little roleplaying. 

If that suspicion arises after decades, what does the surprised administrator expect? Passing judgment on who is good or bad without thinking through the issue is precisely the kind of situation that makes “former moderator” unsurprising. But part of the story is that this person obtained the moderator position, and exhibited not some exceptional problem but familiar behavior he considered acceptable after seeing so many others do it. Surely it cannot be stupid if so many people behave that way... Repetition can make him believe it is acceptable, and this very tendency to throw judgments around instead of arguments may have led to losing the moderator position too.

Is Metagaming a Problem?

Obviously, the bloodthirsty kindergarten crowd needs none of this, especially if they choose a game precisely because it expects neither description nor thought. And in arguments it becomes clear that they learned rudeness rather than thinking, and that the greatest achievement of their conflict-ridden little lives is beating random boss #181 on Sunday, despite it not fitting the setting at all. Yeah, roll that d20. The trouble is that no edition of D&D began with the premise of serving the stupidest powergaming brats and trolls and nobody else.

There is, however, a very important underlying assumption in D&D: characters do not have PC written on their foreheads, and the world does not contain signposts reading The DM's Adventure > . But when you sit down at a club to play with strangers, or quickly find a group on Roll20 or Fantasy Grounds, you will not examine whom your character would adventure with or what kind of adventure they would want. Nor are most purchased adventures likely to have been tailored to your character.

Most players accept a reasonable degree of metagaming in pursuit of various important goals. Once we play out the characters' motivations, have a strong party concept, depict their lives outside adventures, and naturally include many other details, the picture of play changes. Many editions therefore contained quite a few optional rules and tried to accommodate games in which much less metagaming was acceptable and much more happened in character.

Old and New Anomalies

A sensible GM therefore recognizes that situation 5 is definitely an anomaly. The DM can then describe the hp loss in a way that places it in situation 3, 4, or 6. If I have described glancing blows and minor damage, and mentioned adrenaline, I also remember that after a car crash an ambulance takes in even someone who was only slightly pressed by their seat belt, and they get an ultrasound, an X-ray, whatever is needed: an injury you cannot see or notice is still possible. Alongside magical healing, abilities and skills suitable for diagnosis and examining characters become meaningful. And you can bring equipment for that purpose. In other words, there are ways to reduce the problems arising from apparent lack of injury, although they are rarely used.

Treating exhaustion, overexertion, and many other things is possible too, so even hp loss without genuine injury can be described in a way that justifies healing, which is good. That leaves option 6: we describe an injury, condition, or something else that warrants healing. This has been true of every D&D edition so far. It is easy to say that any ability restoring hp without healing an injury would then take us to situation 2, another anomaly. But many editions of D&D and AD&D had no such ability. 

The solution is to avoid such abilities. In fifth edition, however, this is not optional: it is a mandatory fighter class ability. We can try to explain why the character is at full capacity despite a visible injury. The problem is that anything superficial enough to make “it does not matter that it is there” the natural response does not justify healing. Anything that does justify healing and avoids the “why are you healing?” metagaming problem remains serious and still warrants healing even once there is no hp loss behind it. As I said, take your pick: either the PHB's authors are idiots, or there are hp losses for which they themselves explicitly tell you to describe an injury. 

This leads to casting a spell for zero mechanical benefit in a system where managing such resources is fundamental, balance is a goal, and even official campaigns warn of the possibility of a TPK, a total party kill. Drawing resources out this way is bad, especially when they are not replenishing spells but, say, consumed potions. Here it is not players' or characters' mistakes, or an inherently dangerous situation, but features of the system that lead to character deaths or TPKs damaging the experience. Checkmate. 

D&D 5E's Plan B

The system does have an optional rule to handle this. A hell of a lot of fans do not use it, though, because why grant individual advantages...? That rule is Inspiration. Since the character was roleplayed at a mechanical disadvantage, inspiration, which rewards good roleplaying, is a natural reward, provided the DM does not shy away from individual rewards. Otherwise there is a bit of a bug here. Assuming there really was roleplaying, and we are imagining the situation rather than chess pieces on a battle mat. Part of that situation is whether the character has a wound, independently of hp lost or regained.

Interestingly, once this topic comes up, people behind the “D&D 5E is great exactly as it is” arguments immediately reveal that they play it differently. They dislike individual rewards, do not use the system to correct anomalies, and therefore have no idea, even after years of playing and GMing, what this element does to balance or how it devalues other mechanics granting advantage. What they play already differs significantly from D&D's official rules, and they do not address describing and imagining situations or roleplaying. Yet on that basis they “know” how good D&D would be for roleplaying without these changes. And because they have other players, received opinion, sheer volume, and no need to justify calling people idiots, they are happy with it. Others may be happier avoiding them along with D&D 5E. 

The main problem is that if their descriptions of hp injuries do not follow the PHB, this rule is different too, they do not check what the system says about related diagnostic checks, and they play almost everything differently from the PHB, are they still playing D&D or some homemade patchwork system? Is their experience relevant to the D&D in the books? After all the talk of not needing to check, of things not working that way at their table, of being able to rewrite everything, they are discussing a very different system...

How Can Hp Incorporate So Much?

At its best, the hp issue is simple. A high-level fighter can withstand a hell of a lot of hp damage because, thanks to their combat skill, 10 hp of damage represents progressively smaller and fewer wounds. Hp includes battlefield luck, defense, and the fighter's skill. This still works if we do not want to describe damage that affects only luck and so on, to avoid metagaming when healing happens anyway. Monsters can still lose hp without suffering wounds. But everything included in hp reduces the size of the wound represented by x hp of damage. When all these things were folded into hp, this was probably the intended direction, rather than needing bandages to restore battlefield luck. 

In other words, maximum hp incorporates not only the ability to withstand injury, but any ability that reduces the injuries expected in particular situations. Everything that reduces incoming damage in Storyteller or Shadowrun, for example. And yes, in Shadowrun's third edition that includes not only Body but the Combat Pool, and even using the Karma Pool representing luck. Instead of rolling to reduce damage, we multiply the available hp by the expected degree of reduction, effectively stretching out this condition track. Lo and behold, it works perfectly, without little Peter having to explain to little Steve that his combat skill or luck has taken a blow and decreased, which is why he lost hp. 

For a first-level fighter with 12 hp, losing 9 hp represents a fairly serious wound; for a fighter with 120 hp, the same loss is almost a scratch. Great. But taking the same time and effort to heal an almost-scratch and a serious wound, whether through magic or bandaging, is not so great. For spells, we can say the fighter involuntarily resists the spell more, which is also why they have more hp against spells. Fine, logical, I buy it. But the rate of mundane healing is a problem.

And showing no sign of injury above half maximum hp does not necessarily mean a closer examination would find nothing to heal...

An Often Invisible Problem

Sometimes I describe strains, discomfort, and other things, since they too represent hp loss without a visible wound. The basic aim, however, is that when there may be a reason to heal, at least one character feels or sees it, keeping in-character and out-of-character information aligned, because otherwise problems can arise. I have good reason to slow magical healing: if every perceived injury and discomfort disappears but hp still needs restoring, the obvious question is why bandages help replenish battlefield luck after the wounds have healed through magic, and how the character would know to apply them. Besides, if they feel nothing wrong, why would they not enter combat at half hp? A fighter could even brush off an examination, saying they are no little girl, need no checking, and are fine.

To have the experience above, it is enough merely to watch one game where the GM properly describes situations and the character's condition. Think about it for even a moment, and the question of why the character heals more slowly immediately appears. If there is no described damage, no mundane healing, and no such question, you will not see the problem either. Nor will you see that you described the injury because of the PHB's explicit guidance, that it is visible, that Second Wind would not remove it, and that a healing potion is therefore wasted. If you do not describe situations, there is no roleplaying and no problem. As a board game enriched with RPG elements, the system works perfectly.  

Why Is the Hp System Good?

The brilliance of the hp system lies in simplification: a genuinely simple, minimalist combat system has few steps and few facts to consider. There are few variables. It includes wounds, momentary discomfort, tactical position, and everything else so that we need not track many things. Agatha Christie's mysteries also taught us that when we receive too much information, our brains start selecting. We cannot attend to everything or distinguish reliable information from questionable information in every detail, so things in the story surprise us that should not. The imagined situation, including the character, the system, and visual information independent of that imagined situation all compete for our attention and working memory. 

There is the imagined battle described by the GM, and the series of facts being recorded and weighed. But there is a battle mat in front of you too. The described combat would be cinematic, slightly chaotic, full of movement and simultaneous events. The battle mat is much more static. What you should imagine therefore differs from what you see, but mechanical modifiers encourage you to rely on and use the visible situation. Your mind will preferentially discard the roleplaying, the imagined situation, and the more such modifiers there are, the more prominently you use the battle mat, line of sight, and other elements, the more you will focus on that. As it and the system squeeze more information about the imagined scene out of your mind, roleplaying recedes and we start getting a board game focused on miniatures.

The newer D&D editions I like less have, in this respect, moved in a good direction through simplification, even if simplifying elsewhere has made things worse. Simplification and abstraction during play conceal many flaws, which balance one another out, improve play, reduce problems caused by metagame tactics, and benefit roleplaying. Simplifying character creation, characters' research, managing the world, and other “quieter” activities merely saves time while giving us far fewer possibilities. When a game's possibilities narrow, it has to compete with computer games, board games, and so on, which require far less preparation and offer many other advantages. 

If I want to play a tactical or strategic tabletop game, there are a hell of a lot of wargames excellent for that purpose. Even though I do not like Warhammer, I can warmly recommend Warhammer products of that kind. But using far less combat data in D&D and AD&D than in many other games—including Hungary's M.A.G.U.S.—is good precisely because the system's data and such should push less information about the imagined situation out of working memory. Attractive battle-mat combat and various tactical options, instead of character creation options granting freedom, do push it out. We therefore lose both the strategic and tactical depth of good wargames and the opportunity to devote enough attention to roleplaying.

The price of the hp system is that it generally needs levels, so it appears in more restrictive systems, and that healing creates anomalies that need attention and could be improved. Its advantage is that it combines a hell of a lot of factors, simplifying and speeding play; by occupying little informational capacity, it leaves more working memory and attention for roleplaying. 

Hp Is Not Meat Points, but It Is No Miracle Cure Either

The hp system is a damn good simplification whose main weaknesses are its usual reliance on gaining levels and its poor handling of natural healing. Instantly fatal critical injuries could be handled by the combat system rather than the hp system; Rolemaster, for example, does that. Player's Option: Combat & Tactics for AD&D's second edition offers a similar option, so there really need not be a problem with the hp system. In a high-fantasy game relying heavily on magical healing, heroes depending on natural healing are often a negligible factor, and relying on the GM to make adjustments is entirely natural. 

At the same time, a system developer is under no obligation to introduce abilities leading to case 2 in the table at the start of this article. If they appear in a game, that is not the hp system's fault or sin; we should look at the particular ability rather than blame the inherited concept. The Second Wind found in D&D 5 appeared in neither original D&D nor AD&D's first or second edition, and the fighter did not have it even among the optional choices in Player's Option: Skills & Powers. Nor did it appear among the fighter's class abilities in the 3.5 PHB, or even on that book's feat list; in fourth edition it does not appear as a Fighter Class feature or a PHB feat either.

The Second Wind problem is therefore a new one. Of the six states in the table at the start of the article, this new problem produces the troublesome state we had largely managed to avoid. It does so through a mandatory ability of a basic class, right from the beginning of the game. Meanwhile, a party that does not metagame and consumes more potions and other valuable resources because of this system flaw may suffer consequences for play and its chances of success, so the flaw can fundamentally affect the experience from several directions. 

For someone who treats hp as meat points, every hp recovery as removing wounds, and ignores descriptions, the flaw does not arise. But when people cannot even understand that the gap between the described condition and the mechanical condition arises precisely when hp is not meat points, and start making snide remarks, that reveals an old problem with hp: however simple it is, however easy it is to imagine it and the six situations above, some people still find it beyond them and compensate for missing intelligence with rudeness. When a game system deliberately reaches out to idiots, it does not make its new target audience understand the system. It only ensures that anyone else choosing the system encounters people like this. 

I think the problem comes from the developers and official playtest team never reaching the situation above with precise descriptions and an imagined scene. Likewise, they do not see why the average roll is not the only thing that matters when you pay attention to the story emerging in play. Nor did it occur to them that many races' iconic traits would require higher racial maximums, because there is little description of that kind and plenty of dice rolling and somewhat board-game-like play. 

Of course, this could be thought through. Many things can be improved. Or people can attack the criticism. The first step toward correcting flaws is noticing and understanding them. Many flaws are trivial to notice and trivial to fix. You can say they obviously cannot be troublesome, then. But you can also ask: if the developer does not fix even trivially repairable flaws, how can we trust that the system is not full of land mines that are hard to spot in time but may cause bigger trouble later? We could expect the system's creators to pay attention. To get as far as the six hp states in the table... To know which choices are good out of character, what many people would choose in character, and what small adjustments could bring the two closer. And yes, advice about the latter belongs in the PHB, not on fan sites. 

It matters whether we are playing D&D or merely something similar, because we never read two-thirds of the rules, do not necessarily apply the remaining third, and can fit anything onto a few basic roll mechanics. Because we handle inspiration differently, allow deviations during character creation in the name of flexibility, describe damage differently, and handle combat differently. That latter approach can have dreadful consequences, but good ones too. In the latter case, we need to ask: if you, as a “5E player,” are so much better than the developer, why the hell should we pay them? Why do we need the rulebook? Why is the part of the SRD onto which you can fit everything not enough? The question is particularly fair when a significant share of the flaws are new in fifth edition...

But fifth edition came out in 2014. It is five years old. There have been editions followed by the next three years later—3 and 3.5—and others followed after five or six years. There has even been an eight-year lifespan. But that must also accommodate development of the next version, extended testing, and plenty else; identifying the considerations needed for sixth edition should happen before that. Fifth edition was a step in a good direction in many respects, but it was not enough for a hell of a lot of people, and its lack of forethought and many other considerations, large and small, made it unappealing. Nevertheless, it was a step in a good direction, seeking balance between players' needs. That foundation can be built on, whether the goal is D&D 5.5 or D&D 6. The points above, the issue with dice, the number of skills, and a million other things can be reconsidered and improved, because we have a foundation that is not being criticized because much of the community thinks it points in the wrong direction. We do not need to find a path, but to refine and improve.