ryryguy
First Post
So I still haven't read the new books cover to cover, so if this is touched on somewhere else, let me know. But in the generally excellent "DM's Toolkit" chapter of the DMG, there is a glaring absence: no advice about altering powers or creating new ones from scratch.
We do have that "damage expressions" table, and some of the hints about how to use it with monsters can be applied to powers in general. We can extrapolate from the discussion of how monster role affects damage to how player class role might affect damage.
However, there's no advice about how to figure the tradeoffs between damage and extra effects, durations, melee vs. ranged, special requirements, etc. And really nothing about how you might go about creating and balancing new utility powers.
I find the absence to be particularly annoying when considering the "missing" classes of bard, barbarian, monk, druid. It would be much easier to homebrew versions of these with some advice about power design. I'm not so sure I'd go so far as to say power design advice was left out to try to sell more PHB2's, but do you think WotC is intentionally keeping their power design framework proprietary, for whatever reason?
We do have that "damage expressions" table, and some of the hints about how to use it with monsters can be applied to powers in general. We can extrapolate from the discussion of how monster role affects damage to how player class role might affect damage.
However, there's no advice about how to figure the tradeoffs between damage and extra effects, durations, melee vs. ranged, special requirements, etc. And really nothing about how you might go about creating and balancing new utility powers.
I find the absence to be particularly annoying when considering the "missing" classes of bard, barbarian, monk, druid. It would be much easier to homebrew versions of these with some advice about power design. I'm not so sure I'd go so far as to say power design advice was left out to try to sell more PHB2's, but do you think WotC is intentionally keeping their power design framework proprietary, for whatever reason?