Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!

Reply to thread

Message: <blockquote data-quote="Urizen" data-source="post: 2763227" data-attributes="member: 11673">I think that's a problem with any combat system. If, say, you hit someone in the head with an axe, the damage doesn't reflect the reality of what happens to someone who basically gets his head hacked up. This is a problem with any called shot, really, because the player doesn't make a called shot unless they want to have something specific happen, like cutting of the creature's head with an axe.With the D20 system, you could THEORETICALLY make a rule easily enough that allows for this to happen, just raise the number needed to actually hit the character and make the modification reflect the reality of what will happen if the target does get hit. A Fortitude save might also be in order, especially if the victim of an attack might reasonably die.So, If johnny gets hit in the head with an axe, it isn't far-fetched to assume that he just might die from that blow. Johnny's AC is, say, 20, so add 10 to the number needed to hit and if the player hits johnny, roll damage, if the tally equals or exceeds johnny's constitution score, Johnny needs to make a Fort Save or immediately drop to -1 hp.You might even go as far as ruling that if a crit was rolled and confirmed, the head comes clean off. dead, end of story.Let me say though, that there are a plethora of game balance issues that come into play when you start doing this sort of thing.  I'd think long and hard on even allowing called shots, because in the current system they are neither realistic, or particularly satisfying even when a character scores a hit, because the intended result usually never occurs.</blockquote>

Verification