Upgrade your account to a Community Supporter account and remove most of the site ads.
ShortQuests -- Pocket Sized Adventures! An all-new collection of digest-sized D&D adventures designed for 1-2 game sessions.

Reply to thread

Message: <blockquote data-quote="Saeviomagy" data-source="post: 1326435" data-attributes="member: 5890">Garbage. In the case of maximise, it's an effect that might have happened anyway. In the case of empower, it's a relatively small difference (only 50% extra damage). In the case of the others, it's no difference between what's attainable and what's not.Because that feat was a resource. The use of the feat no doubt prevented the expenditure of other resources of the party.If a maximised fireball turns a challenge into a nothing, then it was a crap encounter in the first place, and the DM is an idiot. It means that a normal fireball could have done precisely the same thing, and that two fireballs would most certainly have polished off the fight.Except for the fact that a BBEG who dies to a maximised fireball was a wuss anyway. Giving him more hitpoints is a really lame solution.Of course they are - too much has an inherent negative connotation. If something is "too much", then it's bad. Too much water is bad for you. Too much food is bad for you. Too much dieting is bad for you.The problem is defining 'too much'. Personally I think that a minor bit of messing about with probability isn't 'too much'.So spell slots are bad. Hitpoints get used up too - does that mean that they're bad? Is toughness a feat that is inherently bad for the game? What about rage? What about...I think you get the point.If that's the best you can come up with, then I don't think you've really shown much.As for disproportionalities in encounter schedules - that's already a problem inherent in the spellcasting system. Wizards are ludicrously potent if they're always at full charge. Campaigns with that level of activity basically preclude the involvement of any of the fighting classes, as they have almost nothing to contribute.</blockquote>

Verification