Routes and Routs

Fragments on an Abandoned Work on Playing Something Like Tetris for Mass and Vehicular Combat or, I Decide Who Lives and Who Dies (GLoG Class Captain)

I'd hoped to make a variant of Louis Garamond's At Your Order / Tansquare's Orders Received - alas, I was abandoned by the will to complete it, and therefore cast the fragments here, to you, to exorcise my drafts folder of this lingering reminder of my shameful and inveterate dereliction. This is, if not good, at least novel, and may provide a kernel of inspiration to others.
- Epi




Once there came a man
Who said:
“Range me all men of the world in rows.”
And instantly
There was a terrific clamor among the people
Against being ranged in rows.
There was a loud quarrel, world-wide.
It endured for ages;
And blood was shed
By those who would not stand in rows,
And by those who pined to stand in rows.
Eventually, the man went to death, weeping.
And those who stayed in the bloody scuffle
Knew not the great simplicity.



A: Reconceptualise Battlefields, Command Ability 4
B: Command Ability 5
C: Command Ability 6
D: Command Ability 7

I have always wanted to be able to resolve mass combat, with scores of different and varied units operating under different and meaningful circumstances, in few simple rolls. I want real utility from bringing adequately supplied, high morale, and well-suited units to battle. Actually placing units on the map and fighting it out would bring the slowness of a typical wargame and distract from what I consider more interesting decisions (deciding whether or not to fight at all, stressing over maps and marches, and politicking to see who even shows up). But I still want control over how units are employed, which are risked and which are protected.

The setting this is designed for is one of massive flying-wing aircraft carriers - metabolic vehicles - traversing a stupendously vast planet. They rarely shoot at one another directly, instead trading strikes through their attached air groups and managing their ground forces. Doubtlessly the mechanics could be reskinned according to taste, some blackpowder milieau striking me as particularly appealing....

Anyway, to give it to you in brief the cursed solution I've hit upon is a sort of tetrisy arrangement of polyominos. These shapes are placed on a grid1, height six, width according to the skill of the commander. The top ('the front line') faces the enemy, and units near it are first to be damaged. Each shape covers three to six cells and represents a unit. Basic types can be rotated any which way, special unit types have different effects against the enemy or vulnerabilities depending on the whether certain faces point to the front. Each unit provides a number of attacks - each attack is a d4 (if disadvantaged), a d6 (most of the time) or a d8 (if advantaged in some way). Rolls of 4+ are hits. Every unit rolls all its attacks at once, the DM sees how many hits have been effected, randomly determines a column on the enemy's grid, then the DM goes down the column crossing out one cell for each point of damage. Left to right when a column is exceeded, wrapping around if the right edge of the grid is exceeded. Unit vulnerabilities sometimes redirect the damage. Each unit which has half or more of its cells crossed out is moved to the casualty pile - it's combat ineffective for the rest of the battle and may be destroyed. Damage is dealt simultaneously. Before each round, each commander blindly selects their move (attack, hold position, screened withdraw &c) and this determines features of the round of combat or, indeed, whether a round of combat takes place at all. After battle concludes all casualty units are resolved at once.

I can assure you that this is damned fast (most importantly) and, though perhaps gimmicky, presents some interesting tradeoffs to the commander and produces pleasantly granular outcomes. I will now describe the process in full detail.


Pre-Battle Decision Matrix

A contact is spotted at distance. What shall you do? Each side decides blindly and simultaneously. Reactions can be programmed beforehand wholesale, or with simple conditionals (e.g. flee from superior or unknown force, intercept weaker force)

Group A \ Group B Close Shadow Bypass Flee Simple Move Hold
Close ENC INTCHK INTCHK INTCHK ENC ENC
Shadow INTCHK DIST BRKCHK BRKCHK DIST DIST
Bypass INTCHK BRKCHK NOENC NOENC NOENC NOENC
Flee INTCHK BRKCHK NOENC NOENC NOENC NOENC
Simple Move ENC DIST NOENC NOENC ASSESS ASSESS
Hold ENC DIST NOENC NOENC ASSESS NOENC


Options

Speed Difference 1 2 3 4 5 6 7 8 9 A
0 S S S S S F F F F F
1 S S S S F F F F F F
2 S S S F F F F F F F
3 S S F F F F F F F F
4 S F F F F F F F F F
5+ No roll

F: Faster wins, S: Slower wins

Grid(s)

The grid is always six rows, with the top nearest the enemy and the bottom safest. It has a level or an altitude: Ground level grids may be composed of ground, sea, air, or a mix of these. If mixed they are split in columns. A common variant is half ground columns, half air columns, the air columns representing low altitudes here aircraft can directly engage and be engaged by ground units. The terrain proportions do not have to be the same for each combatant.

Note the terrain.

High altitude grids are composed only of air. They are above the lower grids. They can only use Long Range attacks to hit the ground, likewise ground, sea, or low altitude units can only use Long Range attacks to hit them.

The width of the grid is determined by the commander's skill. Less capable commanders can handle fewer columns, so can deploy fewer units.

Units

A unit's most immediate characteristic is its shape, or Footprint2. These are always orthogonality contiguous (i.e. not connected diagonally), and consist of three to six cells. They can be rotated but not flipped. Their characteristics are:

Speed Units (Not exhaustive)
1 Infantry, Crawler
2 Slaved Armour, Cavalry, Tank, Ship
3 Automobile, Destrier, Hovercraft, Fast Ship
4 Speedboat, Groundspeeder
8 Dirigible, Ekranoplane
10 Cargo Aircraft, Helicopter
12 Bomber, Attack Aircraft
14 Fighter


Battle Decision Matrix

Group A \ Group B ATTKPURS ATTKHOLD COMPWDR SCRNWDRW HOLDPOS
ATTKPURS BATTLE BATTLE BATTLE BATTLE BATTLE
ATTKHOLD BATTLE BATTLE BATTLE BATTLE BATTLE
COMPWDRW BATTLE BATTLE DISENG DISENG DISENG
SCRNWDRW BATTLE BATTLE DISENG DISENG DISENG
HOLDPOS BATTLE BATTLE DISENG DISENG NOBATT

Options ATTKPURS: Attack and pursue if successful. ATTKHOLD: Attack and hold position if successful. COMPWDRW: Withdraw Completely SCRNWDRW: Screened Withdrawal: The forwardmost unit in each row remains in combat, the rest withdraw. HOLDPOS: Hold Position

Outcomes BATTLE: Battle DISENG: Disengage NOBATT: No battle

Process

Each round of fighting:

  1. DM Actions
    1. Determine all incoming attacks and long range attacks, whether they are advantaged (d8), regular (d6), or disadvantaged (d4). Roll all at once, count those greater than or equal to 4.
    2. Randomly determine a column or columns, if the target unit is particularly wide.
    3. Apply the damage. Go down the column, crossing out each cell within that column. At the bottom, continue from the top of the next column to the right, wrapping around if going beyond the edge. Skip any number of cells not containing a unit. If damage enters a unit through an 'exposure' face, first fill all of the affected unit's cells in the damage column, then all calls to the left, then all cells to the right. If there is still more damage to apply continue, down, from the rightmost cell of the exposed unit.
    4. Remove all units with half or more of their cells damage to the 'Casualty' pile, noting whether they are protected, regular, or vulnerable.
  2. Player actions.
    1. Each commander has a command ability, limiting the actions they can take per round. Actions include:
      • Rearrange units by rotating or translating them. A rotation, translation, or rotation+translation costs one point.
      • Move units between high altitude and low altitude
      • Embark or debark passenger units
    2. Submit choice on Battle Decision Matrix

Carrier Operations

Metabolic Vehicles have hangarage for their aircraft, and a staging area: A 3x3 grid to which aircraft can be fit for rapid deployment to the actual battle grid. This limits how many may be deployed at once, or the size of strike groups. A launch-recover deck also of 3x3 can feed its returnees directly into the staging grid or back into hangarage.

Future Variants

Blackpowder polyominoruleset? Units are pike formations, musketeers, light and heavy cavalry &c. Long range attacks are artillery, and can soften distant parts of the battlefield. Adventurer scale polyominoruleset. Blocks are individual adventurers.

  1. This is not even a simplified diagram of the battlefield, instead it is an abstract representation of exposure, support, and the commander's ability to utilise their assets.↩

  2. This is not necessarily the unit's literal size on the battlefield but how much mental effort it takes to use effectively. For example, some units are large when they are green and grow smaler in footprint as they gain experience.↩