Monthly Archives: August 2021

Rewriting my Napoleonic rules 3: combat

One of the last club games with my previous rules, in February 2020. I think it is based on Montmirail 1814

While the game structure on my new rules was falling into place, I needed to rethink the combat mechanisms. What I was looking for was both a period feel and something that players could pick up quickly, with the minimum of referring back to tables and the like.

My old system was inherited from Bloody Big Battles, which in turn adopted the Fire and Fury system. There are two types of combat: firing and assault. Fire combat covered both artillery and small arms fire, and is carried out by each side in two phases – first by the passive player after movement (“Defensive Fire”) followed by the active player (“Offensive Fire”). All firing by the relevant side is resolved simultaneously. Fire points are totalled from all sources on each target, two dice are thrown and totalled (or a single D10 for F&F), and the result looked up in a table; there are no dice modifiers, but there are “column shifts” on the table. Assault combat occurs when units are brought into contact, but not resolved until the end of the turn, after firing, which both sides in the assault participate in. The combat is resolved by each side throwing a die (all dice in BBB are six-sided; F&F uses 10-sided dice), and the modified results being compared. One side always breaks off in some form after the combat, if only by three inches.

I have never been comfortable with this system in the big-battle context, and especially without long-range infantry weapons, for which the BBB game is designed. The narrative fits much smaller encounters and much shorter turns – especially the firing. At the big game level firing was more a matter of exchange than one side firing after the other, and the distinction between close combat and short range firing is artificial. Still I stuck to it because it seemed to work, and rewriting it would be a big job. But now I can’t avoid that rewrite, because of what I am doing do with the game mechanism.

This has proved quite long journey, but I have ended up with something that seems to work, but needs more play testing. I have three forms of combat (plus some special rules for pursuits), which I am calling, for now, bombardment, firefight and assault. Bombardment covers artillery fire at longer ranges – over 3in. This fire most closely resembles the old fire system. It can be used by the active player at the start of his turn in a Bombardment Phase, or when he activates the unit; the responding player can fire too during the active player’s turn. Each time a unit fires it picks up a smoke marker; it may not gather more than two of these in a turn. I also limit ammunition to six rounds – though I may yet drop this if it doesn’t have enough impact on play. Most fire creates a fire zone which troops cannot move through in that turn – but not preparatory fire in the opening Bombardment Phase, which is meant to represent a short burst of rapid fire.

All combat is resolved as being one unit to one unit – but I do allow three artillery units to combine fire on a single target, by allowing up to two supporting units for each attack. Fire, like all combat in my new rules, is resolved by both sides throwing a die. In this case the modified throw of the firer must exceed that of the target; more hits are scored for bigger margins. Funnily enough I found that this method can be crafted to exactly replicate the old fire table in its results. Of course it is easier to combine the fire of several units using the fire points and table method – but that is not so important for my system – and having kept modifiers down to a minimum, this method is now very quick and easy. It helps to strip out short-range artillery fire, which is wrapped up into firefight and assault combat.

I seriously considered whether I could combine short range fire and assault combat into a single system, based on the old assault rules. In the old system fire by infantry units was usually fairly ineffective, and certainly quite random; you would be unlikely to use it as a serious way of engaging the enemy on its own. Infantry firing (and short-range artillery) almost always came as an adjunct to assault. It was in the rules simply to add a bit more depth and complexity to the assault, which otherwise could have had too much hanging on the throw of two dice. But then I reflected that in this era (and later ones too) there were two distinct forms of infantry combat. Apart from the classic close assault, meant to displace the enemy, forces might enter a prolonged fire combat, which would wear down the opposition, but was unlikely to yield quick results. This was tempting for armies whose troops’ morale and training made them less effective at the close quarters fighting. This style of combat should not be confused with the exchange of volleys by formed troops within 100 paces of each other – which for my purposes is another version of close combat. Instead it is what Is often referred to in English as “skirmishing”. But a skirmish implies inconsequential exchanges between small numbers of troops., when in fact it typically involved serious numbers of men over a period of time. I have called it “firefight” for want of a better word – “tirailleur combat” might be better, though it often involved more than tirailleurs – it might include artillery, and sometimes troops in more close-packed formations.

Classic wargames rules, including the BBB system, do not handle firefight combat well. They tend to have one side throwing dice to determine losses on the other side, and the other side doing the same with a separate throw, either at the same time or, as in BBB, sequentially. There are two problems. First, specifically to BBB, the fire is often ineffective, so the whole thing is a pretty pointless. In fact such combats on the grand tactical scale (when troops might blast away for half an hour or often longer) almost always had an impact, though casualties might be relatively light (the shooting was often inaccurate and the target dispersed) – because firing a musket repeatedly is physically exhausting and ammunition was not especially abundant; troops low on ammunition often refused to fight, so this was important. Better troops often prevailed because they did not burn through their ammunition so quickly, rather than because their fire was more accurate. The other big problem is that there is much too much random variation between the effects of fire between the two sides. In fact a lot of the myriad variables that are represented by the dice applied pretty much equally to both sides – visibility, range and length of time engaged in particular.

Firefight combat in my game is resolved by both sides throwing a die, as usual, with same menu of modifiers is the same for both sides. Numbers of participating bases is part of the modifier process, and supporting artillery can be brought in. First the number of hits on the active player is determined, by looking at the responding player’s modified score. This is usually one or two hits; the responding player suffers the same number of hits unless the active player’s score is four points more or less than his. That is a little complicated to describe, but it is quick when you get used to it. The result is a bit boring; both sides usually suffer one or two hits. But that is intentional – the combat is meant to be low-risk, but (usually) a drain on both sides. Of course if one side masses lots of modifiers, the outcome will not be so even.

The mechanism for assault combat is nominally similar to the old one. The result (usually) depends on the difference between the two sides’ scores, but in this one side is forced o disengage. I wanted to do away with the results table, and have a set of simple outcome rules that would replace it, which would be able to handle the differences between infantry, cavalry and artillery. I also wanted to keep dice modifiers to a minimum. One of the complexities of the old system is that of conferring advantage for numerical superiority, which involves counting bases. There is also an advantage for sides in deeper deployments, as well as the a two point advantage for flank attacks, though these were quite strictly defined. Now that combat is reduced to one-to-one encounters between single units, I had the opportunity to rethink this. I took the view that the outcome of this sort of combat was primarily about momentum. Numerical advantage conferred staying power but not much else. This simplifies things dramatically. The modifiers for numerical advantage and deep formations disappear. This is not quite accurate. If a unit had more men, and its opponent had an open flank, it did have the possibility of using its superiority to tactical advantage. I also suspect that there are differences for units that deployed extended or in depth. But it is hard to reflect these ideas without the rules become too fiddly – so I’m keeping it simple for now. I have retained the flank attack modifier, but split it between a +1 for the attacker and -1 for the defender, with a lower threshold for the former.

I have also added outcomes that reflect the absolute size of each side’s score before combat is joined. If the attacker fails to get a positive score, the attack baulks, and the defender is not engaged. If the attacker fails to get a score of 4, then the attack stalls – if the attacker is infantry, then the attack converts to a firefight; if it is cavalry, the attack does not proceed, but the target unit is pinned, which may limit its options in the next turn. On the defence side, if the assault proceeds and the defender fails to achieve a positive score it routs without combat. The 4 threshold for an attack to progress as an assault is a high one – I want to use the same set of thresholds on all my resolution procedures (i.e. 1, 4 and 7) to make them easier to remember. In fact I think it was quite hard to make troops conduct a full-blooded assault.

That’s just an overview. I am quite pleased with the overall design – the process is simple, and yet it yields a wide range of historically plausible outcomes. Whether it achieves my aim of packing more decisive action into each turn is another matter. I have this habit of providing with one hand and taking way with the other.

So that is far as I am going to describe the rules for now. I am pleased that the length of the them has actually been reduced from 14 pages to 13; it was running at 12 until the last series of tweaks. (The text is quite dense and there are no pictures…). I will only know how well they work after further play testing. Until this testing is done I won’t post up on the website. If any reader is interested in reading them before then please contact me in comments.

Rewriting my Napoleonic rules 2: game structure

Another view of my Plancenoit trial game

In Part 1 I described how I settled on a game based on divisional units with a game turn representing one hour (or more – I will return to this). I described the journey that led to that conclusion. If that was clear before I started the project, the game structure – the basic framework for the two sides to interact – certainly wasn’t.

It is worth explaining a bit more on the representation of the armies. I started with the Bloody Big Battles system where troops are represented by bases, in my case 25mm square, though I have also acquired some on 30mm squares. I mount these with six figures for infantry and two for cavalry, as I like my miniatures to be more densely packed than the modern fashion, though still looser than actual close order formations, where you would get four rather than three infantry figures across 25mm in 18mm scale. In BBB each base represents 1,000 to 1,500 men for both infantry and cavalry, meaning that each of the figures would stand for 167 to 250 infantry, or 500 to 750 cavalry. Artillery bases represent 30 or more guns. I kept the infantry scaling but I felt this did not do justice to Napoleonic cavalry; I base these at the same figure ratio as the infantry, which means 333 to 500 men per base. I wanted more cavalry on the tabletop, and besides they did take up more space than infantry. Cavalry did not deploy dismounted and engage in fire combat in this era, so that was a complication I did not need to think about. I also halved the artillery ratio – though I adjusted the fire factors to reflect this. While the high artillery ratio in BBB worked better than I thought it would, each base is still an awful lot of hardware, when artillery was not always massed together. Each artillery base is 12 to 18 guns.

The elapsed time that each game turn represents needed a bit of thought. Other large scale games, such as Et Sans Resultât and the 1870 series use 30 minutes, as I did in the brigade-based rules that I used for my Vitoria game. But this creates too many moves for a game, even in a fast-playing system. Also a longer turn length is one way of simulating the communication delays in these large scale encounters. It takes longer to react to your opponents’ moves. A one hour turn is the logical next step – and it is what BBB is based on nominally (and Volley and Bayonet). But one-hour turns are not the only option. You can go for a two hour turn, but with a more complex interactive system for sub-moves within this. This is what Grande Armée did and another old system – Legacy of Glory – that I bought in the 1990s, but never played properly. I actually designed a system based on this idea with a rather interesting interactive system of sub moves. I may yet bring this into the light of day, but I was worried about the complexity of it.

Somehow I needed to pack a bit more action into the move, and especially combat action, while maintaining simplicity. I gradually realised that I had to rethink the turn structure. Like BBB I was using the Fire and Fury system. This was innovative for its time. Prior to that the fashion was for an alternate move system, where each player took turns to go through all their armies, with phases for movement, firing, mêlée, morale an so forth. Or (how my games started) with a simultaneous move system based on written orders. F&F retains the alternating structure, with each player taking it in turns to be the active player. But the passive player gets a firing phase directly after the active player moves, and before the active player fires or mêlées. This creates a very interesting dynamic, but firing and mêlée is done on a whole army basis, with complex interactions possible between several units on each side. Two units can gang up on one. This is one of the things that makes the writing of traditional rules so complicated.

Then I had a lightbulb moment as I was reading about innovations in modern fantasy games, less tied to notions of realism. In one system all actions are one on one; there were no multiple combats. If two units were to gang up one one it had to be done sequentially. This means that a player can pick a unit and go through the whole action sequence, including combat, before moving on to the next. In systems terms this is much simpler than the traditional wargames approach – indeed this is how computers tend to do things, in my rather limited experience. It then hit me that this could work for Napoleonic warfare for divisional level units. It was impossible to coordinate divisions closely, and it rarely happened. There was something sequential about how they moved and entered combat. On the few occasions where more than one division operated closely with another (I could think of two examples – McDonald at Wagram and the French main attack at Albuera) the divisions became entangled and in effect merged into a single tactical entity. The sequential approach could be adopted for my game – though artillery would be a complication.

So now a player picks a unit, activates it and goes through the complete sequence. This includes allowing it to carry out more than one attack per turn. The old Movement Throw (a combined movement randomisation and morale test which is a central feature of the F&F system) stays (now called Activation) and gives the unit zero to three actions (and can cause a battered unit to retreat). Each action can be used for movement, rallying or an attack. The player also has an opportunity to focus command resources on particular units to improve their activation result – allowing players to manage the risk of being slowed down by bad dice throws – one of the issues/features (depending on your point of view) of the F&F system.

This approach opens up the whole turn sequence. It is now possible, as it is with many modern wargames systems, for the I-go/U-go sequence to be broken down, with moves from both sides being mixed up. Here I decided to be more cautious. I quite like the idea of a player surveying the scene, deciding what he is going to do, and then trying to do it -rather then everything being lost in an interactive muddle. The typical narrative of a Napoleonic big battle does seem to work this way, with each side moving into action or response across the whole field. I also worried that a more mixed up sequence would take longer to play out. So I left the basic idea of alternating active and passive phases for each player, but allowing the passive player more opportunities to respond (e.g. opportunity charges or turning to face a flank).

Artillery does not work this way though. In some cases I allow it to tag along with other units, but I also have a Bombardment phase when all the active side’s artillery can fire together, either in a quick burst of preparatory fire – or in a longer cannonade of up to an hour. The passive player’s artillery can also fire at any unit it can while it is moving. Artillery differs in many ways from other troop types – not least in that the noise and smoke means that the whole field knows if it is in action, so the same command and control issues don’t apply.

This is all very clever, but it brings with it some problems. The most obvious is that of sequential attacks. This could be very advantageous to the active player. The first attack will almost inevitably disrupt the defender, making it more vulnerable to further attacks, before it has any chance to respond. This is harder in practice than in theory – because the attacking unit tends to block other attackers. But it does bring to light a more fundamental problem – that while each unit is operating in its own time and space on the table, in reality other units on both sides are using that time and space too. If a unit has been fighting multiple rounds of combat while passive, won’t that reduce what it is able to accomplish when it becomes active?

All sequential move systems run into with some variation of the time problem. That is why simultaneous systems were so popular in the early days with gamers who wanted to move from games with toy soldiers to historical simulation. Still, a couple of ideas can help smooth things over. First is overlapping time. So if side A’s turn is 10am to 11am, side B’s might be 10.30am to 11.30. So each side spends part of its turn responding to the other player, and part setting the pace. Another idea is slack: the furthest a unit can move in my rules in one turn, across good terrain but not along roads, is 18in or 2.7 km in real space (1.7 miles). This is slow going, meaning that more action can be packed into that turn without it getting out of hand. A third idea is that the game turn is not strictly tied to the clock – an hour (or whatever) is only meant to be an average. Sam Mustafa is a particular exemplar of this line. He avoids tying his game turns down to particular time periods, and he has a similar flexibility towards space. This is too much for me – I like to have a clear crossover narrative from what is happening on the table to what might get recounted in a history book. That means creating reference points: naming the geographical points on the table, the units and commanders, and so on; the clock is an important such reference point, albeit on a rather approximated basis – this is before the age of precision timetables. As the game clock reaches 6pm I like to image the evening sun. You don’t get that from a system that just tells you it is Turn 12.

Using such reasoning I simply created rules to stop more obvious problems: limiting the number of attacks on any one unit to three for example. These were the rules we used for the Sorauren game. These worked OK, and we encountered only one clear problem on the time and motion side. One of the French brigades advanced into the field of fire of a newly-moved British artillery unit. This unit was able to give it the full hour-long cannonade before it had any chance to adjust its position – which was in fact enough to knock the unit off the table, coming on top of earlier wear and tear. As the French player I could have been warier and spotted the danger, but it still didn’t feel right.

That problem doesn’t require a big fix, even if it means another fiddly little rule of the sort I have been trying to avoid to keep things simple. But the time problem still nagged me. The idea that you would attack an enemy unit with the primary aim of pinning it down is certainly relevant to this era, but the ability to do so in this rule system is limited. Before Sorauren I tried out a simple scenario based on Bulow’s advance on Plancenoit at Waterloo, which I ran twice. This is quite an interesting time and motion problem. Loyal readers of this blog will know that I puzzle at the speed with which the Prussians were able to reach the village, in spite of the supposedly hard and skilful resistance of two French divisions and two kilometres of ground to cover. In this trial there was no issue. In move one (about 4pm) the Prussians went in hard against Lobau’s corps, with two rounds of combat. When it came to the French turn (on both trial games) they decided to fall back on Plancenoit in case their line was turned or broken in the next round, threatening the whole corps. They had plenty of opportunity to do so. Apart from needing to rally if they wanted to fall back in good order (problem that the pursuing + would also have to face) the effect of the first turn’s heavy fighting did not limit them. One hour (or one and a half) would cover both the heavy combat and the 2km withdrawal. This the point at which the photo above was taken. So in this game the Prussians attacked the French in turn 1 and engaged in two rounds of combat; the French withdrew in their turn. In turn 2 both sides reorganised. In turn 3 (6pm) the Prussians (in the one game I played that far), the Prussians attacked the village. This is not a bad tracking of historical events, but it still didn’t feel right.

I wanted to address this problem. In my new (and untested) version of the rules each attack on an enemy unit causes it to gain a “pin” marker. Pins are also picked up picked up for response moves, such as opportunity charges, evades, or turning to the flank. Similarly responding artillery gets a smoke marker each time it fires. When it comes to the next turn, when the responding player turns active, these pins (and smoke markers) need to be cleared before the unit can move. So if the unit activated with two moves, it might have to use one to clear a pin marker, before using the next to rally or attack. However this rule could get out of hand, so the rule is that the first pin is cleared for free; only if a unit picks up two or three pins will it cost them a move (or two). I rationalised this on the basis of overlapping time and making use of slack. We will see how it plays out – but it could have a significant influence on play. I have two slight worries – that it will confer too much of a first mover advantage on attackers by not giving the defenders enough space to recover; and that it will slow things down again, after all that effort to put more action into a turn.

We will see how that works. Meanwhile I am pleased to find that the new turn structure has led to simpler rules. Next time I will describe how I handle combat.

Rewriting my Napoleonic rules part 1 – scope

The Prussians drive the French back into a rather Mediterranean-looking Plancenoit in my trial game

After a spate of painting this spring and early summer, my energies turned to rule-writing. It proved a much longer and harder road than I expected. But the end result might be very close to my final “Dining Table Napoleon” product. Or it might yet collapse into a heap of broken pieces. I want to take this opportunity explore the choices I had to make and the solutions I have come up with.

But first: what is the game for? As the blurb on my blog suggests, I want to fight big Napoleonic battles. Wagram and Leipzig might be a stretch, but a medium-sized encounter of 30,000-50,000 a side should count as a relatively small game, and a Waterloo (with about 70,000 a side plus 40,000 Prussians) should be quite possible to handle with two players (plus one for the Prussians) on a moderately-sized table. I want to use my 15-18mm figures (while catering for smaller ones) and I also want rules that will be quite easy to pick up and play for occasional players. I want to recreate the ebb and flow of a Napoleonic battle reasonably faithfully, so that game outcomes are historically plausible, and historical outcomes within the bounds of the game’s possibilities. But the game needs to evolve reasonably quickly, with a turn representing about an hour of action.

If that sounds straightforward, we are left with the puzzle of why so few games systems take this on. Only one mainstream system that I know of does: Sam Mustafa’s Blücher. This is a clever system with a lot of interesting features. I played three games with it at the club with my French and Prussians, and the experience was decidedly unsatisfactory. Why? A lot of it was visual. In order to make it fit the table sizes I wanted meant having two bases to a unit, giving 12 infantry figures and four cavalry. This didn’t look right, for reasons that I find hard to pin down – but my fellow club members thought so too. Too few men to a unit? It would have looked better with 10mm or 6mm figures (or bigger bases and a fuller ground scale). Certainly that was true of the cavalry. I also didn’t like uniformity of the unit sizes in this context (as opposed to a smaller game). Other aspects of the rules failed to float my boat too. The rules on built-up areas felt entirely wrong – they became fortresses against which attacking units were dashed in vain, rather than stages for gory and confused fighting that was costly to both sides with frequent changes of fortune. Leaders are not generally represented, and neither is the divisional level of organisation – all for very good games-design reasons, but which spoiled the historical narrative for me. The rules did not handle the Prussians very well. They are a pretty boring army in terms of classic gaming features (elite units, heavy cavalry and so on), while their flexible battlefield organisation, where the battalions from different regiments were mixed up in task groups, did not lend itself to a system where the basic unit is a regiment or small brigade.

So I let Blücher go. In fact I thought that brigade-sized units were not the route to go. This is really the minimum-sized unit for big battle games, unless you have big tables and many players. This is the reason why so few rule systems don’t fit the scope I am looking for. For many players, representing battalions is the essence of Napoleonic wargaming, with classic decisions about line, column and square. I have even read some rather implausible arguments that numbers of battalions determined the effective size and capability of armies more than numbers of men (in fact generals of the time tended to measure army and corps strengths in 1,000s rather than battalions). But even if you reduce battalions to a relatively vestigial role (such as in the very interesting Et Sans Resultât rules) you find you find that a single player can’t control more than a corps. If you want to play with battalions, that is fair enough – but it annoys me when any such battalion-based system claims that it is for big battles, which is often the case. Smaller battles (20,000 or less per side) were quite rare historically, so you are left with refighting a corner of a bigger battle. Or fictional encounters between two corps or reinforced divisions – which, to be fair, can make fun game. With the modern preference for games between smaller forces chosen from army lists, it is not surprising that most Napoloenic rules are based on battalions.

Old school wargamers in the 1970s simply fudged things by scaling down, with each battalion representing a brigade or division, and the table being scaled to fit the battle. But in due course proper brigade-based games were created. I investigated three systems in particular. The first was Volley and Bayonet by Frank Chadwick and Greg Novak, published in 1994. In this system units were represented by square (or sometimes oblong) bases with a standard 3in frontage. The system covered the whole era from the Seven Years War to the Franco-Prussian War. I never played it. The table sizes required for 3in bases was large, and at the time I had few gaming opportunities. But the stripped down nature of the system was inspiring. They also published a very useful scenario book for the 1809 campaign. Next came Age of Eagles. This is based on the ACW Fire and Fury system, a revolutionary set of rules published in the 1990s. Age of Eagles is based on deep historical knowledge, but it is not a stripped down system. The units might be brigades, but they are made up of multiple bases, and perform battalion-like evolutions. I played them once (a recreation of Quatre Bras), but let it go after that. In my view it ia player per corps game – and if you are going down that route I would prefer the vestigial battalions route of ESR. And thirdly there was Sam Mustafa’s Grande Armée and its fast-play derivative. Sam is for my money the best games designer out there, and it showed with this system. Like V+B, its units were brigade represented by squares. The system was based on 3in squares (which gave me a space problem) but I followed the recommended option of 2in squares with special rulers marked in 2/3 inches. This was the system I settled on for many years, using the fast play version with house rules. But a number of features were unsatisfactory, both from a visual point of view, and as a historical representation. Sam moved on and the system gradually became ossified.

This brings me to the 2010s and where I started this blog. I wanted to write my own system. I was focusing on a project to refight Vitoria on its bicentenary. This was definitely a brigade-based battle, and so I keep the brigade-based system using 30-minute moves. These rules are quite clever and innovative (they used playing cards in place of most dice), and they are published on this blog. But Vitoria took all day with four players, though my fellow players were very kind about the rules. Incidentally we did not use my miniatures for this, but my friends 6mm GA bases. This left me the conclusion that I must move forwards to division-based games and one-hour turns.

Divisional-based games do produce headaches, especially for Peninsular War battles, as my Sorauren game showed. But I did have an interesting place to start: Chris Pringle’s Bloody Big Battles. This is not a mainstream commercial system like Blücher with well-produced booklets and player-aids. But it is very well designed and comes with a host of big battle scenarios. The system is based on Fire and Fury, again – but unlike AoE it is properly stripped down. But the big problem is that it is primarily designed for the Franco-Prussian War, and then extended to other campaigns of that era. Small arms ranges were much greater in relation to move distances. But quite a few people used them for Napoleonic games, and so I started out on that path. What worked especially well for me was the way units are built – on variable numbers of bases, based on unit size. I found that this got me much closer to the look I sought than the standard brigade blocks – though trying to use 15mm figures on such a reduced distance scale (1in to 150m) is always going to be a visual challenge.

By this time my journey is well-documented on this blog. At last I was getting regular games as a club member – and the system proved suitable for that. But it was slow going by historical standards, and the cavalry rules did not have the Napoleonic feel. The latter was mainly dealt with when I rewrote them into Big Napoleonic Battles V0, published here, which became our settled rules for club games. But then lockdown hit and I moved away from the club. This year I started to think hard about how to rewrite the rules to address their less satisfactory aspects – notably that a game turn packed less than an hour of action, and so games were going on for too long.

But in a phenomenon that will be very familiar to rules writers, what started as a few tweaks turned into a full-on rewrite and rebalance. To be continued.

Sorauren 1813

The game at start of play from the French lines. The great hill is in the centre, and you can see my representation of the col, defended by a Portuguese unit. n the far right Pack’s division advances.

At last! My first proper live game in 14 months. My friend Rob came over with his Minifigs of British and Portuguese (with some Brunswickers taking the pace of Spanish) to take on my French army. We always base our games on a historical battle, and this time I chose the battle of Sorauren on 28 July 1813.

This is a medium-sized battle with about 30,000 men a side that is very neglected by historians and gamers. Historians seem to lose interest in the Peninsula War (and its appendix in the south of France) after Vitoria in June 1813. To them this was the decisive battle, and everything afterwards was a side show. But in fact there was plenty of drama, and not least in this battle, which is bigger than many earlier battles – comparable in scale of engaged forces to Busaco in 1810, and bigger than Albuera in 1811. This neglect means that there is little information available on the battle. I tried Googling for wargames scenarios and I got back practically nothing – a few games which revealed little historical research. I didn’t have much time to put the scenario together, so mine too suffered inaccuracies. But researching battles is one of the joys of the hobby for me. Even as an amateur historian you can always add a bit of value to received wisdom with just a little careful research and asking the sorts of difficult questions warmers must resolve but historians can gloss over.

So the background: after Vitoria (incidentally my biggest wargaming project and the starting point of this blog – my maps now come top of a Google search!), the French rapidly evacuated Spain outside Catalonia (another neglected wargaming topic, for another day), leaving garrisons in the fortresses of San Sebastian and Pamplona. Napoleon gave command of the defeated French forces to Nicholas Soult, who reorganised and reinvigorated them with the sort of speed that so often caught France’s opponent’s off guard. He counterattacked, seeing that the allied forces were dispersed. To cut the story short, he massed two corps, those of Clausel and Reille, a few miles from Pamplona after storming through the Pyrenean passes, brushing aside British forces at Roncevalles. The first French forces, Clausel’s corps, arrived on 27 July, but these were not enough to take on the allied forces there, based on the British divisions of Picton and Cole and the Spanish ones of McDonnell (conducting the siege) and Morillo. Reille eventually arrived, but too late to be mobilised fully that day. Soult himself was their together with army level reserves of cavalry and artillery. Also arriving on 27 July was Wellington, who, seeing the threat, immediately summoned reinforcements, of which Pack’s division was the only force within a day’s march. The great man’s presence greatly reassured the allied forces.

I didn’t have much time to research the battle; I was hoping to find something readily available that I could use, notwithstanding imperfections. My first port of call was a booklet by Terence Wise that I had bought for £1.50 in 1977. This was part of the Battles for Wargamers series published by Bellona – I also have the booklet from the same author for Tunisia 1943. The Peninsular War booklet covered the series of battles after Vitoria – mainly Soult’s offensive and Wellington’s counterattack, but also covering Suchet in Catalonia. A nice idea, but the battle map was highly inaccurate (including quite the wrong ground scale) and the narrative was suspect. I went back to good old Oman as my main source. Oman makes mistakes, and he can be irritating in his period way – launching into criticism of the decisions of officers at the time, rather than making much attempt to understand why they took them. But it is proper history, and reasonably transparent about its sources. He also surveyed the ground. Alas few modern authors do this and are more interested in painting a dramatic picture which fits into a broader narrative about the Peninsular War. The only other account I read was that in Lipscombe’s Peninsular War Atlas. This was pretty superficial too. The map is a pretty decent one, though the British forces are depicted as being far too far forward. It does provide additional details on the Spanish, though.

And what about rules? My big wargames project for the last month has been a rewrite of my Big Napoleonic Battles rules to get to a “Version 1”, so succeed my “Version 0” which we used successfully at the club, but which I felt wasn’t right for historical refights. This was a classic case of one idea leading to another, which turned into a radical rewrite, about will I will write separately. I had carried out some small scale trials, simulating the Prussian advance on Plancenoit at Waterloo. but Ithe opportunity of something bigger was too good to miss. These are big battle rules, with divisions being the principal unit – so not all that well suited to the Peninsular War, were the big battles were large fought between brigades of around 2,000 men (as well as Wellington’s habit of deploying individual battalions). The battle is too big for rules based on battalion units (still by far the most popular format) – but one based on brigades, such as Blucher, would have been a more natural choice. That would have been a bigger game though. I would like to find some way of making my big battle rules work in the Peninsula, as a number of battles there could make very good smaller games; so I tried to adapt as best I could.

The most difficult thing about refighting this battle is the terrain. I am a big believer that terrain dictates the course of battles, and that even small details matter. It puzzles me that many historical wargamers seem to take a lax attitude to it – though getting it right is undoubtedly hard work. Which isn’t to say you can’t achieve this with a greatly simplified presentation, just that this requires an understanding of which features were critical. Sorauren was fought over terrain dominated by steep hills. This is tricky for wargamers at the best of time. I didn’t have time to do more than a rushed job of taping some 1in chunks of styrene to the table (in two contour layers) and a couple of thinner bits for lower hills, and throwing my green felt cloth over it. This was completed using paper tape for roads and rivers (painted over with tempera paint) and scattering some buildings and bridges on it. You can see the result in the picture, and its not very pretty. With such steep and complicated hills the time-honoured method of using cloth over formers is problematic. I used map pins, but rumples in the cloth are everywhere.

The central feature of the battle is a large hill referred to by Oman as the Heights of Oricain, but otherwise un-named on the maps, which rises to about 200m above the plain. Wise referred to it as “Cole’s Ridge” – but it isn’t ridge-shaped. This is rather typical of the way historians have tried to bend this battle into the shape of a classic Peninsula reverse slope encounter that historians try to do for all Wellington’s defensive battles. In several important respects I got the terrain wrong, as a close examination of Google Earth revealed afterwards, and these do much to explain some of the deviations of the game from history. If I do this again, I will use more contours, as this is a better way of dealing with many of the important complexities. For most battles two contours is more than enough, but alas not here.

I am also left with the challenge of how to improve the visual appearance of the table. One thing I had in hand is to use a different cloth, or battle mat. The day after the game a new fleece mat from Geek Villain arrived, in their Sicily pattern, designed to represent arid terrain. I had a chance to see how it worked over the formers, though I did not try the pins.

A lot of the same problems emerged as for the felt, as can be seen from the rumples, but the material does fall more easily over the shapes, and the colours are much better. My bête-noire is the over-use of saturated colours in wargames products (like my felt mat) – and this product does not fall into that particular trap. The big question is whether I create the hills to sit on top of the mat, using paint and flock as best as possible to blend in. A point to ponder. Other questions are whether I manufacture lengths of roads and streams to look a bit better than the painted tape – perhaps using caulk. On Google Earth the watercourses are marked by vegetation along their banks, and this may well have been the case at the time – replicating this make make them too wide though.

There does not seem to be too much doubt about the forces involved, fortunately. The only doubt I had concerned the French cavalry. The maps (I also have Fortescue’s – but not his text) show that the French deployed cavalry from Pierre Soult’s division – which did engage with the British hussars on the day, having deployed to the far left of the French positions, alongside Foy’s division of Reille’s corps. P. Soult’s division was in fact a very large cavalry formation, especially by Peninsular standards, with nearly 4,000 men. It is highly unlikely that all of it picked its way across the difficult hill paths to reach the positions shown on the battle maps. I divided this unit into three, and placed one of the sub units with Foy, with the rest backed up along the mountain pass with the artillery. To represent the forces on the table I dropped the normal ratio of 1,250 infantry (or 400 cavalry) to a base to 1,000 (or 333 cavalry), and limited the maximum unit size to four bases rather than six. This reflects the terrain which made it hard for large formations to operate cohesively, as well as the relatively small numbers of the forces involved. Using this system for the French was quite straightforward – each unit was a small division or large brigade. The British infantry divisions were another matter. They typically had 6,000 men organised into three brigades, one of which was Portuguese. The whole division is too big to be a single unit; the brigades are too small. I allowed two units per division, the second unit being Portuguese for Pack and British for Picton. Cole’s division was another matter, as it was reinforced by additional British and Portuguese British brigades, and a couple of Spanish battalions. I represented this formation as four three base units, two British, and one each Portuguese and Spanish.

For the game I chose to start it at midday, an hour before Soult planned to launch his attack, but when the French spotted Pack’s arrival and Clausel responded. In fact I had Pack too far back historically (or I should have started with the British moving first). The objective was for the French to break through to the far side of the table and relieve Pamplona; the game was six turns long. Playing the French, I got nowhere close to this objective, though not radically far from the historical positions. On the their right, the French benefited from Pack’s late arrival, which was compounded by the British component of this formation grinding to a halt due to poor activation throws. The Portuguese took the brunt and the unit was eventually eliminated. But Rob brought forward McDonnell’s Spanish division, which was more than able to to contain the remaining threat. On the French left, Rob could not resist the temptation to use his considerable body of cavalry (which included two fine units of heavies, not actually used on the day), to push forward up the valley. This brought out all of the French cavalry, and I also pushed forward Foy’s infantry. This was eventually reduced to a stalemate, with the French infantry rather battered. Rob then started to move his infantry to the centre to contain the French threat there. Subsequent research showed that this highly unhistorical course of events was shaped by errors in my terrain layout – the river valley was too narrow to take such troop movements while the main heights were being contested. The front of Picton’s position was also more difficult terrain, with a steep slope and a river bed – which would have limited the movement of cavalry.

The main battle was in the centre, as the French tried to take the hill. Cole’s four units looked distinctly vulnerable as they could barely cover the front, against the six French units, some of which were large four-base ones, notwithstanding the steep slopes. It didn’t help I forgot that the British units had a discipline bonus (allowing them to recover more easily from disruption). But once Rob had brought forward the British unit in reserve (Byng’s brigade), the slope was enough to keep the French contained on the British left, while the Portuguese holding the famous col in the centre (inasmuch as anything in this battle is famous) where the slope was not steep, also held their own. But that left two French units to gang up on the Spaniards on the British right. These were pushed back and French breakthrough beckoned. I saw an opportunity to push through to Pamplona; Rob was worried that the French units would turn to take his other units in the rear, where his reserves had been committed. He brought forward Murillo’s Spanish division, which contained the threat to Pamplona.

And there the game concluded. The French objective is pretty much impossible to reach. Even if the battle on the hill had gone better, there was not enough time to get to the other side of the table, especially as there was likely to be some form of last line of defence. It would perhaps have been better to either focus the game on the hill, or perhaps leave a path to victory for the French in destroying a substantial part of the allied army. Not that I had nailed the battle particularly well; I devoted too much strength to the centre, and could easily have deployed an extra unit to the right after the good initial progress there.

Here’s how the game looked at the end:

As the evening approached at the end. Foy’s division on the far left is looking battered, but the French have made good progress on the left of the hill.

It was very good to have a proper live game at last. But it has left me with plenty of food for thought, about the scenario, the appearance of my games, and the rules.