Long-distance runaround
Converting real-world weapon ranges to an RPG makes me sad and a little anxious. Sad because it's bound to turn out wrong. Anxious because there's a good chance the wrong range value will spark pointless debate over how far a long bow or M16 really fires, and then someone posts a You-Tube video of them firing a ranged weapon at a distance not at all in agreement with what's in the rulebook, and then people are like, "This game sucks—it doesn't even do javelin range right."
So I've been mulling over weapon ranges, and I think I found an answer I'm comfortable with.
Traditional Approaches
The "standard" for weapon ranges was set by D&D, which used a fairly intuitive short/medium/long range mechanic. The idea being (as near as I can tell) that each weapon had a maximum (long) range value, and that it could be reduced in even increments for effective (medium) and close (short) range shots. What's important is that the range increments were based on "thirds" of the maximum. So if a long bow could hit at a maximum of 21", medium was two-thirds of that (14") and short was one-third (7"). This made for neat math, but required that all maximum ranges were divisible by three. Rarely a real issue, but you'll note that we're already accepting a bit of abstraction.
Also important in this mechanic is the concept of a range modifier to your "to-hit" roll. Different versions of D&D handled this differently: B/X imposed a -1 penalty at long range, granted a +1 at short range, and left medium untouched. Another version (I can't remember exactly which) left short range unmodified, but imposed a -2 penalty at medium and -4 at long. Regardless, the idea is that the farther your target, the harder it is to hit.
Another approach I've seen is to establish a single range value, call it "effective range" and assume that any target within it is equally easy to hit. This is more in keeping with the abstraction (i.e., non-simulationist) model I prefer, but it doesn't account for point-blank shots (which should be easier to make) or for targets that are outside effective range, which (when you look at real-world weapon performance) could conceivably be hit—there's always some example (however isolated) that shows how a crack shot reached out and touched someone at a ridiculous distance.
Either system has merit, but neither really feels right for Chimera, which relies on abstraction to be fast and flexible. As I've said before, Chimera is more concerned with what happens than how it happens. In other words, the game moves faster when you concentrate on likely outcomes instead of fussing over exactly how those outcomes are achieved.
Ineffective Range
Keying on the abstraction layer, the single value, "effective range" mechanic is closest to what I'm after. However, this introduces another potential issue—how do you derive that number?
The first hurdle is finding real-world data, and it's surprisingly difficulty to find sources that give consistent effective range values for a given weapon. The Colt M1911 .45 calibre pistol for example. The 1911 Pistols website says effective range is 75 yards. My copy of Twentieth-Century Small Arms (Chris McNab, 2001) puts effective range at 114' (pg. 65). That's a difference of 111 feet. Now, it's probable that "effective range" means different things to different experts, but frankly, it's not worth my time to figure it out. Because I'm writing a game.
The effective range question is harder for archaic weapons, possibly because such weapons—like the long bow, javelin, crossbow, sling, et al.—were all hand-made and infused with too many variables (like building materials and ammo weight) to ensure completely consistent performance. True, you can safely assume that a long bow shoots farther than you can hurl a javelin, but by how much and what if you're using flight arrows or your bow was made of elm or maple instead of yew? Again, you have to rely on an abstraction to make them work in the game.
The second hurdle is translating whatever range value you come up with to the tabletop. Not really a problem unless you're using minis, but as a game designer, you have to account for the possibility. Let's say your M1911 has an effective range of 110' (see—I'm already fiddling with the real-world data). If your battlemat or combat grid is marked in 10' squares, that's a range of 11 squares. Let's say your long bow has an effective range of 640' (well within the conservative and maximum range values I've seen). That's a range of 64 squares, which (as it happens) is a lot of squares, but still manageable.
But when you get into modern firearms, the issue becomes apparent: the Barrett M107 .50 calibre has a range of 5,906'. Are you gonna count out 590 squares? Do you even have a battlemat that big? When you incorporate weapons like this, you can hit anything on the board, which is another way of saying range isn't really a factor. Which got me thinking...
Home On (my) Range
I had already applied a good deal of abstraction to weapon damage; assuming range is just another aspect of weapon performance, why not use the same model?
Think of it this way: certain weapons connote range—you think of a pistol as a short range sidearm, a rifle is a long range firearm, a sub-machine gun falls somewhere in between. As with damage, it's more important for weapons to have workable ranges relative to each other than it is to figure out exactly how far away you can drop a target. The trick is to establish a set of consistent range values first, then assign weapons to them. For example:
- Close (2"): blowgun, most pistols, hurled melee weapons
- Short (4"): short bow, powerful pistols, shotgun, sub-machine gun, hurled aerodynamic weapons
- Medium (8"): sling, early rifles, long bow, light machine guns
- Long (16"): most rifles, medium machine guns, RPG
- Remote (32"): heavy machine guns, autocannon, catapult
- Extreme (64"): anti-materiel rifle
- Ludicrous (128"): artillery
This removes the need for much research (and the guesswork associated with it). It also keeps things manageable on the tabletop in that most small arms max out at long range (16")—longer range weapons (e.g., heavy machine guns and artillery) still work on the battlemat, but they tend to be fixed position guns, so that provides some balance.
To determine a real-world weapon's range, you pretty much decide on where it falls within the scale above. Again, small arms are rarely above long range, fixed weapons are rarely less than remote range. Apply reasonable variation as you see fit. For example, most pistols are close range weapons, but an exceptionally powerful pistol, like the Desert Eagle, might be short range.
In game terms, there's no modifier for shooting at a target within the specified range. If your target is farther away (let's say up to twice effective range to have any chance of hitting), apply a "to-hit" penalty and reduce damage (e.g., in Chimera, the Shoot roll is DL +1 and downgrade the damage die by one step).
Final Words
Is this the best solution? Not for simulationist games, no. But for abstracted combat models, fast resolution on the tabletop, and a flexible way to introduce new weapons into your campaign, it's a good start. I'm trying this out in my Chimera campaign now—if it sticks, I'll add the mechanic to the next release.
In the meantime, what do you think?