Showing posts with label tactical moves. Show all posts
Showing posts with label tactical moves. Show all posts

Friday, September 23, 2011

Combat Maneuver Type

To recap: This blog entry discussed the three Non-Player General (NPG) Character values (Aggressive, Bold, and Cautious). This blog entry linked the NPG Character values to the three Maneuver Types (Combat, Positioning, and Defensive) and the order in which those maneuvers would be selected. In this entry will focus on the Combat maneuver type, and how to further break it down to find the move the NPG should make.

When I look at possible moves to make, and try to determine which move is better (when I have a limited number of PIPs and cannot make all desired moves), I tend to look at one factor: what is the total combat advantage I will gain by making the move. What do I mean by that?



As shown in the figure above, assume that I use a PIP to move the group of two red Blade elements into contact with the two white Auxilia elements. This results in two combats to resolve: one at 5 to 3 and one at 5 to 3, modified by overlaps resulting from the previous combat (it may be a 4-3, 5-3, or 5-2, depending on who, if anyone, recoiled). As you cannot determine who will win until the dice are rolled, a simple method of calculating the combat potential is to score the combat differential of all the combats resulting from the moves.

So in the example above, the move results in two combats, each of 5-3 or +2, so the move receives a score of +4. The move below, in which two red Blade elements are moved into contact with three white Auxilia elements, results in a score of +3.


Note that if the three white elements were Psiloi, with a combat factor of 2 each, the move would be scored +5, so even though the red Blade elements are moving into a position of overlap, because of the superiority in combat it would rate higher than the first depicted.

Now this is very similar to the original scoring system with the Tactical Engine in DBAS, but the idea is to provide a series of rules of which are the "best" maneuvers and only use the scoring as a tie breaker. So, what are the best combat maneuvers?

In my mind, clearly the best combat maneuvers are (in order):
  1. Results in the destruction of the enemy element if the score is tied.
  2. Results in the destruction of the enemy element if the score is beaten.
  3. Results in the destruction of the enemy element if the score is doubled.
  4. Where the worst possible result for the enemy element is it fleeing.
  5. Where my element would be destroyed on being doubled, but the enemy element would not.
  6. Where my element would be destroyed on being beaten, but the enemy element would not.
  7. Where my element would be destroyed on being tied, but there enemy element would not.
In these cases, scoring is easy ... if all the elements in the maneuver are the same, and facing similar opposing elements. But what happens when a group maneuver results in some combats at order # 3 and some at, say, #5? Use the worst case.

That's the start of the idea. Next I will focus on Defensive Maneuvers.

Friday, September 16, 2011

NPG Character and PIP Usage

So, now that we have established that the Non-Player General (NPG) can have a Character value of Aggressive, Bold, or Cautious, and under what circumstances those values change (see last blog entry), what does each value mean.

I have always viewed the use of PIPs in DBA as for one of three reasons:
  • To maneuver into combat 1.
  • To maneuver out of combat.
  • To maneuver, but neither starting nor ending in combat.
1 Typically the maneuver is into or out of contact, but could be into or out of Bow and Artillery range and fire arc too.
For simplicity, I call these three types of maneuvers Combat, Defensive, and Positioning, respectively. These three types provide an order of precedence that can be aligned with the NPG Character into Primary, Secondary, and Tertiary choices, as shown in the table below.

Character
Precedence
PrimarySecondaryTertiary
CautiousDefensivePositioningCombat
BoldPositioningCombatDefensive
AggressiveCombatPositioningDefensive

Note that there is a fourth possibility for a Character value, between Cautious and Bold, which would produce the precedence of Positioning, Defensive, Combat. But I decided to set that aside for the time being.

So, now we have an order to using our PIPs. If the NPG is Cautious, all Defensive maneuvers will be considered first, with Positioning maneuvers second, and if there are any PIPs remaining, Combat maneuvers last.

The next few posts will consider each maneuver type and provide a set of rules for determining the "best" PIP use within each type, hopefully tying it back to the movement scoring entries I started back in October 2010.

Sunday, November 21, 2010

Pondering Terrain Deployment and the Matching Battle Plan

I think most will agree that how the defender sets up the terrain greatly influences the resulting battle. I'm not one of those that think the battle is over because of bad terrain placement, but I do think it greatly changes the odds of your success or failure. Understanding why it does one or the other is the hallmark of a good gamer.

I think most will also agree that how you deploy your troops greatly impacts the odds of your success of failure in the subsequent battle. Again, I am not one that believes that a bad deployment means you will lose - there are too many variables that allow either player to lose grasp of victory - but I do believe that it can give you a deficit of a few VPs.

Quantifying what constitutes a good or bad deployment is a key to understanding and will help you not only in your solo games with DBAS, but in your face-to-face games. I don't claim to be an expert by any means, but the first step to quantification is to put it down on paper (digital or otherwise) so all can see, discuss, and dissect the results. So, here is my straw man.

The (Polybian) Romans


I've played a number of games with and against my Polybian Romans, both solo and face-to-face, and so can use that as a test-bed for discussions.

Against Auxilia-Heavy Armies


The Romans, on paper, do well against Auxilia-heavy armies. They have six Blades with a factor of +5 versus the Auxilia factor of +3. Attacking up a Gentle Hill results in a +5 versus +4 battle. Attacking in Bad Going results in +3 versus +3. Getting overlapped on one side makes the battle +4 versus +3. Sounds good overall with the Romans always having an upper hand.

That said, I have had the Ancient Spanish hand the Polybian Romans a loss even when the Romans won the terrain and put postage stamp sized terrain down. How can that be? One factor not mentioned is the Blades have a movement of 200 paces while Auxilia moves at 300 paces. That does not sound like much, but it really is. Added to the ability for enemy Psiloi to ZOC the Roman line and throw it into disorder (i.e. the element has to peel off from the Roman battle line to deal with the element) and what quickly comes to mind is that the Romans don't do as well as the combat factors portend.

So, if the Romans Blades anchor their flanks on Bad Going terrain (like Woods), it really does not do them any good against these armies as they move through it like butter (although they could have PIP problems due to having a shorter command radius), don't suffer a penalty against others in the Bad Going, and do not have their ZOC affected by terrain, so they can still disrupt you.

If the Romans are going to anchor their flanks, at least the gap should not be so narrow that the enemy General sitting in the center of the pass is within 6" of both forces on the flanks, thus allowing forces on both flanks being in command.

Against Light Horse Armies


The basic combat factors of Blades versus Light Horse is +3 versus +2, so the Romans have a slight edge, but given the incredible movement of the Light Horse it won't be long before the Romans are overlapped and flanked, making the odds +2 versus +2 with a recoil being a quick kill. Having the Psiloi in rear support changes the odds in to +4 versus +2 or +3 versus +2, but that is a thin margin to bet on. Given that the Light Horse cannot be destroyed in a straight-on fight with Blades, they have no reason not to keep tossing the dice in an attempt to break the line (think Carrhae - not Polybian, I know, but the same principle applies).

Quite simply the Romans cannot afford to let the Light Horse get on their flanks or to be without rear support from their own Psiloi. This leads to wanting the flanks of the line to be anchored on Bad Going terrain. This largely restricts the Light Horse to frontal attacks, and if the gap between terrain is narrow enough, gives the Romans a second line for reserves to plug any breakthroughs the Light Horse may be able to force.

Against Heavy Infantry Armies


When facing an army similar to itself, especially Blade-heavy armies, the Romans need to rely more on their auxiliaries, the Velites (Psiloi) and Equites (Cavalry), to get on the flanks of the opposing army and crush the center that the Roman line is holding. This means that the flanks need to be clear for those forces to operate efficiently.

If the enemy line is weaker - all Spear, for example - or less numerous then the Blades on the flanks can start to cave in the flanks and slowly roll to the center, making the cavalry battle on the flanks less of a concern.

Against Knightly Armies


This is probably the least favorable matchup the Romans face. Factors are +3 versus +3 and the loss results in the Romans being quick killed. The Romans can throw in the Psiloi as rear support and get +4 versus +3, but they risk the loss of two elements on one die roll. Not my kind of odds.

This is one of the matchups where the Romans want to be in Bad Going. Sure, they are -2, but so are the Knights, and the Knights also get quick killed on a simple loss. It will be ugly, but with rear support they are +2 versus +1 to the Knights.

Given the Knights movement, they are like Auxilia in that they will out-maneuver the Romans (in general) so can place their superiority where they want.

All-in-all not a good situation.

Against Warband-Heavy Armies


This is an interesting matchup in that the Warbands do not have much of a superiority in movement (a little bump with extra PIPs), have lower factors like Auxilia, but they quick kill Blades. With Blades getting rear support from Psiloi against Warbands the factors are +6 versus +3, so it does not look good for the Warband army. (I don't double-rank my Warband, as I do not like to commit two elements' destruction to a single die roll, so they rarely have rear support.)

Like Auxilia, however, they like Bad Going, so the Roman army is going to want to keep the flanks away from Bad Going terrain like against Auxilia-heavy armies.

Summary


So there you have it. The Romans like to stay away from anchoring the flanks on Bad Going, except when they want it or want to be in it! :)

So where are we. What has this little mental exercise gained us? Well, if the goal is to develop a means for "programming" an opponent, and that opponent is a a Polybian Roman army, we have a start on how they might choose terrain if they are the defender or how they would use terrain, based upon the army you chose. I see these choices as:

  • Avoids Anchoring on Bad Going terrain
  • Anchors on Bad Going terrain
  • Deploys in/moves to Bad Going terrain
One you have the basic strategy - to anchor, deploy in, or not - your battle plan writes itself. You choose a forward line of defense and that becomes your objective. Once you have the objective identified for your elements, you can use that for your scoring system in the Tactical Engine.

I would love to hear your ideas on these basic thoughts. Please feel free to respond here or on the Solo DBA Development forum.

Saturday, October 16, 2010

DBAS - Scoring the Side Effects of Moves

Continuing on with the catalog of combat moves, still looking only at a single element moving. Next let's look at the single element flanking, or attacking from the rear, an enemy group.

Flanking


When we looked at a single element flanking a single enemy element, there was no obvious advantage to the contact as combat to contacting the front edge; without another element in place, the enemy element simply faces to make front edge contact. Without other factors to consider, that produces no advantage or disadvantage.

Let's look at four basic flanking moves.

DBA.DBAS,catalog,moves DBA.DBAS,catalog,moves DBA,DBAS,Moves,Catalog DBA,DBAS,Moves,Catalog
Move to Flank Contact Move to Flank Contact of Group Move to Flank Contact of Deep Group Move to Flank Contact of Supported Group

The first, Move to Flank Contact, we have seen before. Again, with no other context this move produces no greater value than the Move to Front Contact. The Move to Flank Contact of a Group, creates an advantage for the attacker in that it fragments the enemy's command (i.e. it will now require two PIPs to move the two elements where previously it only required one) in addition to creating a threat of destroying an element should it recoil twice.

The Move to Flank Contact of a Deep Group - which would apply not just to elements with base depths greater than 1/2 the base width, but also to elements in two ranks - creates an even greater threat; if the flanked element recoils once, it is destroyed.

The Move to Flank Contact of a Support Group adds an additional advantage over the Move to Flank Contact of a Group: the flanked and turning element no longer receives rear support. Whether this is advantage should be scored separately is questionable; it will be factored in with the Combat Value differential.

The more I ponder the moves the more I realize that the moves themselves are not the keys, but the list of advantages and disadvantages the move brings. If you consider named advantages and disadvantages, such as:
  • Fragments enemy command
  • One recoil will destroy*
  • Two recoils will destroy
  • Breaks rear support**
  • Combat Value differential
  • Can Quick Kill enemy element
  • Etc.
* This is effectively the same thing as a Quick Kill on the Combat Outcome Table, so should be scored the same.
** This will be a factor in changing the Combat Value differential, but is there additional reason to score this?

So, can the actual moves be ignored - thus saving me from cataloging their variations, ad infinitum - and you simply score the side effects the move will produce?

Thursday, October 14, 2010

DBAS - One Attacking Many

Last time I looked at a single element attacking a single element and didn't really find any reason to differentiate between the moves, so now I will try the same thought experiment with a single element attacking a group of elements and see what changes.

DBA.DBAS,catalog,movesDBA.DBAS,catalog,movesDBA.DBAS,catalog,moves
Move to Overlapped Front ContactMove to Double Overlapped Front ContactMove to Supported Front Edge Contact

The first move is the Move to Overlapped Front Contact. Essentially this put the attacker at a -1 disadvantage. Compare this to Move to Double Overlapped Front Contact. Although this move results in a -2 disadvantage, does it warrant being treated separately? The last is the Move to Supported Front Edge Contact, resulting in a +1 advantage to the defender.

Consider the following:

MoveCombat FactorDifference
AttackerDefender
Move to Front Edge Contact+3+3+0
Move to Overlapped Front Edge Contact+4+3+0
Move to Double Overlapped Front Edge Contact+5+3+0
Move to Supported Front Edge Contact+4+4+0

Given that the difference in each combat is the same, should the moves still be ranked separately or do they have equivalent weight, as they all result in a single element coming into front contact with a group of elements and resulting in a combat at +0? Put another way, which is more important: the move itself, or the resulting combat?

One factor in weighing the Move to Supported Front Edge Contact more heavily is that, unless the supporting element is a Pike, there is the potential for destroying two elements in this single combat. That alone warrants weighting, and thus differentiating this move from the others.

Summary

In my mind I have only found one case where the movement of a single element into combat is materially significant; all others seem to indicate that the resulting combat factors are the differentiator. I would like to hear your thoughts on this, either here or preferably on the Solo DBA Yahoo forum.

Wednesday, October 13, 2010

DBAS - Contemplating the Simplest Moves

To start let's consider the moves of a single element against a single element. There are basically three moves to contact:


Move to Front Contact Move to Flank Contact Move to Rear Contact
Move to Front Contact Move to Flank Contact Move to Rear Contact
Moving into flank contact from the left and right are technically two different moves, but functionally they are the same given our "universe" with no other factors.

This leads me to wonder: if there are no other factors - this is simply one element on one element and no other element comes into play now, or in the near future (i.e. within the Zone of Control of an enemy element or within one move of contact) - is there really any difference between the three moves? Does it necessitate cataloging all three variations and ranking them separately?

At this point, I am willing to say yes catalog them, just to be complete. But at this point I have no means of saying one move is more or less valuable than another, so they will all be scored the same. As I catalog other moves, I think either the proper scoring will come to light, or the need to differentiate these moves will disappear.

Tuesday, October 12, 2010

DBAS - Contemplating Moves

As part of my involvement with the Solo DBA development effort, I have a tendency to get on an idea of something to try, and then try to catalog all of the variations of that idea. The latest idea to get this treatment is available moves.

Problem

A fundamental problem for the solo gamer is to determine what move - from all of the possible moves - should be taken for the non-player, or programmed side. In a game like DBA, where you have a command and control mechanism that does not necessarily allow a player to move all of their units every turn, you end up with an additional twist, which is to evaluate the chosen "best" move for one unit against that of another unit and determine which should be taken in those cases where you are restricted and cannot move every unit.

So, to restate, the problem is two-fold:

  1. Determine, from the set of moves that an element or group could make, which is the best move to make, and
  2. Determine, from the set of best moves found in #1 above, which ones to make if not enough PIPs are available to do them all.

Solution (or Attempts at Solutions)

In previous versions of De Bellis Antiquitatis Solus (hereafter referred to as DBAS), my version of rules for the wargamer to use DBA for solo games, my approach has been as follows:

  1. Determine the "best" move for any given element or group of elements. (The "best" move is the one determined as having the highest score - see below.)
  2. Score that move, based on:
    • The Non-Player General's (NPG) current mood (called the Strategic Stance).
    • The category of the move (Combat, Defensive, or Approach).
    • Conditions resulting from the move, such as whether the following combat gives you a tactical advantage, retreats you out of a losing combat, moves you towards and objective, etc.
  3. Play out each move, from highest score to lowest, until the NPG runs out of PIPs for the turn.
This process worked well, and despite the sound of it, did not take a lot of time to calculate the scores of the various moves. (After awhile, you pretty much got the feel for which move was better than another.)

Where I did not like the system was that I tried to bite off too much; I was trying to provide a different scoring system for each Strategic Stance of the NPG (there were five). My last effort was to reduce the Strategic Stance Values to three - Cautious, Moderate, and Bold - and then provide a preference to the type of move (Combat, Defensive, or Approach) based on the Strategic Stance. A simply table shows how it works.

If the Strategic Stance is......the First Preference is......the Second Preference is......and the Third Preference is...
CautiousDefensiveApproachCombat
ModerateApproachDefensiveCombat
BoldCombatApproachDefensive

As you can see from the above, the NPG's mood determines the type of move favored. As I used a scoring system I simply add +4 to the score for the moves in the First Preference, +2 to the score for the Second Preference, and +0 for those in the Third Preference.

This is a good start, but it still requires you score out all possible moves for an element or group before you can figure out what gets the first PIP.

What About...?

So, one of the ideas is to rank the actual moves and consider them in order. Essentially this means cataloging the possible moves and giving them point values. If each move has a value, it probably needs a modifier based upon how good it is compared to other like moves.

For example, consider the basic Move to Contact, where one element moves into contact with another element. If Move A results in a combat of +5 versus +3 and Move B results in a combat of +3 versus +3, should Move A be valued higher than Move B because A has a better chance of winning the subsequent combat (all other things being equal)? In the past my answer was yes (and probably still is).

Now consider a Group Move to Contact (two elements, moving as a single group, move into front-edge contact resulting in no overlaps but rather initially two one-on-one combats). If the Group Move to Combat results in two +4 versus +3 combats does that move rank higher than a Move to Combat resulting in a single +5 versus +3 combat? As you might imagine, the resulting scoring system that takes all of this into account could probably get out-of-hand pretty quickly.

So, if you go down this path of cataloging moves and assigning scores to those moves, your next basic decision is, do you:

  1. Rank the moves in order.
  2. Compare each element/group that can make that move to determine which ones get PIPs first.
Or do you:

  1. Rank the moves in order in order to assign a basic score to that move.
  2. Modify the scores based upon additional factors.
  3. Execute the moves in score order.
The latter sounds right, on face value, but is much more difficult to pull off, I think. Next, I'll look at some simple moves and pose questions on how to go about tackling these issues.