Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="pemerton" data-source="post: 6321005" data-attributes="member: 42582">I know how temp hp work.If you take damage, temp hp are no different from actual hp. They only "go away after 5 minutes" if you didn't lose them to hit point loss.This means that 2nd wind as temp hp is silly for two reasons:* You're better off using it before you get hit, to get a maximum buffer against being killed/knocked unconscious. That is not a second wind; * The only time the final outcome ends up being different from actual healing is if you didn't need the extra hp (and hence misjudged your need to second wind). This is something of a corner case that it is not worth designing a system around, in my view.For those who don't want short rest chaining of this ability there are multiple ways to handle that without distorting the key features of the ability itself:* The most severe is to make it like a barbarian's rage in 3E: the PC takes damage equal to the amount of their healing once the combat finishes; * The ability can only be used during combat, or within a certain (small) time of having taken damage; * Any rest of 1 hour or more but fewer than 8 hours counts as only a single short rest; * Capping short rests per day; * A table understanding not to chain short rests; * Using the standard time management devices that Mearls et al mentioned (wandering monsters, ingame time pressure, etc).D&Dnext was always going to need the GM to be very active in pacing management, because of its return to extremely assymetric suites of resources across classes. I think it's somewhat amusing that the first brushfire over this issue involves fighters rather than casters - that's a nice change - but the issue was always going to break out somewhere!But anyway, resolving this issue seems to be about as difficult as extending the duration of extended rests in 4e to deal with the complaints of "overnight healing" ie utterly trivial.</blockquote>

Verification