Ancient Battlelines Clash first face to face playtest

My first face to face playtest
Andy suggested coming over for a game today using the rules I am working on, Ancient Battlelines Clash (ABC).  It would be the first face to face playtest of the rules I have done.  There have been others out there that have provided feedback over the years but this would be the first time for me.  I have done around 20 solo games of ABC but that is not the same.

In summary, it went well.   There are a couple of changes to the layout and content of test tables to make them easier to read and I need to redo the charge/pursuit table; but the rules themselves stood up - from my point of view - really well.  We only had one game and Andy seems to think they were alright.  The big plus was that good and historical tactics won out.  And those tactics were Andy's.  He won by a lot by using much better tactics than me despite not knowing the rules (he had not read them beforehand). So the rules seem to reward good historical play, at least after one play! Andy took home a copy of the rules with him.

Something that occurred while explaining the rules
While explaining the rules to Andy, I realised that the root of these rules are (and I am generalising a bit here) Warrior Kings - now Rally Round the King - for reaction tests; Bill Bank's Ancients for combat and the way disorder works; Justified Ancients for command rolls and missile fire and Armati for restrictive movement, groups and general ethos.  Andy had read some of these rules but played none of them.  If you have played all four of these rules, it will be really easy to pick up on Ancient Battlelines Clash and what is is attempting to portray - particularly WK/RRtK for a sequence of play based on reaction tests and Bill Banks Ancients for how combat and disorder works.  If you had not played any of these, it will be just as easy as any other set of rules...

The Game
Here is a brief run down on the game - Alexandrian Macedonian Vs Later Achaemenid Persian.

I have a very formula driven excel spreadsheet to generate random armies and terrain.  But I do not have many army lists.  Most of my focus is on the Peter Side's replays.  I do have a draft Macedonian list that I quickly updated to be able to randomly create a army (I have a Later Achaemenid Persian army list).  My randomiser basically stops with the last unit that does not take the army over the defined point level.  But what that means is if the point level is defined as 35, and a 5 point unit takes the army points to 36, the army list will only have 31 points and could have had another 4 points (light infantry, skrimishers etc).  I need to fix this, which may not be easy as it is excel, not code.

Macedonian (attacker) (Andy)
1 Companions (high fortitude, disciplined)
1 Light Cavalry
2 Phalangites (phalanx)
1 Hypaspists (phalanx, high fortitude, drilled)
1 Peltasts
1 Skirmish Infantry

Later Achaemenid Persian (me)
1 Heavy Cavlary
4 Poor Heavy Cavalry (low fortitude)
2 Light Cavalry
1 Hoplite (phalanx)
1 Light Infantry
2 Skirmish Infantry

 Deployment:

Macedonians on the left.  From their right to left, left is cavalry, pikes and the light infantry. Persians left to right is the good cavalry, LI and hoplite, poor cavalry and some light cavalry as flankers.

The Persians move the light cavalry up to flank to get at the Macedonians from the side.  Note this this turned out to be a wrong thing to do - they were too far to order properly and went too far.  They should have stayed where there were and waited - they were not faced by anyone - they did not have to move up.  Some of the Persian poor heavy cavalry move up against the Macedonian peltast and skirmisher and the Macedonians are routed. 

Macedonians move up the entire line; some Persian heavy cavalry at right is threatening the Macedonian light infantry.

 

A picture a little further along showing the Persians cleaning up the light infantry (to the centre right).  It was the last good tactical thing I did!

The Persian heavy cavalry with general is forced to charge the Companions. While writing this up, I have realised they they should have not been subject to mandatory charge; about 3 games ago I changed it from all heavy cavalry being subject to mandatory charge to only high fortitude and modified the impetuous ability so only impetuous units were subject to mandatory charge. Easier to say units with impetuous ability subject to mandatory charge than have to remember it is Knights, Heavy chariots, elephants and high fortitude heavy cavalry.
 

Persian Heavy cavalry and general in combat with Companions and the Macedonian general.

 A general loss check resulted from the combat.  Macedonians were OK, the Persians lost their general.  This made it hard for the rest of the game to order troops.
 

Where the Persian general was.  The replacement subcommander is required only for distance measuring for orders, otherwise it is useless!

 Persians start to move the right flanking cavalry units back closer to the action, but it is too little too late.  The Macedonians manage to destroy a hoplite, and also the heavy cavalry now the genral is not there to bolster their ranks.

Note the lack of Persian Heavy cavalry, and the hoplite in the centre doe snot last long either! Also note the high quality of Andy's painting (the Macedonians) compared to my ebay acquired Persians.

The Persians then lost one more heavy cavalry (from a hoplite), the Persians reached their breakpoint and game over.  Well deserved win to Andy.  One thing that was good explaining the rules and probabilities is that the game rules made sense in the context of what went on in ancient battles, or at least in my version of events!

The end.

 So that's it - a fun game and not too long.
 
Changes to the rules (for those interested)
I had a number of rows in some of the test tables with the labels "2-5", "6-7", "8+" but they all applied to the same result. I was trying to keep the tables consistent with the combat table but most other tables all have the same result for 2+.  So to un-confuse results, I can just change the "2-5", "6-7", "8+" to "2+".

I was thinking of doing this anyway, but only Infantry and Chariots are -1 to combat when disordered.  Rather than describing this under troop types in the rules, I can add this to the combat table.  It will be more obvious.

I need to add veteran and drilled and some other abilities to the quick reference chart, plus a few minor content additions to the reference chart.

I use the description of +0, +1 +2 general but really the +1, +2 enhances command and control, it does not affect the general itself, better to describe the +0, +1, +2 as command structure, rather than the general.

The biggest change is to the mandatory charge/pursuit test.  It did not sit quite right and the play with Andy confirmed I really have the fortitude modifiers back to front (high fortitude units are should be less likely to pursue).  Currently the table has 2+ for charge/pursuit and less than that no pursuit/charge.  High rolls are good in this game, and most of the time you do not want a unit to mandatory charge/pursue, so 2+ should be changed to no pursuit/charge.  The was the way it was late last year but I changed it.  I am going to change it back, but I have to think through the modifiers to make sure I don't stuff it all up!

Battle of (2nd) Mantinea 362BC using Ancient Battlelines Clash

Introduction
This is game 12 in playtesting my ancient rules. Previous games used my rules called Ancient Warrior  Battles.  The latest version is on its own blog page. I am playtesting the rules by replaying all the Peter Sides scenarios from his Historical Battles books.  ABC is designed to finish in under an hour on 2'x2' tables.


Battle of Mantinea
Athens joins the Spartans to attempt to curb the Theban influence over Greece. Once again, Epaminondoas leads the Thebans into battle against the Spartans.

Here are links of interest and that I used to create the scenario:

Wikipedia article
DBM scenario

Changes to the Peter Sides scenario
Originally 44" wide, I reduced the number of hoplite bases to fit to 24".  I also did not place the streams on the table as the scenario indicates they have no effect.  The scenario had Sparta and Allies all Sp(O) and Thebes (and their allies) all Sp(S).  Helped by Lost Battles, I created 1 high fortitude unit on each side, and made the rest average.

Troops

Thebes

Hoplites at back (Deep phalanx on the right); cavalry and skirmishers on the flanks.

1 Elite/formed-deep Hoplites, HI, protection 0, phalanx, fortitude +1
4 Hoplites, HI, protection 0, phalanx
4 Hoplites, HI, protection0, phalanx, fortitude -1
3 Heavy Cavalry, HC

6 Skirmisher, SI, javelin

1 General (Epaminondoas)

Breakpoint: 12

Sparta and Allies

Spartans on the left end of the hoplite line; cavalry and skirmishers on the flanks.

1 Spartan Hoplites, HI, protection 0, phalanx, fortitude +1
6 Hoplites, HI, protection 0, phalanx
2 Heavy Cavalry, HC
2 Skirmisher, SI, javelin

1 General (Agesilaus II)

Breakpoint: 9

Deployment
Deployment:

Thebans at the bottom; Sparta and allies at the top.

The Game
Theban left flank cavalry charge opposing cavalry and with some pursuits, end up on the hill, both sides disordered.  Two on one combats see only the worst result inflicted on the loser, not two results from each one.  Result was disorder and retreat and then both Theban cavalry pursued and all ended up disordered in the followup combat.  Fast, fun and sometimes surprising.

Theban cavalry pursue up the hill.

And in the very next combat, the Allied Cavalry roll a 1 (which is bad) against Epaminondoas and the heavy cavalry.  Allied cavalry routed.

Spartan and allies advance the whole line.  Spartans taking out the Theban skirmish infantry along the way, but are disordered on a unlucky fired-on test of a 1.

Seeing this, the Thebans advance all their non-poor hoplites (basically the left half of the line).  They are just out of reach and the Allies stand (the result of a proximity test - what to do when an enemy is within 4cm).  I have been tempted to class some hoplites as impetuous, just so they will charge when the enemy come close like this, rather than stand.  But I do not know my history enough to call this. Anyway, the rules are flexible enough that you would just add the impetuous ability to hoplites if you so choose.

The battlelines are very close (allies to the back, the non-poor Theban hoplites at the bottom)

This gives Agesilaus II a chance to rally the Spartans (50% chance as he is attached). Woo-hoo!  Rallied, undisordered, back in the game!

Agesilaus and the recently rallied Spartans

Thebans clash with the battleline. First combat sees a Theban hoplites routed!  (Theban hoplite unit roll a 1 - retreat and disordered.  Allied hoplites pursues and roll a 6 - Theban hoplites routed).  But then a Theban skirmisher further back disorders the victorious allies.  Have I said this is fun and fast?

There was a Theban hoplite to the right of the one in the left of the picture.  But it routed.

Next, I could not make this up if I tried.  The Theban deep phalanx rolls a 1 against the Spartans and so retreats.  As Epaminondoas is attached, a 1 means I need to roll to see if the general leaves the field (killed, wounded etc).  I roll a 1 which is a yes. Epaminondoas is out of action.  Just like in 362BC.

Theban deep phalanx (botom left) after retreating.  Epaminondoas was with them but left the field.  The single figure behind the unit is the replacement general.

An unusual string of 1's and 6's sees the battleline broken up and losses mount in one turn - 2 hoplites from the Allies and 1 Theban.  The Allied left flank enters the fray as well but eventually the cavalry take out a disordered allied phalanx.

Overview of battleline from the Theban side.  There is a large gap in the middle and the Theban cavalry has entered melee to the right of the picture (and manage to rout a disordered phalanx)

The Thebans find it hard to move units with a -1 (poor) general and rallying is out of the question (so the Cavalry are effectively stranded on the hill as it will take ages for them to come back).
Agesilaus II attaches to a hoplite and takes out a Theban hoplite.  And next turn attaches to a cavalry unit that came from the left flank and assists it to rout a disordered hoplite (it may look like a flank attack but it isn't - have to be completely behind the front line for that).

A not flank attack but the hoplites are disordered and the cavalry with attached general is too much for the unsupported Theban hoplite, and the latter rout.

Thebans are now at their breakpoint and so have lost.

End game overview - Thebans to the bottom and Theban cavalry on the hill at the top left (and centre top)

Verdict
Great game.  About 80 minutes to play and write up and take pictures and type some clarity into the master rules so maybe 30 minutes all up.  I did get to clarify some parts of the rule in this game - if you capture a replacement general, it is not worth anything to the army's breakpoint count.  A replacement -1 general gives no modifiers to combat was not clearly spelt out.   This game seemed full of two on one combats and I followed the section on it carefully as I have not had many before.  No changes - very happy with how it works.  Onwards to more games! 

Battle of Delium 424BC using Ancient Battlelines Clash

Introduction
This is game 11 in playtesting my ancient rules. Previous games used my rules called Ancient Warrior  Battles.  The latest version is on its own blog page. I am playtesting the rules by replaying all the Peter Sides scenarios from his Historical Battles books.  ABC is designed to finish in under an hour on 2'x2' tables.

The Battle of Delium is not one of the Peter Sides scenarios, or in my other replay list, Bill Banks Ancients.  I came across Delium as a replayable scenario while researching Leuctra.  Hence I am playing it out of chronological order compared to the previous battles.

Battle of Delium
Athens invades Boeotia and fortifies the temple at Delium.The Theban commander, Pagondas, convinces the Boeotian forces to attack the Athenian force, led by Hippocrates.

Here are links of interest and that I used to create the scenario:

Wikipedia article
fanaticus.org DBA scenario
Warhammer Ancient Battles scenario
Thucydides Book IV 89 onwards

I also used Lost Battles (Sabin).

Troops

Boeotia

1 Elite/formed-deep Hoplites, HI, protection 0, phalanx, fortitude +1
6 Hoplites, HI, protection 0, phalanx
2 Heavy Cavalry, HC

4 Skirmisher, SI, javelin

1 General (Pagondas)

Breakpoint: 10

Athens

7 Hoplites, HI, protection 0, phalanx
2 Heavy Cavalry, HC, fortitude -1

1 -1 General (Hippocrates)

Breakpoint: 9

Deployment
Deployment:

Athens on the left, Boeotians to the right on the hill.  Note the rivers that inhibit flanking.

Note that both wings are constrained in movement by the rivers.

The Game
An unfair fight if I ever saw one.  But the river restricting the cavalry movements may even it out a bit (in the actual battle, Pagondas moves cavalry from one flank to another to assist the failing left flank).

Thebans move the entire line forwards.  Athens responds by moving three hoplites on their right flank up.

Athenians (top) advance 3 hoplites to face the Boeotian left flank (bottom)

The plan is the Skirmish infantry will throw their javelins, and then hoplites charge forwards and as the general is attached to one of them, there is a chance to break the Theban left flank.  It sort of works - one retreat each.  This is the best chance for the Athenians to win.

One retreat to each side (Athenians at the top)

The Boeotian right flank move up to tempt out the Athenians.  While on left flank the Athenian Hoplites with an attached Hippocrates routs opposing disordered phalanx; they pursue into another disordered hoplite that rolls a 1 and routs too!  Hippocrates is doing well.

Hippocrates (centre) and hoplite unit that has no units in front - they have routed.

Athenian left flank forced to advance to protect the right flank. Pagondas and the Boeotian Heavy Cavalry move from the Boeotian right flank moves to shore up the left flank.  

Pagondas (centre) and Boeotian heavy cavalry (centre rear) moving to shore up Boeotian left

 An Athenian hoplite, shored up with an attached Hippocrates, routs the opposing cavalry (the one that was already on the Boeotian left flank).

Hippocrates and victorious hoplites

Not to be outdone,  Pagondas assists a disordered hoplite to rout an opposing hoplite too.

Pagondas and victorious hoplites.

The centre 2 Athenian hoplites advance and mange to rout a disordered hoplite with Pagondas; they advance and capture him too!

Pagondas (on the left) just before having the hoplites he is with rout, and then being captured by the hoplites he is facing

Boeotians reach breakpoint.  I play to the end of the Athens turn but nothing more.

End of game position (Athens at the top and the left as well).

The Thebans may have had a chance with the heavy cavalry flanking disordered hoplites, and with the elite hoplites (on the right) with the +1 fortitude advantage on the opposing hoplites.  But they just did not get the chance.

Verdict
Game took one hour, including taking photos and writing the progress of the game.  Fast and furious and great fun.  I did not expect the outcome but the whole game was a tight balance and could have gone either way every time I rolled the dice.  I love ancient wargaming.

Spaceship miniature game - Starfire with Firestorm Armada models

Introduction

So, spaceships.  Where did this come from?  I have never done spaceships miniatures before and so I bought some earlier this year.  Why does a wargamer ever need a reason to start a new project?

Back in the early 80's, and before I got together with my partner (and now wife), I used to do a fair bit of science fiction boardgaming (ones I played a few times that spring to mind are WarpWar, Starforce, Titan Strike, Ogre, Dune, Sword and the Stars) and also spaceship boardgames.  I did play Starfire a bit (the original ziplock bags and then the second edition), SFB a lot, Yaquinto's Shooting Stars  and FASA's Leviathan a little bit, and some space fighter miniature rules called Starhound (but playing with someone else's homemade spaceships).  I stopped doing this around 1985.
 
When the spaceships turned up my wife asked "Since when are you into spaceship gaming?"

And I replied (with the truth!) "Oh, in the early 80's I used to do a lot of space gaming."

"Oh, before my time then..." and lost interest in further conversation. No "What are you doing?!" or "How much did you spend?" or rolling of the eyes.  A keeper.
 

The acquired ships

The ships are a bunch of painted Firestorm Armada ships - a few starter kits and models.  Large models, but I am expecting I can also use them to play some games with my children.  And I like using larger spaceships.

The Firestrom armada ships - mostly Dindrenzi and Terran.

Rules

I have acquired a few spaceship rules (and science fiction boardgames, but that is another story) since over the years, assuming I would maybe get back into it - Full Thrust, Silent Death, Starfire 3rd edition (and Ultra edition!), Attack Vector: Tactical, Squadron Strike. Also some more recent that are available as a PDF; THW 5150: Fighter Command being the most recent.

But what rules to use? I am looking for quick games with maybe up to 1/2 dozen ships a side.  Not fleet battles, and not detailed ships as per SFB.  Full Thrust looks ideal and I may try them later, but to get me in the mood for spaceship gaming, I am going to use Starfire.  I loved Starfire more than SFB but I never liked the large battles and large ships that were in Starfire and also played smaller scenarios.  So I will go with that for now, but I do have Full Thrust, Starmada Nova, Warcosm and 5150:FC on the top of the pile to try out. I am using Starfire as I know the rules, not because I think it is the best system out there for me.

 

Starfire 2nd Edition box

Starfire very quick overview
A ship in Starfire is a represented by a list of ship systems, from left to right with shields and armour to the left and weapons and engines further in (see below for an example).  Damage is crossed off from left to right, although some weapons can skip armor and/or shields.  Ships move up to 6 hexes and need to move a number of hexes before they can turn 60 degrees (no vector movement here).  Range of beams etc is normally around 10, and missiles are 20.   Players moves ships one at a time alternatively and fire one at a time alternatively.  Who moves or fires the first ship is via initiative that is rolled for at the start of each turn.  Movement is broken down into 6 phases - in phase 1 all players move ships up to one hex, second pahse all players move ships another hext, then thirs phase.  Can only move in phases up to your movement rate, so faster ships will get a movement advantage.  when fighters turn up, they move further than 6 and there are more phases to compensate.  that's about it.,  no specific weapons firing arcs but no ship can fire 60 degrees to the rear.
 

Starfire Mods

Life would not be complete without tinkering with the rules.  So this is what I have done so far:

I use the rules from the second edition except for:

• I use the ships systems from the 3rd edition (with magazines, engine rooms etc) so I can use the ship designs from "The Stars at War". I did not want to design ships for Starfire.  Although interesting, I did not want to invest in learning design when I am unlikely to play many games of Starfire.
• I converted the to hit table from 2d6 to 1d6 (I like rolling single dice - always bugged me the 2d6 per weapon)
• If you roll 2 1's when firing with all the ships weapons, you inflict a critical hit and inflict another hit 1d6 systems further in (or the last one if you roll higher than the number of systems left)

Scenario

I was looking for something simple with only a few ships (a lot of battles are large with lots of capital ships) and a few different ship types to try out my first foray in 28 years (wow, it sounds like a lot when I write it down!).  So I used scenario 2 from "The Stars at War" with the Khanate of Orion defending a Space Station with a Light Cruiser and 3 escorts.  Attacking is the Terran Confederation with 2 destroyers and 2 frigates.
 

Forces

Khanate of Orion

Spacestation BS1 (0) SSSAAAALhQRGRGMg (0)

CL Karhae (flag) (3) SSSSSAAAA(Bbs)G(II)LR(I)RMgQsH(CIC)(II)(I)Qs(II)(I) (6)

ES  Malkon  (2) AH(I)GRMgQS(I) (4)

ES  Talron (2) AH(I)GRMgQS(I) (4)
 

Forces start 20 hexes of the planet (Mazdranar)
 

Terran Confederation

DD Napoleon (flag) (2) SSSSSAAAAHW(I)LM1(I)(I)(I)WMgLhQ(I)(I) (6)
DD Discovery (refit) (2) SSSAAZHL(I)(I)WMgQs(I)(I)(I) (5)

FG Outreach (2) SSAHX(I)(I)(I)GRMgX(I)(I)Qs(I) (6)

For those not familar with Starfire the main things to know are:
S = Shield
A = Armour
(I) = Engines
G = Gun
R = missile launchers
W = Gun /missile launcher combo
L = Laser
 

The Game

 Starfire is hex based and  so I dragged out the hexsheets from Leviathan and put them on the floor.  I have a dark wood 3x5 fold out table that I would have used if it was non-hex.  Not that fond of hex based miniature games, and I could have done with larger hexes.  But you play with what you've got! 
 

Deployment

Terrans come on the board and advance over 2 turns into missile range.  They focus on one of the Escorts (Malkon) and do 3 damage, reducing its speed to 2 and taking out the Gun.

Exchanging missiles

The Khanate missed 2 out of four shots available (a 6 is a miss!) focusing on the Discovery.


Terrans have one more laser (range of 8) in total than the Khanate, and so move closer.  The Khanate have more Guns, so need to get closer too (guns are range 9 with a 1 in 6 chanve of a hit; range 6 is when there is a 50% chance to hit. Beams will only miss on a d6=6 out to range 8.

Malkon loses second weapon and effectively out f thefight, napoleon has M1 so splits between Karhae and Malkon.

Closing in....

Kahae focuses on the Discovery and takes out shields and armor, and the Talron does first blood on an internal system (a hold) of Discovery.
 

I just like the look of the ship so here is a pic (Dindrenzi Cruiser standiung in for the Khanate Karhae)

The Terrans are now in range of the Space Station. It has two missile launchers that it targets on the Discovery. Yep.  Laser and Engine gone.  Talron then takes out remaining weapons on the Discovery.  Karhae hits with all weapons on  Outreach,  but all Outreach weapons are still OK - they are well back in the ship list of systems.


Something I have forgotten after 20 years is that missiles don't hit well at range 0-2.  Oops for the Khanate who I have moved quite close to the Terrans.  The Terrans have dual missile/gun launchers so are fine at short range.

Karhae gets 4 hits on the Outreach - not looking good - Talron hits on its shots and Outreach has no weapons left. Napoleon proceeds to rip the guts out of Talron.

The ships in action

Only Napoleon and Karhae and the pace station left. The Napoleon can take more damage than the Karhae at this stage, but the Space Station will keep sniping.   It will be a close run thing.

Karhae is too close!  Only it and the Terran destroyer Napoleon is left in the fight.  Karhae begins to turn and run for the Space Station.

A couple of turns are spent exchanging shots as Karhae runs closer to the space station.  Napoleon gets the initiative for the first time in ages, fires first and takes out Karhae laser and missile launcher.  So Karhae only has one weapons left; but Karhae fires back and takes out a weapon on Napoleon too.  Space Station still sniping.

Karhae is back near the Space station.  Eventually Napoleon becomes devoid of weapons.

I played a few more turns with pot shots being taken but Napoleon lost its last weapons before being able to drop the shields and armour on the Space Station.  So a win the the Khanate, but with much damage to both sides.


Verdict

Even for a simple combat sequence, there what a lot I forgot about tactics - Beams Vs Missiles, close range stuff, rear arcs etc.  And to really focus on the order that the ship systems are!  But I had a blast.  It may be awhile before I drag them out again but I hope to do so later this year.  Not sure if I am up to the complexity of some of the rules after playing Starfire - firing arcs, written orders etc may end up being too much for what I want from spaceship gaming!

Battle of Leuctra 371BC using Ancient Battlelines Clash

Introduction
This is game 10 in playtesting my ancient rules. Previous games used my rules called Ancient Warrior  Battles.  The latest version is on its own blog page. I am playtesting the rules by replaying all the Peter Sides scenarios from his Historical Battles books.  ABC is designed to finish in under an hour on 2'x2' tables.

Battle of Leuctra
Thebans and Boeotians, led by Epaminondas, defeat the Spartans and their allies.  This victory broke the Spartan domination of Greece.

Here is a link of interest:

Wikipedia article

Changes to the Bill Banks Scenario

The scenario is designed to play on a 24"x16" board, so no changes required there. The depth ratio will be fine being longer as ABC has longer move distances than DBA.  The scenario also had all the Spatans and ally hoplites as Spear (O), except 1, and all the Theban and ally hoplites as Spear (S). I changed this by improving some Spartans, and downgrading the Theban allies.  Lastly, I reduced slightly the number of bases on each side so they would fit onto a 24 frontage - DBA allows for Spear rear support, and my rules don't.  In the original scenario there are too many units to deploy in a single line on a 24" frontage.

Troops

Thebans and allies

 

Thebans, from left to right, skirmishers, hoplites, cavalry (and elite hoplites behind).

2 Elite Hoplites/Sacred band, HI, protection 0, phalanx, fortitude +1
5 Hoplites, HI, protection 0, phalanx
3 Heavy Cavalry, HC

4 Skirmisher, SI, javelin

1 General (Epaminondas)

Breakpoint:10

Sparta and allies

Spartans, left to right, skirmishers, cavalry, hoplites, skirmshers.

2 Spartan Hoplites, HI, protection 0, phalanx, fortitude +1
8 Hoplites, HI, protection 0, phalanx
2 Heavy Cavalry, HC, fortitude -1

4 Skirmisher, SI, javelin
1 Camp (on a hill)

1 -1 General (Cleombrotus I)

Breakpoint:12

Deployment
Deployment:

Spartans to the left.  Their battleline is definitely a lot longer than the Thebans!

The Plan
Theban: The Theban cavalry need to charge the opposing Allied Cavalry and hopefully force them back (rout or retreat) through the hoplites, disordering them.  Followup really fast while disordered to gain an advantage.  Refuse the weak right flank.
Spartan: The Theban Cavalry are going to come on, and are better than us.  Hold on as long as possible while attacking with the left flank where we have the superiority of numbers.

The Game
Theban cavalry charge the Spartans counterparts.

The Theban cavalry (right) charges into the Spartans.  The generals are the single cavalry figures.

Three average heavy cavalry Vs two poor ones;  one Spartan cavalry routs back through their own hoplites and disordered them.  This is something I have borrowed from Justified Ancients - every unit will involuntarily interpenetrate others when routing or retreating.  Heavy infantry will be disordered when interpenetrated.  It also allows for the historical event in this battle where the retreating spartan cavalry disrupts the Spartan hoplites behind them.   One Theban cavalry is also forced to retreat.

The elite Thebans hoplites move up to be closer to the cavalry battle.

While cavalry battle is a swirling, the rest of the battleline on both sides moves.  The Thebans needed to advance to protect there cavalry flanks.

The Spartan cavalry is depleted and routs backwards, disordering another Spartan hoplite.  A Theban Cavalry pursues into a skirmisher unit - routs it and then pursues even further into a Spartan hoplite and is locked in melee.

After the cavalry met - the Thebans are on the left.  One Theban cavalry (at the rear of the picture) pursued a routing Spartan cavalry unit into a hoplite unit.  Green bushes are disorder markers.  There is a lot of disorder!

More toing and froing with the Theban cavalry and Spartan hoplites.  A Theban cavalry unit retreats through the elite Theban hoplites and disorders them (ha! just like they did to the Spartans).  Spartan unit with  Cleombrotus I commands the centre. Epaminondas had the Theban cavalry unit he was attached to destroyed, but he survived.

Another turn and on the Theban left flank sees all the Spartan cavalry gone.  One Theban cavalry lost. Theban elite hoplites are in the centre (both disordered by the retreating Theban cavalry seen on the right). 
Epaminondas can be seen alone between two enemy hoplites.

The Spartan left flank advances and manages to rout some skirmishers (skirmish infantry will usually evade from heavy infantry but are disordered.  Two evades will destroy a skirmish infantry).  They also engage some Theban hoplites  but they are both disordered and locked in melee (which is what normally happens when two similar units meet).

On the Theban right flank the Spartans (on the left) are doing better on this flank. 

This ends turn 3!

A Theban hoplite charges into a Spartan hoplite already in melee and already disordered.  This fresh hoplites manages to deplete the Spartan hoplite which is a rout (a deplete result when disordered is a rout).

..well, maybe not so good.  The Spartans are down a hoplite (the gap in the middle of the line at the rear).

Epaminondas moves over to assist cavalry in combat with disordered Spartans and with a good roll depletes them and the Spartan breakpoint is reached.

Theban cavalry that routed an opposing disordered hoplite and caused the Spartans to reach their breakpoint.

 Game over.

End game. Most of the Spartans are in the centre line and the darker bases - the Thebans are to the left and lighter.

Verdict
 The Thebans had only lost one cavalry and all their skirmishers, but they did have a few lucky rolls as well.  More of the cavalry would have gone with average rolls and it would have been a much closer game.  Rules are still fun and no changes required, a good thing.  I will be out of the hoplite clashes in a few more games and so will have to wait and see if more changes are required with different troop types.

The shorter format definitely is helping me focus on getting more games - I have the next one already half played and the four after that in varying stages of scenario development.