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

Reply to thread

Message: <blockquote data-quote="Beginning of the End" data-source="post: 5268961" data-attributes="member: 55271">Yup.Like Justin Alexander says in <a href="http://www.thealexandrian.net/creations/misc/wandering-monster.html" target="_blank">Death of the Wandering Monster</a> there are only two ways to prevent the 15 minute adventuring day:(1) Eliminate any advantage from the "1 encounter, then rest" model of play.(2) Apply meaningful consequences to the decision to rest. (Wandering monster encounters; NPCs trying to hunt them down; or simply NPCs reinforcing their positions, closing up shop, destroying evidence, etc.)The latter is in the hands of the GM. The former could be solved mechanically, but only at the cost of sacrificing mechanical strategy.Another way of looking at the problem is this: There are two varieties of the 15-minute adventuring day. The first is the "nova" (the PCs use all of their most powerful abilities in a single encounter and then rest); the second is the "forced rest" (the PCs are out of resources and must rest/retreat to recover them).These are two different problems.Fixing the Nova: Mechanically you can fix this by removing all daily powers. Non-mechanically, the nova becomes a valid strategic choice (allowing the PCs to defeat more powerful foes) that isn't always the best strategic choice (if it allows NPCs to regroup, escape, or destroy evidence).Fixing the Forced Rest: Mechanically you need to remove the <a href="http://www.thealexandrian.net/archive/archive2010-01.html#20100106" target="_blank">hard limits in your system design</a>. At the very least, this means that hit points need to completely regenerate between encounters.So what would be the absolute worst way to fix the 15-minute adventuring day problem?(1) Give all classes daily powers (increasing the mechanical incentive for nova strategies).(2) Create a hard cap on the amount of healing any single character can receive (introducing a hard limit resulting in forced rests that didn't previously exist).</blockquote>

Verification