Rya.Reisender
Explorer
I personally don't let monsters do "called shots" at all. No PC will ever lose his eyes or an arm or something, unless the player of that PC tells me he wants his character to have such a fate.
After mana/spell-point systems and critical hits, called shots & hit locations were probably the most-done variants back in the day. Maybe a distant third, but they were certainly out there.I've seen players wanting make things like this since I begin to play AD&D 16 years ago. People always want to hit specific body parts to cause different effects, a thing that directly confronts with the HP system of D&D by introducing located injuries instead of reducing abstract vitality. AD&D 2e has its own rules, which are the base of what I've done here.
Better than most called shot systems I've seen. You're pulling in extant sub-systems - disadvantage, reactions, saves, & conditions - rather than making up a lot out of whole cloth. And, you haven't quite made it an end-run around the hp/damage sub-system (which is a huge part of how 5e scales, so bypassing it would be disastrous).I think that Conditions are the perfect resource for this...
If you don’t already have disadvantage from any source, you can attempt a called shot. A called shot is a readied action triggered after the foe has taken its turn "opening" its defense, and the attack is made at disadvantage. ... The main effects of affecting body parts are applying a condition if the shot is successful. The condition is decided by the player but it must have sense for the attack (such as stunning a foe with the pummel of a sword to the head) and the DM has to approve it, and the foe must succeed in a Constitution saving throw to avoid the effect.
Thougths? comments?
PC: "HeroDude grabs a handful of dust and dirt from the ground and throws it in that nasty bruiser's eyes. He runs off this way." -moves mini on map- "Rules-wise, that's a Disengage."If you want to blind the foe so they can't attack you as you run away then use disengage.