Saturday 20 January 2018

Game Design #75: Weapon Range vs Terrain Density

I think I've somewhat covered this in the past in a topic on scale (I recall ranting about how Bolt Action's 24" rifle range, gives them an absolute range of about 50 yards/metres "in scale" - resulting in weirdness such as 28mm paratroopers who could not shoot the length of the Arnhem Bridge model Warlord themselves supply.)   I also have looked at move:shoot ratios (how movement ranges compare to weapon ranges; i.e. Bolt Action copies the 6"/24" (1:4) ratio made popular by fantasy Warhammer - which can be jarringly short with modern firearms. 

However I've been thinking about it a bit lately and would like to come in from a different angle. First of all, let's look at why ranges are compressed.

Restricting weapon ranges can be done to promote maneuver; short-ranged weapons cover less area, leaving plenty of room to move about without taking severe casualties.  In a 2:1 game (say 12" movement, 6" shoot) maneuver is very strong - units can duck in and out of engagements almost at will.  In a 1:12 (say 4" move, 48" shoot) then the firepower tends to dominate - it's hard to move out of range or close with the enemy without being shot to bits. Units will probably camp in cover. 

This obviously is much impacted by the lethality of weapons (the chance of death per attack; a typical 40K-esque roll of 4+ to hit, then 4+ to hit has a 25% chance of causing a casualty and I often use this as a benchmark) - if it is a '6' to hit with a '6' then required to kill (5%?), maneuver is unlikely to be impeded as death would be caused more by luck than firepower.  This is lethality is multiplied by "rate of fire" - attacks per turn - I assume a RoF of 1 for a baseline; but 2 or more is possible with many weapons, and likely with modern warfare.

Terrain and Weapon Range
While playing with my homebrew Tankmunda, I was struck by how much of a role terrain plays in this as well. Using 15mm (1:144) tanks on a 6x4 table, I didn't want engagement ranges to look silly and nerf-gun short, yet I wanted differentiate between the long range capabilities of say a 88mm and a 2pdr. I also did not want tanks able to hit each other from the very first turn shooting between deployment zones.  If I kept the ranges strictly to scale, ranges would be unlimited on the tabletop - a route increasingly taken my many games. Even assuming a 2-3" long tank is say 5-6 metres in scale (2 metres per inch); a 1500 metre gun range would reach 750 inches or 62 feet... a tad longer than most gaming tables...

My solution was to compress ranges as much as I could without them visually looking silly, but also to ensure there was terrain every 8-12" (the distance of the "sprint speed" of most tanks).  And I was thinking - how often do wargames specify how much terrain or how it should be set up?
Not often.  I do know Infinity is very specific.  It has higher than usual lethality (30%+) with a high rate of fire (3+) for most weapons; an attack on a unit in the open is very very lethal. Move:shoot favours shooting with 4" vs 36" for normal rifles (many reach across a table) giving a 1:9+.  Infinity wisely has detailed setup instructions. Setting up a table like traditional 40K (with 3-4 terrain pieces and much wide open space) will see everyone dead in short order. Sight lines must be kept short (8-12") - even a single tall building can offer a massive field of fire, completely unbalancing a game.

 Obviously, the "traditional" 24" shooting range for a 28mm figure assumes little cover; and is handy for a gamer with little terrain. Like a typical 40K table. Games like Infinity with very lethal, long-ranged weapons demand a huge investment in terrain or the game is very un-fun. That said, a WW2 game where bolt action rifles shoot as far as a garden hose look silly.  Warmachine (admittedly steampunk) even has sniper rifles with 14" range (vs handguns that shoot 8" or so). Yikes!

But what can we do to mitigate this?  How can we make it so weapons shoot further without messing things up?  Well, weapons can have their lethality tuned down.  Want to double ranges to 48"?  Make it so it hits on a 5+ and kills on a 5+ on a d6; now instead of 25% chance of killing per attack, it's more like 10%. This compensates for the doubling of the range.  Maybe units can be stunned or suppressed; instead of outright removed.

It's all about terrain, baby
However I'd like to focus on terrain (or lack thereof).  On the importance of making it clear how much terrain is expected - how far apart, and the impact of the terrain.  I'll assume that being in cover gives a 4+ d6 (50%) save.  If terrain is no farther apart than the average unit move (say 6") we have effectively halved the lethality of the weapon (down to ~13%).  We could double firing ranges with no major issues.  If terrain is farther apart than units can move in a turn (say 12"+) then lethality is less impacted (it will also encourage camping).

The effect of cover (modifier to "to hit" or saving throw) is also worth thinking about. If we assume a 4+ (50%) saving throw for the average cover - what effect would a 2+ (83%) save have? It would confer near-invulnerability on units and discourage them from ever moving.  In contrast, a 6+ (17%) save would make the cover barely worthwhile. This ties with rewarding and punishing players; using saves and modifiers to direct them in the way you want them to play.

Weapon ranges, movement distances and the lethality of weapons are all used as balancing methods.  They dictate particular playstyles and most game designers adhere to pretty common formula.  This can result in silly looking games (modern rifles shooting the same range as bows or slings; the average elf archer would handily outrange a Bolt Action grunt with a Mauser).

Terrain however is also a major balancing factor with as much impact as any of the above methods. And few wargames rules actually address this. How much terrain? Where? Even - what effects does the terrain have - many times terrain modifiers seem to be copied-and-pasted regardless of genre. Should "cover" (and it is often genric; or divided into "soft" and "hard" at best) have the same 50% save to a M60 as it does to a sling?  How often is terrain actually addressed in rules.


  1. It's complicated subject in terms of game design. I met it a few years ago when designing PMC 2640. In early playtests there were +2 Firepower bonus for stationary fire and +1 for close range. It made the game quite static, with dull exchange of fire at the border of effective fire range. Swapping this parameters and big bonus for crossfire made the game much more dynamic and fun. For me the key is making the game in such way that range advantage requires some smart approach to be used.

    In Shadows in the Void I decided that the spacecraft fights on huge distances, but also moves with extreme speeds, so average range to move ratio in case of missiles is about 3:2 (maximum 5:1,2) and in case of cannons it's about 1:1,5. Maximum range is 50cm (in game scale it's ~1000 km in deep space) and the average fighter speed is 16cm or 20cm. Such appraoch with combination of lock-move-fire turn sequence requires nice skills to make the proper usage of range advantage. Good range is much more than "two turns" of safe firing.

    1. That's a really good example of using modifiers to drive player behaviour. I really like flanking, and dislike the "push models into a pile in the middle" so any homebrew rules I have tend to have hefty flanking bonuses.

      Reducing the move:shoot to favour movement makes the game more dynamic; if, as you say, there is quite a few "safe turns" of firing then weapon stats tend to trump maneuver; emphasizing good dice rolls over a player decision.

  2. I once made a lot of people very angry at me for suggesting that infantry move often tends to be about 6" regardless of time and ground scale because it's defined by our gaming tables :-)

    1. Unit movement IS 6" in 99% of game (I exaggerate somewhat; it varies between 4-6" most times, with "sprint moves" doubling them on occasion)

      I do think it's a factor of how it "feels" on the tabletop; but for some reason shooting ranges get ignored and fantasy bow ranges just get copied+pasted.

      When looking through new rules, I mentally use 24" shoot, 6" move, 25% lethality as "baseline stats" - based on the familiarity everyone has of 40K. I can usually predict how a game will play out before I have models on the table.

  3. MacavityandMycroft23 January 2018 at 17:35

    My current game design IS fantasy but I'm working with the advantage of a built-in lack of balance requirement.
    So far (two scenarios played twice each) the system of a baseline for ranged troops (x damage dice y range) and their effectiveness on each turn being variable where 1 success=base 2 successes=base +1 range OR damage die. In the very limited sample, it seems to be working with my focus (and the dice) assuming 2 successes, with 1 being a lousy shot and 3 being an inspired one.

    My very limited sample is showing well, giving the chance for a talented individual with a lousier weapon compensating for it a bit.

  4. I seem to recall Swuad Leader (and possibly Rogue Planet) had some novel ways for terrain and movement to interact but I can not quite recall. I think it was something like unlimited movement between terrain?

    1. Rogue Planet, yes. Crossfire I think is the grandaddy of the "unlimited move until you hit something" genre.

  5. I'm currently working on a grand tactical game (which will be played on a grid of squares - the Horror!!).

    I expected movement and command/control to be the difficult elements of the game.
    In fact shooting is proving a lot harder.

    I'd started with the assumption the cannon would fire 2 or 3 squares, while muskets could hit an adjacent square, and the sequence was red move, blue shoot, blue move, red shoot..

    Playtest quickly showed that only a chump would make the move into musket range, since this handed the first big volley to your opponent.

    Games then consisted of both sides hovering outside musket range engaging in artillery duels.

    The really unexpected solution was to allow both sides to perform close range shooting after each movement turn. They now advance while firing.

    A happy side effect is that I don't require a bonus for close range fire (They fire twice as often).

    It's not all good news.
    I'm still struggling to tune shooting lethality correctly.

  6. "I'm still struggling to tune shooting lethality correctly."

    I always start on 25% lethality - 50% to hit, then 50% to wound; and go from there. (That is BEFORE modifiers - presuming a 50% cover save that is 12.5% against cover).

    This is common to many familiar wargames, so it at least feels right to most players....

  7. Good suggestions and I'll certainly run a playtest using those settings.

    I'm on completely unfamiliar ground with the scale of this game.
    An infantry element represents 2000 man, and up to 6 elements can occupy one square.

    There's a little voice in my head screaming "They shouldn't die so fast when there are that many".

    Like any personal "under development" set of rules, I've a thousand new ideas every day, and at least 999 of them are absurd.