There has been a some discussion in the DBR world for a few months on issues, or perceived issues, in the rules. One such issue is the impact of baggage on games. From a game perspective I believe that some of the issues are being addressed in ways that are not always elegant or may provide unforeseen issues. So what is the issue?
Basically, there is concern that the baggage rules, as they stand, allow baggage to allocated to bolster a commands break point to a level that a command can not be broken, at least by casualties inflicted on fighting stands alone. I agree that this is unrealistic and is an issue. I would like to see this changed. I however differ from some in how this should be addressed. I am particularly cautious of a proliferation of ad hoc amendments.
Over recent months there have been a couple of tournament specific attempts to address baggage. In my view they are either complex, create further issues, or fail to focus on the Renaissance battlefield. They adopt selected DBMM mechanics which I believe are not ideally suited to the current version of DBR. One of the current ideas is to divide the baggage between the commands. In my view the DBMM “variants” miss the point in several areas, one of which they take only part of the DBMM rules, ignoring others.
In standard DBR baggage bolsters one command and allied contingents, both of which I believe are flawed. I think it a mistake to try and fix one and ignore another. Unfortunately, the DBMM “variant” currently being used in some DBR competitions extends this bolstering to all commands, irrespective of size. This is in contrast to DBMM, which is sensibly formed. Some of the most obvious points of DBMM are that it introduces a tactical factor reduction at 1/4 loss, rather than DBR’s 1/3. DBMM also reduces a baggage elements ME value. Both limit the bloated command affect. So what are some of the ways to address the impact that baggage has on games?
Before defining possible solutions here are a couple of additional thoughts, the first an excerpt by the English Civil War commander George Monck in his “Observations upon Military and Political Affairs”…
“There is nothing that bringeth so much disorder to an Army upon the March as the Baggage; and therefore it is highly necessary to reduce it to the smallest proportion that may be.”
It’s interesting that while Monck advises to limit the baggage while wargamers, especially those attending competitions, start with baggage to maximise their army composition. Perhaps something is wrong?
Now, to some gaming specifics. Let’s start with a look at figure scales. DBR has a figure scale where a stand represents between 50 and 100 men, depending on the stand type. Typically an English Civil War army with 400 points represents around 3500 to 4500 men depending on the various troops selected. These typically have some six stands of baggage. Interestingly, some non Civil War armies have allied contingents of only a few stands. There are examples of allied contingents with five or so stands of light horse. As each stand represents 50 men, or 250 men in total, how realistic are such small commands become unbreakable when baggage is added? Even more typical allied contingents, let’s consider English Royalists supporting Scots Engagers, can be bulked out effectively making them more resilient than other commands. This seems equally suspect.
By way of contrast DBMM allows baggage association only if certain ME of fighting troops are available, this counters the small allied contingent. Something could be added to DBR to cover these small commands, but given the low number of figures a stand in DBR represents I wonder if another solution exists?
As you may know my main period of interest is the English Civil War. There are a number of Civil War battles where one or both armies fielding horse only, or horse supported by commanded shot. In these situations they travelled relatively light and unencumbered. This style of action can be represented in DBR now, and rather well. You may recall that armies without baggage have a notable advantage in the deployment process. In my opinion this should be retained. I’m therefore not of the view that all armies should have free baggage.
Interestingly, in very large battles baggage where baggage existed it could well be some distance from the deployed armies, at Edgehill a good mile from the Parliamentarian troops. Edgehill and Naesby also provide good examples of Royalist cavalry being “lost” to the battle pursuing routers and raiding baggage to the detriment of their own side than that of Parliament. Not having baggage on table helps represent this rather well.
So what does baggage represent in DBR? It models the concept of an army being a little more determined to hold the field rather than abandon their loot, despite George Monck’s advise to commanders. I do not believe however that such baggage should bolster any individual command be that the largest foot command, an allied contingent or all commands in general.
Yet I’m not keen for it to be free, where its loss demoralises an army rather than adding to it, simply becasue small armies often travelled without it or it was some distance from the battleield. Indeed we must be careful, when using points budgets, that the a balance exists between points cost and benefit. Currently the benefit is clearly too great for the cost as most players wish to use baggage.
What DBR does model reasonably well is the situation where a well formed reserve can be steadied, has a degree of resilience and can we’ll continue to operate even once the command is beaten. This is well defined in DBR with a nominal break of 1/3. If we maintain this trigger value point value, without increasing any commands breakpoint, what are our options?
I would suggest that all army baggage, irrespective of its source be deployed as one group. It does not count towards the break of any command but rather only contributes to the army breakpoint. It seems sensible to have it deployed behind the largest foot command. If it is to be moved then PIPs must be allocated from the CinC’s command. This requires no change to the ME equivalents or points cost, while at the same stage addresses the bloated command syndrome of any command, including allied commands.
I’m sure if a new version of DBR is developed other solutions will be thrashed out, but in the meantime perhaps this would provide a useful method of resolving a perplexing challenge. That said it is yet another amendment and I believe there are inherient risks with such amendments. Further, does it address the points cost for benefit equation? To be honest I’m not sure. Players can not help themselves construct a perfectly balanced army when real commanders were forced to struggle with what they could assemble.