Tuesday, January 27, 2009

Healing Surge - The "Best Doctor" Problem

Healing surges aren't a perfect solution. One difficulty is the "best doctor" problem.

Players have a limited supply of healing surges, which can only be replenished by taking an eight-hour "extended rest". Extended rests not only cost in-game time, they also reset your milestones and remove any excess action points you've accumulated.

During combat, players will take whatever healing they can manage. After combat, the rules allow players to use as many healing surges as they wish to heal up.

However, using an unbuffed healing surge is for suckers. The cleric is the best doctor. If you heal yourself, you're getting back a quarter of your hit points, rounded down. If you let the party cleric use a healing word, you're getting back the surge value, plus 1d6, plus the cleric's wisdom modifier. The cleric gets two of these "per encounter", which can be refreshed through a short (five minute) rest.

What was intended to be a quick way for teams to get back into fighting shape after a battle becomes an extended dice rolling session. No one wants to waste a valuable surge on an unbuffed heal, so now the cleric's rolling 1d6 for every surge for every player, and making notes as to how many groups of five minutes everyone rests to reset the healing words.

This appears to run counter to the design philosophy of 4th Edition. Post-encounter downtime is supposed to minimised under the new rules. One option is to restrict the use of these powers to honest-to-God encounters. The cleric is now inexplicably unable to call on his or her abilities when not threatened by monsters. Unimpressed players will begin attacking nearby rats and insects in an attempt to trigger a heal-enabling "encounter".

A better solution is to run a house rule. Establish that healing words used outside of combat consistently deliver a heal bonus equal to the cleric's wisdom modifier plus one. This isn't ideal, but it allows people to calculate their healing quickly without the cleric having to roll a storm of dice.

On the bright side, 4th Edition makes cure light wounds and cure serious wounds dailies. Few parties will take an extended rest just to reset those suckers when they're otherwise fine.

Questions:

[1] House rules are good, but surely this issue arose during playtesting. Why wasn't it specifically addressed in the Player's Handbook? Or alternatively, is there something about the operation of encounter powers or heals that I'm not aware of which would circumvent this problem?

5 comments:

Vaurien said...

Just a technical clarification: an extended rest is actually only 6 hours.

Greg Tannahill said...

It is too! My apologies; I was probably getting confused by the recommended 7-and-a-half hour rest if players are keeping a watch.

Anonymous said...

Their is one mention on powers I rand across either in the Keep book or the DMG regarding using attacks on random rats/bugs to trigger heals: you can only trigger these effects off of enemies that are a threat. So, as the paragraph said, you can't just carry around a bag of rats with you, hitting them for some extra healing periodically.

Doug said...

I think RAI is that heal powers quickly fill in the gap between encounters.

Without even thinking I have simply assumed maximum heal value is achieved outside of combat and applied basic maths to the situation.

minutes healing = d ÷ h x 5

d = total party damage
h = total hp to heal per 5 minute rest

For "h" simply claculate your part's maximum possible heal per short rest. Best yet you only need to work "h" out when your healers' ability to heal changes (usually once per level).

Never, ever had a problem with it.

eabod said...

You keep mentioning playtesting. But tabletop game design has historically not had a dedicated QA department. This means that playtesting is typically done by the designers themselves (also true of low-budget video games).

Unfortunately, designers tend to test only in terms of "positive" testing - "does it work as intended?" Once a positive result is observed, testing stops.

QA Professionals, though, are trained/conditioned to "negative" testing - "what can I do to break this?" and "what happens if I?" This kind of testing can go on virtually forever, and requires incredible amounts of re-playing the same thing over and over.

Tabletop game design schedules/budgets do not allow for the kind of rigorous testing that would have found some of the issues you have been describing. Granted, this module in particular is bad in a lot of other ways, too, but I suspect that time/space/money limitations had a lot to do with why it's so poorly implemented.

As we say in computer game design: Congratulations! You're paying to Beta test the product! :)