View Full Version : My Campaign Modifications

04-21-2004, 06:32 AM
After sending these to Hammurabi following the discussions on seiges I thought I'd share my modifications to campaign rules with the rest of the forum.

Aside from the two tourmanents I run in May and November, almost all of my DBA is played as part of long running campaigns. The club group is sets up at the beginning of the year and we play using the strategic movement nodes drawn onto an outline map of the area, so it ceases to be cyclical like the map in the rulebook. Some of you might have seen the map and read the account of the campaign we called 'Unfurl the Landwaster' back in 2002. Most of the maps aren't that pretty I'm afraid.

As new players show an interest in joining, we add extra countries to the map. The upper limit is 13 players, after that I run out of different coloured pins. At the end of each session we take notes on the location and status of each army and pick up again at the next session.

I have made some minor tweaks to the rules based mostly on personal preference, gut feeling and so forth.

I. The loss of a General, Camp or BUA does not cause the loss of two more elements after the battle. For every battle lost because the general was the first to die, there are two or three where the general was the fourth element to be killed. The loser is then down 6 elements and if the intention is to generate battles then they will not be encouraged at this point.

II. The loss of a camp does not impact on the battle at all, taking the camp gives 2 prestige to the commander that captures it, but does not affect the battle. It costs 1 more PIP to move the element that captured the camp out again (looting!). This is because I have strong feelings about the effect of camps in wargames. I recently wrote an article on this for publication in 'Broadsword' - an Australian wargames magazine.

III. At the end of each year there is prestige awarded for each recruitment point not used ie Player A has 5 cities, allowing for a maximum of 6 elements to be recruited. If they only have 4 losses then they are awarded 2 prestige. There is also an award of 1 prestige for each vassal a player controls.

IV. If a player elects to stand seige with their army inside the city then the besieger is also at risk, if they roll a 1 then they lose 1 dice worth of elements up to a maximum of the size of the besieged force + 1.

V. A BUA on the battlefield does not represent the city. This stops the need to explain the facts that a) the BUA will only allow 1 element inside, but the city can take any number of armies, and b) where the invader loses the battle but captures the BUA and so the city. (It has happened).

VI. When a city is already under seige and a relief force is sent, either by an ally of the besieged, or by the besieged themselves, (as opposed to the initial attack where the defender moves up to give battle, the besieger counts as the defender for the purposes of tactical deployement, but counts as the attacker for the strategic purposes of who can send an allied contingent to the battle.

VII. Goodie Cards - originally designed for a v1.0 Asian campaign where the generic 'Chinese Border Nomad' were very lightweight. The CBN recieved one card each year, and the most disadvantaged player after the first year also recieved 1 (so if the CBN were also the most disadvantaged they recieved 2). I redesigned my Asian campaign several times, first when the WRG 7th Yellow book Lists came out, then again with DBA2.0. With the 2.0 version I picked out one central army (Sung 990AD) - and listed all the opponents and then the opponents opponents, setting limits on distance west. I eliminated from the list any armies that were more than 50% LH or Ps (too light) and those with more than 2 El (too heavy). Eventually settling on 9 armies. Because this was a relatively balanced campaign, when we ran it the first time every player was issued with a goodie card and after year 1 the most disadvantaged player received a second card. Players liked this, it allows for a degree of uncertainty so this is now a standard for my campaign games. The hierarchy for most disadvantaged player is - Least Number of Elements, Least Number of Cities, Lowest Current Prestige.
The Cards We Issue are
1. +1 PIP in Battle - can be used through the whole year
2. +1 to arrival as an allied contingent - used throughout the whole year
3. +1 Element Recuiting - one use at the end of the year
4. Oppponent takes -1 when besieging. The city is sill taken on a 6 unless the besieged are outnumbered by more than 2:1. - used throughout the year. The caveat is designed to ensure survival of an army that is being hammered on many fronts and is down a substantial number of elements, and also to stop gratuitous use of the card when the defending army is relatively strong. This card means that if the besieger rolls a 2 it counts as a 1 (the above risk to the besieged)
5. May cross ocean routes with no penalty. Thus there is no risk of shipwreck in Spring and Autumn - used throughout the year, there is also a card for desert routes (Safe in Spring) and for swamp routes (Safe in Winter) for the appropriate campaigns.
6. May Foment Revolt Once in a Year - one off use, breaks the vassal/overlord relationship between two players. When it is played, the overlord may choose to be at war with the former vassal.
7. Diplomacy. May cancel one war declaration. One off Use at the start of a season. This can stop a planned offensive in its tracks.
May take over a BUA in One Battle Garrison Recoils. - One off use in a year. Allows the capture of a BUA, but the garrison simply recoils outside. This can be a powerful game winning card. Until it surfaces, putting a BUA on the field if you don't have to is dangerous.
8. Ambush. for 1 PIP may deploy one group of up to 4 elements with at least 2 touching either woods, marsh, oasis or a freindly BUA. - used throughout the year. Basically the simplest way to do an ambush without requiring hidden movment or maps. It works the same way as the Littoral Landing Party.
9. Unseasonal Weather - usable throughout the year on one leg of one army or contingent's journey for one given action (battle/seige). It can negate the safe journey cards, subtract or add 1 to the sea/desert/swamp crossing roll or make a standard journey subject to a similar crossing roll. The only limitation is that the holder of the card must be involved in the action somehow (ie attacking, defending, sending a contingent).

I am now working on using my (contentious) rating system to adjust the prestige scores for battles. We trialled it in a one off campaign and it worked quite well.4

My observations over a number of years has been that with 6 or less players, the game goes quite quickly but once a player is taken down, they will probably never recover. As you add extra players, there is a corresponding increase in the time it takes to resolve a year, but has the added bonus that a player beaten has the opportunity to recover.


[ April 21, 2004, 03:33: Message edited by: Macbeth ]

John Meunier
04-23-2004, 04:53 PM
How do you do battles? Do 11 players stand around while two fight out a battle?

I hope to run a campaign in a day for my local group soon. I'm worried about a lot of moaning about standing around and doing nothing while battle turns are played ... I suppose that's an incentive to join in as allies.


04-26-2004, 09:38 PM
Originally posted by John Meunier:
How do you do battles? Do 11 players stand around while two fight out a battle?
That has been a problem. But one of the groups plays at a club, so there is ample opportunity and room to play scratch games, sit and talk, or (until we brought in rules limiting it) sit around the battle and offer advice, or cheer on one side or other.

We have had a lot of success with some people playing larger, longer games (Warrior, DBM, Day of Battle) during their downtime, but coming back to the campaign when required for strategic movement or battles.