mach1.9pants
Hero
Once again, to me, that is a common sense issue. I would not allow the auto-kill animilator in my game.
Great thread, good catches.I've been playtesting the butt-thunder out of this feat, trying to find as many possible exploits and game-breaking combinations that I can. So far, these are the big ones that I've uncovered.
Yes. The GM deciding whether a given action requires a DEX check or a STR check = good empowerment. The GM deciding whether or not the wall is so slippery that it causes disadvantage on a climb attempt = good empowerment. The GM having to decide whether Reaper does or doesn't interact in a certain way with thrown weapons = bad rules. The GM should be adjudicating situations, not having to fiat the outcomes of action resolution.Personally, I would like to see them do both. Clear, well-thought rules + empowered DMs = fun for everyone.
I would write the feat along the following lines: that all your attacks hit and deal damage, but only if your attack roll is successful do you get to roll any damage die and add non-stat bonuses; otherwise your damage is just your stat mod bonus.Nearly all of them, actually...the exceptions being the stacking damage to spells (#5 and #6 of my list.) Some gamers will want Spell-Slayers, so if they want the Slayer feat to apply to magical attacks, they should word these spells a little more carefully to prevent abuse.
But yes. Adding a few more qualifiers to the Reaper feat would go a long way.
Actually, the interaction with spells may even be desirable - since it allows the Reaper to be the "Striker" theme for all classes. Of course it could very wel be that we only got simplified wordings that only apply to the one character that has the feat in the playtest. The Fighter doesn't have spells, so no point in making a distinction between spells and weapon attacks.1.) Somewhat. Reaper interacting with spells (which the designers probably didn't intend to happen) can be nipped with one word added to the feat "melee" or "weapon." The rest are just judgement calls a reasonable DM can (and should) deal with quickly. I still think there is places where the rules need clairity and renfinement; this may just need a nip/tuck.
2.) AFAIK: it was an internet thing like Pun Pun. I welcome the correction.
Actually, the interaction with spells may even be desirable - since it allows the Reaper to be the "Striker" theme for all classes. Of course it could very wel be that we only got simplified wordings that only apply to the one character that has the feat in the playtest. The Fighter doesn't have spells, so no point in making a distinction between spells and weapon attacks.
But if it is supposed to work with spells, at least the issue with Ray of Frost would need to be looked at. A miss shouldn't deal more damage than a hit, obviously.
Pure conjecture on my part, but so far:
1) I'm expecting the full text for Reaper will restrict effects to melee weapon attacks.
8. A slayer fighting with a torch can choose to deal fire damage or bludgeoning damage, even if the fire never touches the target.
2) I'm also expecting that many of the themes are more akin to "class kits", or "builds", and less flexible than the full 4-way combination choice (race/class/background/theme) guessed at by a lot of posters.
. . . on part (2) I will be very happy if I turn out to be wrong. It would be great if all four dimensions worked together to make really versatile PC build system, but I think we'll have that in a minor way, and that only race and class will make sense in *all* combinations.
I seem to be spamming this a lot, but:
'it's all attacks, including spells and ranged.' - Mike Mearls, Twitter
As I posted upthread, and on another thread, the solution to this is pretty simple: the effect of Reaper is that you get your stat mod compoment of damage whether your attack roll is a success or a failure. Which means that, if there was no damage in the first place (as with Ray of Frost), or no stat mod component to it (as with grenade-like missiles) then Reaper doesn't apply.But if it is supposed to work with spells, at least the issue with Ray of Frost would need to be looked at. A miss shouldn't deal more damage than a hit, obviously.