Movement makes games fun and dynamic. Think of the reverse: a camping sniper in a FPS. Or a stationary artillery unit who simply clicks on enemies to delete them. They can be effective, but are not 'fun.' Not a lot of 'tactics' are involved.
Imagine a wargame which is just two armies facing each other across a bare table. Neither side needs to move. They just toss dice until one side is destroyed. Not much fun or tactics involved.
Actual warfare is mostly about maneuver. Forcing the enemy to vacate and give you possession of 'something' (be it a strategic building, oil reserves or a whole country) is usually the end goal of a fight.
I've been thinking about movement in games of late, and I'll try to tie the random ideas into a coherent whole....
1.Movement not Massacre
Most wargames are too bloody and focussed on killing enemies. I've discussed this elsewhere, but a normal round of fire in an average wargame has a 10-25% chance of killing. In most cases, lethality is way too high.
I like in MESBG how most melee results in a 'push back' - disordering the enemy line, handing the winner an advantage positionally and allowing 2v1 'gang ups' later - a losing isn't necessarily lethal now but creates a positional disadvantage which results in lethality later.
This is historically accurate - most casualites occur AFTER an enemy has 'broken' and is in retreat. After the shieldwall has been pushed back or broken apart (movement) then comes the slaughter (massacre). Even the bloodiest battles in the rifle era - ACW for example - would have fatality rates under 5% for the entire battle.
TL:DR Wargames have too many troops re-moved (dead) vs moved. Should there be less removal, more movement as an effect?
1A. Morale and Movement
Piggybacking onto the above - morale is rarely an area where wargames put in much effort. Admittedly, it's not particularly fun - it's probably more fun to kill a bunch of enemies then be killed yourself rather than your unit spend half the game hiding in a ditch.
A typical game tends to have a few states - firearm-era games tending to have more.
"Suppressed/shaken" - units won't move forward, maybe -1 to hit/be hit
"Pinned" - units locked in place, can't retaliate, maybe fall back into cover
"Legging it" - unit makes forced sprint towards own table edge
"Evaporate" - remove the whole unit - the survivors have left the fight completely never to return
90% of games use some or all of the above. For example, fantasy-medieval MESBG mostly has 'suppressed' - a mini can't move towards terrifying enemies if it fails a roll, and 'evaporate' - if a mini fails a morale roll once you have 50% casualties, your dude is just removed.
Overall, there doesn't seem to be much innovation in this area. If most of the time battles result in forced movement rather than outright removal of troops - why don't we have more robust mechanics for this?
TL:DR Morale rules (which could address the movement vs massacre) tend to be basic and lacking innovation.
1B. Movement vs Missiles
Another factor on the movement vs massacre: The relative gun range+effectiveness vs movement speed can impact movement. The usual 24" shoot, 6" move - with say 4+ to hit and then 4+ to kill (25% lethality). Now, what if gun range was reduced to 12*" and movement was increased to 12". Would we see more maneuver? Or, if lethality of missiles were toned down - sat 5+ to hit, 5+ to kill (10% lethality). *(Reminds me of the ludicrously short gun ranges in Warmachine or Bolt Action)
Terrain is also a factor in the effectiveness side of things. But how many games specifically discuss terrain? (size, % of table, distance from each other, firing lanes). Terrain can have a big impact on army balance, but it is also not often discussed (this kinda links with #2 below).
TL:DR When missile weapons are involved, their range/effectiveness impacts the movement vs massacre
2. Setup: First Movement
The setup of miniatures is in effect the first movement or starting positions for the first movement. Or even to setting up terrain which blocks or aids movement (by blocking missiles). Most games put very little effort into this.
"Roll a dice - winner chooses the baseline or whether to deploy first or second. Units are placed 6-12" from your baseline. Or players take turns putting down models 6-12" from the baseline.
There. I just described 90% of rules' setup phase.
This could be a very tactical phase. Very few games do this. Too Fat Lardies Chain of Command has a pregame phase where you move contact markers until they are 'locked' in position by enemy contact markers - kinda like scouts locating each other. This then determines the 'spawn points' where units arrive.
I've been experimenting with simpler systems i.e. in my homebrew tank rules, light tanks/infantry arrive turn 1, medium tanks turn 2, and assault/heavies on turn 3. Units can dice to arrive sooner but risk arriving with a damaged engine (reliable vs unreliable traits help here). The spawn point can be anywhere out of LoS of enemy units and can be anywhere up to sprint move from the table edge (reward more mobile vehicles).
Game designers spend a lot of time trying out new mechanics which are basically new ways to roll dice and have the same end effect. Dice are just RNG.
In boardgames, games like Catan and Carcassone - the setup (placing tiles) pretty much IS the game. Why not a 'placing terrain' mini-game? Why not a minigame including scout units where they duel for position? Why not some sort of resource management mechanic for setup/deployment/terrain?
TL:DR The setup phase of a game (where you first introduce and move models) is pretty unexplored.
3. Movement Order - Move->Fight or Fight->Move
What if you resolved all the shooting and combat and then saw who could move? Try not to get bogged in specifics but think big picture. I'm not saying one method is best but think how many games do this:
Move, then shoot and resolve effects.
Units can do this all one side (All Side A, then all Side B), or alternately within individual units (like Chess); but usually movement occurs first, and combat effects second.
Why not resolve all combat results first, then see who can move after the dust settles? Maybe make combat effect movement (pushbacks, pins, etc) rather than killing. Then, if the model/unit is free from 'status effects' may it move. I'm thinking specifically modern combat where I see (IRL) soldiers shooting/suppressing, THEN moving across to the next bit of cover.
Maybe I'm overthinking things and there's no overall difference? Or I'm just hyper-focussing too much on one relatively unimportant aspect of the 'initiative/move order' spectrum?
I've been playing with this in my "Tank Mordhiem" rules where you usually move first, then shoot; but can opt to shoot (snapshot) in the move phase for a penalty/under severe limitations; or move in the shoot phase at half/quarter speed. I probably need to dig out Crossfire - I'm pretty sure movement was abstracted/limitless until stopped by combat - an interesting angle on movement vs missiles.
TL:DR Most games always have movement first, then resolve combat - whether as whole armies or individual units. Are there situations/eras of warfare where it would be good to reverse this?
This post may be a bit of a rambling collection of semi-related points, but I'm currently really interested in movement in gamesat the moment, probably because of playtesting my own homebrew rules. In one sci fi skirmish system, I had a (overly) complex reaction system that resulted in paralysis (the lethality was fine, but there was too much opportunity making missiles too effective). In my tank game, I'm trying to balance the fact slow/stationary tanks should shoot better and sooner, while avoiding static gameplay where two tanks simply peek from cover and exchange fire until someone loses. In addition, I'm playing a lot of ME:SBG with my son, and really noticed how the very simple 'push back' rule adds some interesting 'micro' the overall game.