Friday, October 17, 2025

Lusitanians versus Romans and subsequent siege

Could almost be from the Lusitanian Wars 155 - 139 BC and certainly had an historical result as they couldn't beat the Romans commanded by Consul Stefanus.

The Romans were out scouted and look scattered before the Lusitanians.

The Lusitanians press forward.

Getting close with the Lusitanians holding the advantage.

Both sides took a battering, but the Lusitanians are feeling confident.

The Roman cavalry, charged by the Lusitanian cavalry,
defeats them and then emboldened follows up, 
routing the Lusitanian left flank.
Meanwhile the Romans have bounced back in the centre 
and are pummeling the remaining Lusitanian infantry.

Decisive victory to the Romans.

I am working on a set of siege rules for use in campaigns but also as an after-battle adjunct.  This game gave me a chance to do an initial playtest.  I will provide another post with all the detail.  They have been adapted from the boardgame Kingdom of Heaven which is where the terminology comes from.  

The Lusitanians have 5 units providing 6 steps, 7 manpower and 9 combat strength. They have lost their commander.

The Romans have 7 units providing 10 steps, a massive 18 manpower and 21 combat strength. This means they can initiate a siege without problem.

The Lusitanian stronghold has a resistance factor of 5. For purely imaginative purposes the battle took place near Óbidos. 

The Romans decline to call for immediate surrender and move on to easily blockade the Lusitanians.  

The Romans play "Rats in Enemy Food Supply" which reduces the resistance factor to 3 and the Lusitanians lose 1 step and their combat strength drops to 8.

The Lusitanians play "Blockade Broken" The Romans suffer 2 step losses, and they drop to 8 steps, 16 manpower and 19 combat strength.

Angered the Romans play "Battering Ram" the resistance factor drops to 1 and the Romans make an assault. They inflict 3 step losses on the Lusitanians but receive only 1 in return.  The stronghold falls.  

The siege is over.








No comments:

Post a Comment