Since I'm away from the gaming table for a couple of years I'm using this time to brainstorm and think about how to come back later and run SR3 better.

One idea that I'm toying with is hit locations. In my experience as a GM a lot of times players would want to "shoot him in the leg", or "headshot him", and then there was always a little bit of disgruntlement about how Called Shots technically could EITHER bypass armor OR raise the damage level by one. (So that there isn't really a genuine headshot per se.)

Perhaps introducing hit locations would be kind of flavorful and a bit more intuitive. In most cases this would mean that certain body parts such as the head would be unprotected by socially acceptable armor but on the other hand you wouldn't ever have Fallout-esque bizareness of a shot to the torso magically bypassing armor. The biggest problem of course would be trying to keep the mechanic simple and easy so as to not make combat take too long or get a lot more complicated.

Now, from a perspective of completeness and realism, I think the game Riddle of Steel has the *best* hit location system. The combat engine seems pretty realistic as do the wound effects and there's a great deal of detail. There's even different tables for male and female groin hits. With the male groin hits horizontal stabs or blows are more devastating than with the female groin but the female groin suffers more with vertical stabs or blows. Seriously. That's a lot of detail.

Obviously that would be too much for Shadowrun and it would be a poor patch on the SR combat engine. But how about this? Every time someone is hit they are randomly hit either in the legs, arms, head, or torso. Torso hits are the most probable. The condition monitor fills up as normal (complete with damage scaling) to represent blood loss and shock; perhaps an S wound inflicted to the leg represents a worse bleeder than an S wound to the torso does in the abstract. If someone is shot in the arm for a D wound it means something like their arm is ripped off and the shock makes them fall dazed and incapacitated to the ground. Maybe shots to the head would get a damage level upgrade.

The only difference that this would make over normal shadowrun is that you'd have a certain chance of hitting an unarmored part of the body, such as the head. Called Shots would no longer explicitly either bypass armor or raise the damage level but would isntead enable you to hit the specific body part you wanted. So you could aim for the legs on a guy wearing a vest to bypass his armor, or you could make a called shot to the head and get both an armor bypass and a damage upgrade if the target wasn't wearing a helmet.

Perhaps also if someone took a D wound to a limb and failed the organ loss roll he could just "automatically" lose that limb rather than, say, an eye, just for consistiency.

What do you think? Too much detail, not enough payoff? Or do you think it would be a relatively easy way to make things more dramatic and make injuries more imagineable?

i can only scream and cover my horrified face with my hands in abject fear at the mention of hit locations.

the solution i like a lot more is to just add more special effects to called shots. for instance, rather than "i shoot him in the leg", you say "i'm making a called shot to reduce his movement rate." damage is limited to base, and net successes are used to reduce Qui by 1 per success for the purposes of determining movement.

I can only scream and cover my horrified face with my hands in abject fear at the mention of hit locations— and I like them.

But dear god have these threads been done to death.

In short, it's viable. It can work. It takes a lot of work ahead of time to put together a system that is capable of detail and realism while still being playable, but that is definitely not impossible. Riddle of Steel is good, but most of its design is fairly useless for dealing with ranged combat (also notably useless if you want to play online in basically any medium). In any case, it can be done, but I don't recommend it until you've first cleaned up Shadowrun's rules to fix other glaring fuckups that already make it unreasonably slow.

Run some searches revision and realism and you should find some more detailed discussions. Run some searches for hit locations if you feel particularly emo today.

I tried introducing hit location many years ago and while it was fun (specially when one character *always* got hit in the head when doing random shots). The biggest problem is armor. The armor rating in SR is a general armor rating and... it takes some work.

Remember, you can do this, but you will have to practically reinvent the entire combat system (or at least the armor system).

Personally, i would tend to just go with CP2020's friday night firefight. Each area has a number, roll 1d10 to determine where if the person isn't aiming, and keep wound effects simple (-1 qui/running speed for legs, double damage for head, etc.)

*Screams, covers horrified face*

If there's one thing I hate more than hit locations, it's random hit locations.

~J

I didn't really have a problem with the way "headshots" worked out in SR3. Shooting someone in the head isn't reliably fatal... there's lots of parts of your "head" that don't even have anything vitally important in them (like the mouth) which can get hit without causing instantaneous brain death. Hell, bullets will even glance off the skull sometimes, if they hit it at a flat enough angle or don't have enough power when they strike.

If you really wanted to get around the issue in SR3, you could just let your player make a "double" called shot for headshots. The penalty gets applied twice, but it lets you up the damage level AND lets you ignore armor. Only thing that really broke that was the Smartlink II's uberfrightening called shot penalty reduction, and you could say that the normal +4 applied to the "second application" of the called shot rule to that shot.

i'm not against hit locations per se. i think the damage system used in Deadlands is pretty neat, for instance. the thing is, the entire Deadlands damage system is built around hit locations--it's completely integrated. everything from armor to the One-Armed Bandit flaw ties into hit locations.

With only a few separate pieces of armor (even including the less esoteric options in the Cannon Companion), it's much easier to use common sense than create some formula for conversion. And even if you wiped the whole thing clean and came up with a whole new list of armor types, that's still not reinventing the system, it's just the peripherals and options that have changed.

If you generalize it out down to the "arm, leg, torso, head" scale of hit locations (something that easily be rolled on 2d6), it's pretty easy to kill someone if you do enough damage. Your leg shot hits them right at the top of the femur, breaking hip and femur and severing the femoral artery on that side? Yeah, you'd better believe they're out of the fight and bleeding to death...

The fact that the person in question dies is irrelevant—if you so desire, replace the gun with a nerf gun. My objection is to the idea that someone with a whole boatload of successes (the number of which, if you'll note, indicate the overall quality of the shot) can still hit someone in the leg without trying to.

~J

This is the old "too much realism" debate. Frankly when one of my players wants to shoot someone in the leg or head its the same old combat roll. It will affect how the npc reacts, dropping his gun, falling down from a leg wound, but same damage and armour values. Should they realistically be different? Of course though I personally don't want to do any more rolling in combat than I absolutely have to.

A system my brother put together let you exchange degrees of success to move a hit from one location to another. In your example with the 20 successes to the leg, drop 4 successes and move the hit to the torso, if the player desires. It's not hard to figure out a system that works.

But it still makes no sense. Why do you suddenly have a worse shot than you had before? The random motions of the other person are already part of the TN and the random nature of the die, where does this second force enter in?

~J

GURPs had something like this right? (It's been like over a decade since i played it in college), but I seem to remember ultimately it was more useful to call a shot to the eyes, so you avoid the slight armoring of the skull. At decent skill levels, I recall it being hellaeasy.

The crit tables were fun too. A bastardized version ended up in Fallout, if I recall, where it was also most useful to aim for head/eyes/groin.

When it comes to hit locations, I find I usually stop trying to make a system once I turn it around and pretend I'm an NPC using it on PCs. I'd guesstimate about 50 percent of the time, there's no real reason to NOT aim at a Runner's head. And if for some reason the hit table is made to omit the headshot, I'd go, 50 percent of the time, there's no reason to not shoot someone in the groin. Giggles galore!

I've read through this thread and thought some more overnight about the things people brought up. I've refined my thoughts on using a pain-free relatively simple hit location system based on what people have been saying.

1.) Armor would have to be given coverage stats. I'm thinking the locations should be very simple: legs, arms, torso, head, and that's it.

2.) Any attack which hits with only 1 net success, or 0 for melee combat where ties go to the attacker, is considered to have hit either the arms or the legs (50% chance of either). Hits to the arms or legs fill up the condition monitor as normal and a hit to the arms or legs that fills the condition monitor to D will "drop" the person being hit. The rationale is blood loss and shock that is accompanied by traumatic damage to the limb. It's like in Soldier of Fortune II where if you fire the M590 into someone's leg at close range the leg gets severed and the person is "killed" while blood pumps out in a heartbeat pattern from the stump. Yes, it was a leg shot, but it really traumatized the person's system and he is down.

3.) Any attack with at least 2 net successes (one damage level upgrade) is considered to have hit either the torso or the head. After the hit has been calculated roll 1d6. If the result is a 6 then it was a headshot but otherwise it was a body shot. A headshot gets a "free" damage level upgrade.

4.) Called shots, therefore, still exist; you can call a shot to the head, take the +4 TN penalty, and count on getting the damage upgrade. You can also call a shot to, say, the leg, if you wanted to have a better chance of injuring someone who is wearing a vest and a helmet. A shot with a lot of successes to the unarmored leg would be more effective than the same shot to the armored torso since both leg hits and body hits fill the same condition monitor.


Is this method pain-free enough, do you think?

I've given up on hit locations but when I played SR3, I did try these rules with some success:

http://matrix.dumpshock.com/raygun/rules/a...dy/hitloc1.html

What if you just used the battletech hit location chart, that way you keep it in the family so to speak

No, but seriously the Battletech hit location would totally work. Make center, left, and right torso results one hit location, torso. Rolling a 12 gets a head shot and you apply the the called shot modifier. If your roll results in a Torso (critical hit), I think you'd have to roll snake eyes for that, then apply the armor piercing rules. Then you use Austere Emancipator's idea of X armour covers X locations.

And there ya go... simple.