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

Reply to thread

Message: <blockquote data-quote="the Jester" data-source="post: 6576713" data-attributes="member: 1210">In the interest of fairness, I thought that I should mention that I recently had my first complaint about ES@1 from a player, although I'm not sure that the real issue was the starting at first level vs. my having really, really hot dice (and the pcs just... not having good dice, at all). First off, the player in question had his pc die when he was caught in a massive spray of acid from a horrible monster. That pc wasn't 1st level, though, and died by virtue of very low hit points (Con was either 7 or 9) and the fact that the pcs were fighting a monster above all of their level... they almost tpked there. The player's replacement pc was a warlock. 8 hp. He, a 3rd level ranger and a 5th level paladin were doing some dungeoneering and ran into a group of four orcs. And I rolled amazingly well. And they didn't. The paladin's AC is 17, IIRC, and I never missed him. The pcs, OTOH, rolled poorly, made some bad tactical decisions and just didn't have any luck at all. The warlock used a witch bolt on an orc, who dropped him with a single javelin. Then, while the paladin and ranger kept on missing or doing pretty minimal damage, the warlock failed his first death save... and rolled a 1 on the next one. In the end, the ranger and paladin both went down, too, but they were captured, not killed. So the player was burnt (understandably, I think- it sucks to lose two pcs in one session), and complained about the "ES@1" policy. I'm not entirely sure that was the cause, but I definitely sympathize with him. OTOH this game did convince me that witch bolt isn't as cool as I thought, since you're limited to a "come and kill me" kind of range.</blockquote>

Verification