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

Reply to thread

Message: <blockquote data-quote="Primal" data-source="post: 4175232" data-attributes="member: 30678">I agree. I know the designers seem to take a lot of pride in having been able to "minimize" the power descriptions/stats, but the simulationist in me seems to be lost with most of them...  I understand how the power functions mechanically, but not how it happens in the story. And I've never had this kind of confusion with any previous edition of D&D. I can only imagine how it feels to "newbies". I get the same feeling from other excerpts as well, since those 'monster customization' rules make sense to 3E veterans, surely, but if I think back to my teen years, I'm not sure I would have understood how they work (especially as english is not my native language). I hope that the rulebooks will have more concrete examples, because now it feels to me (on the basis of these 'excerpts') like the books are written for people who're intimately familiar with the 3E rules.I can understand that using those keywords/"tags" must make a lot of sense to the designers, and they're probably so "into" the system that it all makes sense to them in the story as well. I'd say, however, that it takes an exceptionally good DM to convey this same kind of "understanding" to the players -- at least to my group (and we're all "veterans" with some 20 years of gaming experience under our belts). Or maybe the new generation is better in handling the combat as an "abstraction" from the story, concentrating on the mechanical effects and thinking about the story only after the combat is over? As for the 'exception-based' design... some DMs will shine with it, while others will struggle to master it even moderately. I probably belong to the latter group, because it's a "hybrid" system which is not completely 'trait-based' -- I just don't like the way it combines so much 'crunch' with those freely-determined "powers". Not to mention how differently the system treats the PCs. If it were a completely 'descriptor/trait-based' system (like many Indie RPGs I've run), I think it would work far better, at least for me and other DMs like me. Or, if your players, as I mentioned above, do not care about the mechanics (i.e. they are not cynical 'simulationists' who always ask for logical explanations for every rule in every situation or want to imitate/learn "monster powers") but focus on the story and come up with the explanations in their own heads.     This actually leads me to what I think will be a major issue with 4E. When every DM starts developing their own "variants" (say, Bugbear Shurikenmasters or Orc Shaman Firebreathers) I think there will be a lot of arguments over the choice of "powers". Comments like: "No, you should have used Range 4 Fire Attack that causes 2D10+CON damage... take a loot at Drgaonblood Flamebrother" or "That's a stupid power for a city guard captain... he should have something like 'Aura of Loyalty' instead of that stupid pseudo-magical 'Summon the Troops'-ability. And it should recharge whenever an opponent is bloodied, *not* on 5 and 6!" or "That's how you stat an experience NPC cleric? Change that 'Heal like Hell' ability into something more appropriate like 'Lead the Masses'!". And so on. I hope there will be a list (and a lot of examples) of "logical" ability choices for different types of your own variants, because otherwise I can see a lot of arguing taking place (especially on the forums) over how DM X or Designer Y should have given NPC/Monster Z ability W and Q instead of O and P. And try running a game to another DM, and I'm quite sure that he can't resist commenting on some of your NPCs and monsters, and even though he did it in private, I'm sure it is as annoying nonetheless ("You know, that elven scout we encountered... I think you should have based him on the Human Deathbow Archer in DMG, and not Elven Skirmisher. And I would have given him a rechargeable encounter power like 'Triple Shot' instead of 'Unlimited Energy Arrows'.").</blockquote>

Verification