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: 6411653" data-attributes="member: 42582">I've pulled these two quotes out because they reminded me of a conversation with my players yesterday evening, after our session finished.I'm going to write up a full session report soon, but the summary version is that four 27th level PCs, with 9 healling surges between them, having already fought quite a large number of above-level encounters (they started the "day" about half-way through 26th level), defeated a 31st level solo with two elite 24th level friends. They did so at the cost of 3 healing surges, and with only the fighter PC actually losing non-temporary hit points.As we were reflecting on this outcome, some of us were expressing surprise at the idea, seen more than once on these boards, that 4e is based around a very strict "X on-level encounters between extended rests" baseline. Certainly at paragon and above, the PCs are close to unstoppable!Another idea that came up from the players was that dailies are far from the be-all and end-all of 4e play, because (at least in our game) you only get to use them once per level or so!We were also reflecting on issues for solos (eg the well-known problems with action-economy), at which point I showed them the 5e sphinx entry to explain the Legendary Actions rules for 5e. In the course of this, I had to explain to one of my players, whose only D&D experience is with 4e, that in 5e spells don't generally roll to hit but instead are save-for-half! Which in turn led to some discussions about why 4e (and some of its fairly obvious innovations) have been so soundly rejected.One player, who reads ENworld from time to time, commented that there is enough uniformity to the adverse commentary on 4e that it must somehow be a reflection of something in the system (ie it's not just random bad experiences). It seems that so many people have managed to systematically misunderstand the system, its parameters, its uses, its outcomes.</blockquote>

Verification