Sieges

Early versions of DBA offered a simplified campaign option in which sieges could take place. No longer offered in the current version, thus prompted the development of simple campaign system which has been outlined in earlier posts. In one campaign assignment, the storming of a field fortification, as part of a siege had me think of designing s similar system for sieges. The Eighty Years War is filled with such excellent examples of what could take place.  See the link. 

Using 's-Hertogenbosch (1629) as a model, its walls were complete with bastions, ravelins and the routes into the city were protected with forts, all strengthening its defence. Streams feeding into swamps offered further protection, but to the defenders’ surprise, the streams had been diverted to allow the draining of the swamps. This was done by constructing dikes around the entire city. work carried out by peasants hired for the task. A circumvallation of the city protected the Republic’s army from any Spanish relief, and allowed the Republic to move its entrenchments closer and allow artillery batteries to be repositioned. Mining operations succeeded in setting off a massive explosion under a bastion to cause a breach; prompting the military governor to surrender three days later. 

In this example, we have a myriad of small operations that can take place on the game board without requiring massive number of figures or the construction of a walled city. There are last minute supplies required for the city, the storming of outlying forts, sallies by the defenders to disrupt the construction of mills, dikes or entrenchments and the relief column’s attempt to break the siege and more. Before these can be translated into scenarios, we must define certain features of a siege and how the rules can apply or need adjustment.

Siege of 's-Hertogenbosch (1629) – Wiki Common