Lake Trasimene - Order of Battle

The battle of Lake Trasimene 217 B.C. was Hannibal's second major battle in Italy but took the form of an ambush rather than a pitched battle. The army of Flaminius was ambushed on the shores of Lake Trasimene. The Romans were caught in march order and slaughter ensued with many thousands being driven to their doom in the lake. Following this, Hannibal's African troops were able to upgrade their arms to the best of the Roman ones.


CARTHAGINIANS

Hannibal's army strength is unknown but it would not be much less than the 40,000 he had at Trebia where he had few casualties and those mostly from the Celts. I assume he was able to resupply from the Celts after such a handsome victory against their Roman oppressors.

We can re-use the Carthaginian order of battle from Trebia minus the elephants. What attrition amongst the men that may have occurred during the winter can be considered inconsequential for our units which are only approximations.

The troop ratio here is 150. While a ratio of 1:75 would work for the Romans and provide an army big enough for an 8 foot-wide table, this would be far too large for the Carthaginian forces to scale up to a 16 foot deployment.

Heavy Infantry - 9 units
4 standard African units (64)
2 standard Celt warbands (40)
3 standard Iberian units (48)

Light Infantry - 6 units
1 standard Ligurian unit (16)
2 African small units, skirmishers (16)
1 Moorish small unit, skirmishers (8)
1 Iberian small unit (8)
1 Balearic small unit, skirmishers (8)

Cavalry - 9 units
3 standard Celt units (36)
4 small Numidian units (24)
2 standard Iberian units (24)

24 units - 565 points


ROMANS

Lazenby argues that Flaminius would have found it hard to fit more than 25,000 men in the confines of the terrain at Trasimene. He assumes that there was a normal consular army of two legions plus allies.

The paper strength of a Republican legion was 4,200.

Total army strength was around 25,000 (Fabius Pictor):

Roman Legion I    4,200
Roman Legion III 4,200
Cavalry                 not fewer than 4,000 (Polybius)
Allies                    ~ 6,300 per wing

Employing a ratio of 1:150 to get us to one small unit of 8 models as the minimum infantry unit size means that :

Roman Legion I & III - 7 units
2 velites (16)
2 hastati (16)
2 principes (16)
1 triarii (8)

Ala Dextra & Ala Sinistra - 11 units
2 velites
6 hastati
2 principes
1 triarii

Cavalry - 4 units
1 Roman equites
3 Allied equites

22 units - 442 points

Since most of the Roman units are small this makes for a tough fight where they are vastly outnumbered, but due to the non-linear scaling of points to unit size in Hail Caesar the Roman force is only 78% of the points of the Carthaginians, provided the units are fielded with the typical stats rather than with the reduced stats suggested for Trebia on account of army fatigue and lack of brekkie.

This may make for a more competitive game rather than a simple exercise in sweeping Roman units into a watery end in Trasimene's waters.

Collecting an Army: how many units is enough? - Part 2

It's not strictly necessary to calculate troop to figure ratios in order to have a good game. But, for a scenario to broadly conform to historical conditions, for opposing armies to be appropriately scaled to each other, and for that scale to fit to your playing area, it helps to work out troop ratios based on historical accounts.

Working troop ratios and dimensions is also helpful for planning your purchases. In my case, a lack of clear planning of unit dimensions led me to collect too many figures. Luckily with a Carthaginian army the component nationalities are readily used for other army projects.

Below is an example based from the Second Punic War.

CARTHAGINIANS

The battle of the Trebia, 218 B.C. offers a good starting point for building a Hannibalic Army for the Second Punic War. It also offers roughly equal sizes for the Carthaginian and Roman forces, around 40,000 troops each.

Following the all cavalry clash of the Ticinus, the engagement at Trebia was the first pitched battle between the Carthaginians and Romans after Hannibal crossed the Alps.

After the arduous Alps crossing, Polybius (III.56) says that Hannibal's army contained 12,000 African and 8,000 Iberian infantry, with not more than 6,000 cavalry. After the victory at the Ticinus, the Celts joined in large numbers.

By the time of Trebia Hannibal's troops numbered 20,000 heavy infantry (Africans, Iberians, and Celts), 8,000 light infantry (mostly African and Iberian, including Balearic slingers) and over 10,000 cavalry. In addition, his brother Mago commanded an ambush force of 1,000 Numidian cavalry and 1,000 picked infantry.

The additional 9,000 infantry at Trebia beyond the 20,000 combined heavy and lights just after the Alps must be credited to the Celts, as must 5,000 horse. It is likely that the Celts had few skirmishers.

This gives a total at Trebia of 29,000 foot and over 11,000 horse.

Borrowing from the analysis of Trebia in Lost Battles, with some modifications to reconcile the totals listed after the Alps and at Trebia, this breaks down into:

21,000 Heavy Infantry
9,000 African
6,000 Celts
6,000 Iberian

8,000 Light Infantry
3,000 Celts (including Ligurians)
2,000 African (Libyan)
1,000 Moors
1,250 Iberian
750 Balearic

11,000 Cavalry
5,000 Celt
3,000 Numidian (light)
3,000 Iberian

~30 Elephants

In order to translate this to the tabletop for practical play we apply a scaling factor to the above numbers to get a reasonable headcount for the number of figures needed for an eight foot-wide game.

Following Hail Caesar's recommended unit sizes I am using 16 man standard units, 8 man small units (typically skirmishers and lights) and 12 man standard cavalry and 6 man small cavalry. Celt warbands and the like are 20 men strong.

Employing a ratio of 1 figure to 150 historical troops, with some rounding off involved, breaks the above numbers down into (number of models in brackets):

Heavy Infantry - 9 units
4 standard African units (64)
2 standard Celt warbands (40)
3 standard Iberian units (48)

Light Infantry - 6 units
1 standard Ligurian unit (16)
2 African small units, skirmishers (16)
1 Moorish small unit, skirmishers (8)
1 Iberian small unit (8)
1 Balearic small unit, skirmishers (8)

Cavalry - 9 units
3 standard Celt units (36)
4 small Numidian units (24)
2 standard Iberian units (24)

2 Elephants

26 units = 42.3% infantry, 15.4% skirmishers, 34.6% cavalry, 7.7% elephants

611 points (with a Ld 9 General)

Elephant numbers were determined by allowing one for every ten units in the army.

This produces a battle line of 9 heavy infantry with 3 cavalry wide on each flank. (Skirmishers and lights are arrayed in front of the heavy infantry line). A total of 15 base widths (160mm each), or 2400mm, just short of 8 feet.

A 6 foot-wide game could be accommodated by trimming the cavalry down to 1 base width per flank, to fit within 11 base widths.

I initially planned for a ratio of 1:80 but this produced a battle line that was too big, around 10' 6" wide, which would be okay for a very wide game, but would require a special gaming venue.

This actually makes my initial project much more manageable. I bought too many figures!

A quick comparison between the list derived above from a single historical battle and the generic Carthaginian 3rd Century B.C. list in Hail Caesar Army Lists: Biblical & Classical shows quite different troop ratios.

The HC army list recommends that 66+% of an army's units should be infantry, excluding skirmishers (which can be up to 50% of the units), up to 25% cavalry, and up to 10% elephants.

Hannibal's actual army at Trebia was more cavalry-heavy, which is what allowed them to sweep away the Roman cavalry from the flanks in this and future battles. Even from the raw troop numbers cavalry amounted to 27.5% of the army, meaning that the Carthaginian army list in HC needs some revision for more historical play. I have one in the works and I'll get round to posting it later.

While an army list can be helpful for a generic game or figuring what types of units are in an army, as well as their game abilities, the army list cannot adequately replace an order of battle (ORBAT) derived from an actual historical encounter.


ROMANS

Polybius (III.72) claimed Sempronius's forces comprised:

16,000 Romans
20,000 Allies
4,000 Cavalry

Using a 1:150 ratio, the standard proportions of the manipular legion's components (a 1,200:1,200:1,200:600 ratio for velites:hastati:principes:triarii), and assigning the surplus numbers amongst the Allies to the hastati and principes, we get:

Roman Legions - 14 units
4 small velites (32)
4 small hastati (32)
4 small principes (32)
2 small triarii (16)

Italian Allies - 16 units
4 small velites (32)
5 small hastati (40)
5 small principes (40)
2 small triarii (16)

Cavalry - 4 units
3 small Allied cavalry (18)
1 small Roman cavalry (6)

34 units = 88.2% infantry, 11.8% cavalry

707 points (Ld 8 general)

If deployed in a checkerboard triplex acies this works out to an infantry battle line of 9 standard base widths plus cavalry wings 2 base widths wide. A total of 11 base widths.

Sabin has voiced some skepticism about Livy's claim that the Cenomani Gauls served as Roman allies, but they can be accommodated by broadening the battle line to 12 base widths, still shorter than the Carthaginian one.

A note for Hail Caesar: there's been lots of debate about whether small unit Republican Romans are overpowered compared to standard units. This is apparent from the points value (HC assigns one point per stat value; higher points, higher stats). The ORBAT above can always be modified to feature standard infantry units.

Roman Legions - 9 units
4 small velites (32)
2 standard hastati (32)
2 standard principes (32)
1 standard triarii (16)

Italian Allies - 10 units
4 small velites (32)
3 standard hastati (48)
2 standard principes (32)
1 standard triarii (16)

Cavalry - 4 units
3 small Allied cavalry (18)
1 small Roman cavalry (6)

23 units

552 points (Ld 8 general)
(versus 611 points for the Carthaginian list above)

If you want to retain small unit manoeuvrability then a more elegant solution that Rick Priestley once recommended to me is to tweak the stats. The points difference between the small unit and standard unit Romans above are due to the fact that while unit frontage halves the unit stats decrease by only 18% (including the scaled cost for pila and Drilled).

In that case, downgrading the stats of the Republican Roman small units from heavy to medium infantry, from light infantry velites to skirmishers, as per the manipular legion under the Camillan Roman list from the Army book, produces an army of 637 points to the Carthaginian's 611.

For Trebia and most of the Italian Campaign the Roman troops arguably should not be more powerful than the Carthaginians. They could on occasion be penalised with a Ld 7 Consul. For a Trebia scenario one could consider further downgrades or penalties - such as a 1 point reduction to stamina - to represent the weaker morale of the Romans who failed to eat the most important meal of the day: breakfast.

Roman Legions - 14 units
4 small velites skirmishers (32)
4 small hastati medium infantry (32)
4 small principes medium infantry (32)
2 small triarii heavy infantry (16)

Italian Allies - 16 units
4 small velites skirmishers (32)
5 small hastati medium infantry (40)
5 small principes medium infantry (40)
2 small triarii heavy infantry (16)

Cavalry - 4 units
3 small Allied cavalry (18)
1 small Roman cavalry (6)

Stats based on the Camillan Roman list in the Biblical & Classical Armies book. All units have a -1 to stamina to reflect their fatigue from crossing the icy Trebia river and skipping breakfast.

603 points

Collecting an Army: how many units is enough? - Part 1

The wargamer needs something more detailed than long rectangles
though units are but rectangles from a plan view.

A challenge peculiar to historical wargaming is deciding on what units and how many one needs in order to play a particular army, battle or campaign.

Reconciling financial constraints with often vague historical details, as well as a practical size for a collection that can be painted and based in a reasonable amount of time, is quite a logistical and research challenge.

Perhaps this is why orders of battle appear so rarely in ancients wargaming, both in print and online, despite the fact that one can't run away from having some 'ORBAT' when one sits down for a game.

The kinds of rulesets one plays with and their representational conceits will also have a practical effects on how figures one needs to acquire and prep. In my case, I have to wrestle with the desire to proportionately represent the look and structure of the armies I collect versus pragmatics of getting a rules-conforming unit on the board.

For example, if each of 10 maniples of hastati was arrayed in a formation 20 files wide and 6 ranks deep, is it practical to use a 28mm scale battle line two models deep by 66 models wide to represent one of the acies of a legion (a 1:3 ratio)? For a typical four legion consular army with each model occupying a width of 20mm, this leads to a gaming table at least 17 feet wide, without factoring in space for the cavalry wings!

Clearly, we need a more practical scaling method for the ordinary game table that is at least six, and at most, eight feet wide.

Systems with a hard limit, such as points-based systems that cap at a certain number of points or have a 'sweet spot' point total, in some ways make things easier by forcing a limit to what you can fit into your budget. Examples would be Warhammer Ancient Battles and similar systems. You assemble your collection within a points total, perhaps allowing for some unit or option swaps.

This comes at a cost of presenting a 'balanced' game that may bear little resemblance to the asymmetries of historical battles.

Unless one is playing scenarios, the diktats of a 'balanced' game or the need to facilitate 'pick up and play' between acquaintances, makes building an army to a points budget a practical endeavour.

De Bellis Antiquitatis removes all this back and forth by removing the research process and capping the number of units at twelve. The army lists are set for you by the designer. They give a flavour of the troop types found in a given historical army, but they demand that one accepts that the tactical performance of all armies can be adequately represented by twelve units and that particular troop types have a scissors-paper-stone dynamic. Collecting DBA armies is, however, a doddle. Given the fixed parameters established by the designer it is a simple matter selecting the figures one likes the best.

I've never been able to warm to the system but I can see the appeal for those on a budget as well as those gadflies who have little attachment to any particular period and treat variety as the spice of life. I have a narrower interest in the historical battles of the Greek, Hellenistic and Punic Wars, with a remote dream of a Sassanian army some day (but with zero interest in the Byzantines that is some ways off), so DBA is far too diffuse to scratch my itch.

However, one can't dismiss the innovations DBA has delivered to historical wargaming. The army lists have proven very useful for giving a snapshot of what an historical army may have been comprised of. The decision taken by the Wargames Research Group to produce system agnostic reference works such as Duncan Head's Armies of the Macedonian and Punic Wars really makes the derived material useful for any system.

Lost Battles on the surface has some similarities to DBA in that it aims for around 20 units per side. It is avowedly more simulationist and puts a lot of effort into representing actual troop numbers and quality based on the historical record or educated guesswork where the former is missing or lacking. It reconciles its rough unit cap with the representation of actual numbers by making each unit of whatever class - heavy/light veteran/levy infantry/cavalry/etc. - equal in fighting power but each unit type represents a different number of troops of a given morale level.

So in a particular battle a single levy light infantry unit may represent 6,000 troops whilst a single veteran heavy infantry unit may only represent 1,500 troops. This is another way of saying that the fighting power of 6,000 levy light infantry is equal to that of 1,500 veteran heavy infantry, with a number of modifiers weighing in to jazz up combat results.

This has the advantage of paring down components to a reasonable number (20) whilst allowing for greater tactical manoeuvre than DBA's twelve pieces. It does make light infantry much more visually thin than they would otherwise appear on the battlefield, but Lost Battles aims to simulate broadly historical battle outcomes rather than aesthetics.

While Lost Battles 'bakes in' troop numbers and quality into a fairly set number of pieces other systems employ some sort of ratio between the number of units and actual troop numbers and pair this with differential fighting power. This is a fairly intuitive approach but it is one which leaves the gamer-collector the challenge of establishing the appropriate ratio for a given battle (it is more challenging to establish one that works across a campaign), and to set out appropriate statistics and abilities for troops of different types and qualities.

Commands & Colors: Ancients takes a scenario approach. Like DBA, the research process is done for you. The number of units one needs to acquire in order to replicate a given army can be simply derived from the block lists in the rulebooks. All you have to do is decide how you want to represent the blocks that make up a unit.

Use removable stands or hit counters, or some other unique basing solution. You could even just use a figure per block (as is done in Samurai Battles). This was the route I initially took. One doesn't even need to get all the units listed as the block maximums factor in outlier scenarios such as the all cavalry battle between Carthaginians and the Romans at Ticinus. Cutting out such outliers pares the project of conversion from blocks to miniatures to a more reasonable level of hubris; one doesn't really need that many cavalry units.

C&C:A handles troop quality a number of ways. The main approach is to assign different numbers of battle dice to each troop type depending on whether they are light, medium, heavy or something in between. The next level is to open or close certain dice results for certain troops with light infantry having the fewest consequential results. Morale is decided by the dice throwing up a Flag result but modified by the presence of leaders or a supporting battle line. Overall army morale is governed by the Banner system. A most subtle system does it build around dice rolls.

Another subtlety is the use of the apparently amorphous 'Auxilia' troop type that hovers between light and medium infantry. It has some of the combat power of medium infantry (e.g. Republican Roman hastati/principes) but with mobility, morale and missile power of light units. This would seem to model something like a peltast or theurophoroi.

However, it appears puzzling when used on a Republican Roman consular army that only had three infantry types (velites (light infantry),  hastati/principes (medium), and triarii (heavy)). It is generally accepted that Italian allies in the consular armies were equipped and fought in a similar way to the Roman legions. So why have an Auxilia class in the game?

Auxilia in C&C:A becomes a useful way of varying troop quality between scenarios. In some scenarios the allies or even the Roman hastati may be of poorer quality or morale, so the Auxilia classification allows for some finer simulation of historical factors. Until one figures that out it does present a puzzle for a miniatures conversion project for C&C:A.

To the Strongest! caters for both scenario play as well as points so it is a mix of C&C:A and WAB from that perspective. It's grid movement owes a lot to the author's long engagement with C&C:A. Rick Priestley and John Lambshead have recently criticised such systems as being more boardgame than wargame, but I don't see grid movement as such a deal-breaker. What it sacrifices in terms of 'free form' movement it makes up for in terms of time saved, reduced ambiguity, and less fussing over geometry. As for figuring out an army for a scenario one is left to do one's research on the ORBAT. Arguably, research is one of the joys of the historical wargaming hobby. It's a thinkers game on multiple levels.

Hail Caesar is geared for big battle, multi-player scenario play. If you're not using one of the published campaigns you're pretty left with option of doing your research or playing to a points total for pick up games.

Hail Caesar is geared towards the fairly experienced ancient wargamer that knows their period and offers a broad toolbox for recreating historical scenarios. Both HC and TtS! lend themselves to some ratio of representation between historical troop numbers and what one can field on the tabletop. TtS! makes this quite explicit in its discussion of scale.

So if one is collecting an historical army using HC or TtS! there is the task of figuring out actual, or close to actual, troop numbers and breaking that down into units and figures. One can play around with the footprint of particular troop types. Light infantry are often discounted in terms of model numbers in order to reduce the area they cover, especially with figures spaced in open order, though this may come with a possible diminution of their already limited battlefield impact.

Perhaps the best approach to take is to look at the gaming space one has available and plump for a scale ratio that fills the tabletop battlefield nicely - allowing for cavalry manoeuvre on the wings - and match the combined frontage of one's battle line against that.

Two practical table sizes to consider are the six foot wide table and the eight foot wide one. Both HC and TtS! are 'big game' rules pitched at spectacle and multi-player participation, so eight feet wide seems a reasonable place to start. Depth shouldn't be more than six feet since an adult can usually only comfortably reach three feet from the table edge.

In the next post I will consider an ORBAT for Hannibal's army at the Battle of Trebbia, which represents the first pitched battle of his Italian campaign. This should give a nucleus of units around which to firm up a Hannibalic War project.