Haywire Rules - A Discussion

 Hey everyone. I know it has been a long time since my last blog post. Honestly it is because I have been pretty consistent in getting face-to-face games lately, plus some computer games, plus wrapping up my work (as I am retired now).

Haywire

In this post I want to discuss the solo mechanics in the rule Haywire, which are free and in beta. This is not a review of the rules themselves as I have not fully read the rules, nor played them, but I have learned enough about them from this video play through to discuss some of the solo/cooperative game mechanics. (By the way, the video is hilarious as the author is trying to explain the basics of the game, but you can tell he gets a bit invested in the scenario and his luck is both fantastically good and bad.) This discussion is largely based on the video, but in some cases I followed up by finding a specific rule in the PDF.

How is the Scenario Determined?

Haywire divides the board up into 12" (30cm) squares. For each of those squares you will have one threat token representing possible enemy forces (PEF), with a minimum of ten tokens. So a 3' square board would have ten threat tokens, a 4' square board would have 16, and so on. The author, in the video, used red plastic silhouettes of soldiers for the threat tokens, which was very effective in quickly identifying where the threats were located, when it came time to interact with them.

What the rules do not specify is what the board looks like, i.e. the terrain. I have noticed this in a number of scenarios lately where the scenario authors are specifying deployment zones, objective locations, and such, but only a basic description of the terrain and layout. Is this good? Is it because players skip over scenarios that use terrain setups they don't have?

Haywire is the same in that it does not specify the terrain at all. You are free to setup the table however you wish. It simply states that the board should have "enough terrain and scatter to block LOS" (line of sight).

How is the Mission Determined?

One thing that most rules lack are good missions, included with the rules. Haywire comes with 23 (to start with, as this is still beta).

There are a number of card decks that you use in Haywire and one of them is the Operations deck. (The rules include separate images of the cards so you can print them out.) Fortunately, they also include a separate PDF listing out the 23 missions so you don't need to print out the deck. The author has stated that this is one area that will continue to expand as he thinks up more mission types.

Let's start by discussing a couple of example missions.

Every "operation" (mission) contains an objective and setup instructions. As you can see with this mission the opposing forces include a surface-to-air missile launcher and the team is sent to destroy it. The setup instructions tell you to place three objective tokens in the open, some additional parameters to the mission (no support), and how to destroy the objective.

This mission, which was the one played in the video, calls for finding and eliminating the enemy leader.

How are the Opposing Forces Selected?

There are three "factions" defined in Haywire: (Western) Task Force, (Russian) Spetsnaz, and Insurgent. Interestingly, the first two are player factions, so no US versus Russia missions are defined in these rules.

Haywire bills itself as using classes, which are essentially profiles that you use for figures. The player factions have classes for Demolition, Automatic Rifleman, Marksman, Medic, Assault, and Team Leader. We will look at their profiles later. The Insurgent faction has the profiles Fighter, Gunner, Sniper, Rocketeer, True Believer (complete with bomb vest), Advisor, Executioner, and Cell Leader.

The next step is to create the Threat deck. Included in the game are two 1 Enemy, four 2 Enemies, four 3 Enemies, one 3 Enemies, 1 Leader, four Nothing, and four Civilian cards. You remove the one 3 Enemies, 1 Leader card and shuffle the rest. You then draw one card for every threat token, less one (for the card you have set aside). Those cards, plus the 3 Enemies, 1 Leader card, become the threat deck.

Whenever a threat token is then spotted by a player's figure, a card is drawn from the deck to determine what figures replace the threat token. If the card is one of the "enemy" cards, for each enemy figure you roll one D20 and look on the following table to determine what profile to use for that figure.

How are the Opposing Forces' Movement Determined?

There are five types of movement: threat tokens before the alarm is raised; threat tokens after the alarm is raised; enemy figures before the alarm is raised; enemy figures after the alarm is raised; and civilians.

Threat Token Before the Alarm is Raised

After the players take their movement the threat tokens are moved. If the alarm has not been raised a scatter die (the die on the left in the image below) and a D6 are rolled for each token. The token is moved D6 inches in the direction indicated by the scatter die.

Although random movement may seem rather nonsensical – guards don't walk in a different direction every turn, at differing speeds – it is better to view it as the player's perception of where they think the threat, which is out of line of sight, is really located. At least that is how I justify the mechanic.

If the threat token wanders into the line of sight of the player's figures, the threat deck is immediately consulted to see what the actually threat is, rolling on the Insurgent table to determine exactly which figure(s) to put on the board. Remember, it may consist of one or more enemies, a civilian, or nothing. If they are enemy, they first test to see if they detect the player's figure(s) by rolling a D20. If they do they may immediately act. (Note that player figures on overwatch may act first.)

Threat Token After the Alarm is Raised

Once an unsuppressed weapon is fired or one of the player's figures are spotted (not just in line of sight) the alarm is raised on the whole board. Once that happens each threat token moves 6" directly towards the sound of gunfire. As above, when the threat token comes within line of sight of a player's figure a card from the threat deck is drawn and any figures are rolled for and placed on the board.

Enemy Figures Before the Alarm is Raised

It is possible for a figure to be placed, but it not have been alerted to the player's figure's presence (it missed its spotting roll) and for the alarm to not have been raised. In those rare circumstances the procedure is actually undefined.

As you can see in the image above, each Insurgent card has a short program to determine how it acts. The first question is: "Is there an enemy in LOS?" Because the figure failed the spotting roll the answer is "No". It then tells you what you should do in relation to the "last seen enemy or where the last gunshot was heard". But neither of those apply.

Thus, the question pops up as to what the figure does the following turns. Should we use the rule on page 11 that says "Once a model is alerted, he stops moving randomly on the board" to mean that, because he is not alerted, he continues moving randomly (D6 inches in random direction)? My first inclination, before I found that reference, was that they would continue on in the direction they were facing until they hit the boundary of the area they were patrolling/guarding/defending and then at that point roll for a new direction. I would think that once a figure is revealed its movement might be more normalized.

Granted, this situation only arises when you are not spotted, but I could see where, if an enemy is walking away from you, and they failed to spot you, you might let them continue on. But if their movement is random every turn, you really can't take the chance and are almost forced to attack them. (In the video gameplay referenced above the author would always have multiple people on overwatch and they would pop anyone as soon as they were alerted.)

Enemy Figures After the Alarm is Raised

As shown in the image above, each figure "class" has its own program on how to act when the alarm has been raised. The first basic question is whether the enemy in in line of sight or not. If they are then it is generally whether the figure is in cover or not. (One exception is the True Believer card, which always moves towards the closest enemy, detonating his "S-Vest" when within range.) The second basic question is whether the figure is in cover or not.

Although simple, simple is good. There is enough of a foundation there if you want to add more factors to the program.

Summary

There are a number of other elements that I could go on about, but you should check it out on your own. It is free after all. Then there is the unintentionally hilarious video by the author. Boy his luck is just plain bad at times!

Hostile Tactical A.I. Review – Part 1

Hostile Tactical A.I. (HTAI) is an solo gaming system to order enemy units around in skirmish miniature wargames, so you may play solo or co-op against the enemy. These are not intended as a complete set of rules, but rather a game mechanic that you need to graft onto whatever skirmish rules system you are using.

In general I do not like to give away too much information in my reviews, especially about game probabilities, but given that so much information is in the cards and not the rules, I feel like I am not cheating the author in talking a little more about the math behind this system. Let me know if you think I let too many cats out of the bag.

Concept

The system works through a deck of 72 cards each of which is used to tell you where enemy models are to go and what they are to do. This is one of the harder problems to solve when playing solo. If you are using rules where not every model gets to act every turn the second problem to solve is which units get to act. HTAI gives you mechanics to solve that question also.

Included with the deck of 72 cards are three, double-sided rules cards, and three "shard" cards.

The Game Cards

The above image shows some sample cards. At the top left is a Reaction Order.

On the right of the top (blue) section is the symbol for a standard playing card, Jack, Queen, King, or Ace, in any of the four suits. This is used in conjunction with markers on the table of with the symbol assigned to a model.

The middle (white) section contains two orders. Which you use is determined based on a general situation of the model the card is drawn for; whether the model sees an enemy unit (Attack) or not (Patrol). The order text indicates anything special you might do, and how aggressively you do it (1D6 or 2D6).

The bottom (black) section has a compass direction on the left, a bit of text in the center describing an enemy's state or position, and a red and white die on the right. If you need 1D6 you use the red die and if you need 2D6 you add the red and white dice together.

As you can see, it is pretty basic, and every probability is baked into the cards.

Using the Game Cards

There is a tutorial PDF on BoardgameGeek that provides some examples of play. It is still very high level, but it gives you a better understanding of how to use them. Basically, once you have determined which model is to move you draw a card and determine its order based on whether it is in Attack or Patrol mode. Once the order is determined, generally you will need to determine which enemy it is taking that action against. You draw another card and look at the black section and either use the compass or the descriptor to determine the direction of any move. Finally, the original order determines whether the move is 1D6 or 2D6, so you draw a third card to determine the distance, indicated on the dice.

At times you will see an asterisk (*) on the card in the section you are using. This indicates that you should draw another card first, referring to the Reaction section. That card draw may in turn require more cards be drawn, which may in turn trigger more reactions. Just go with it.

Shards

No, we are not talking about a database partition here. The author uses the term "shard" to refer to little markers placed on the table to represent a variety of things, such as objectives, potential locations for enemies, or points of interest. Really, whatever is on the board that you want to randomize. As there are sixteen different shards, that is you maximum range of possibilities. Again, these symbols are on the cards, in the top right corner, so you can use card draws to add a randomizer.

Selecting a Model

As I said earlier, the two largest issues to solve for solo games are: which model (unit) acts next, and what does that model (unit) do? HTAI jumps straight into solving the second issue (what does that model do), but it only lightly touches upon the first.

If the number of models that the automated side has numbers 16 or less, it should be pretty easy to simply assign one of the shards to it, then use the deck draw to first determine which model acts, then follow the process above. If the model count is too high then you could assign shards to groups of models, draw a card to determine the group, assign shards to the models in the group, then draw another card to determine the specific model.

Another possibility is to use the compass on a drawn card to see which area of board will act, then using additional cards to hone in on the model.

In essence, the exact method is up to you, including not randomizing the choice at all.

Toolkit Not a Game

The important thing to recognize is that HTAI is a toolkit that you have to integrate into the specific set of skirmish rules you are using in order for the cards to make sense. Although there are some specifics on the cards that seem to imply a game rule, such as the distance moved (indicated by the order and the dice), these two need to be "translated" into whatever rules you are using in order for it all to make sense.

Test Game

Before I give my rating on HTAI I want to use them in at least one game and see if what it looks like on paper matches what happens on the table. So for my test game I am going to use HTAI with One-Hour Skirmish Wargames (OHSW), which I recently reviewed on my other blog. (Part One, Part Two, Follow-Up) It might help to read at least Part One in order to understand the OHSW rules as essentially I will be integrating HTAI and OHSW together.

In my test game I am going to be running the same scenario run in Part One and Part Two. I will be making one modification to the scenario, which should have no bearing here, regarding the firing rate of gunpowder-era weapons. I will not write out the entire game as I typically do, but focus in detail on how I translate the cards in HTAI into actions for the British side in OHSW.

Integration Notes

Given that the British have fewer than 16 models, I will assign a different shard to each model. This will allow me to draw a HTAI card at the start of each British Action Phase to determine which model will take action. Then based on the orders in HTAI, it will consume a certain number of OHSW action points (AP). If there are points remaining I would then draw an additional HTAI card to determine the next British model to act (it cannot be one of the models that have already acted in that Action Phase). As casualties mount, I will more than likely have to draw multiple cards before I get a shard designating a model still in the game, but that is just a guess.

Given the ground scale of OHSW I will have all British models in Attack mode rather than Patrol mode. This will save me from having to consider who is in and out of line of sight, who that is out of sight has and has not fired, how much noise has been generated, etc. all of which HTAI seemingly takes into account. Too much detail too early on. So, the position designations (text in the center of the black section of the card) will be used to see which model the British model attacks. (An asterisk in the compass will be applied to the position designation.)

Movement distances in OHSW are fixed. Infantry move 6" per move action. I could use the dice roll to simulate a model's hesitancy in moving, but that implies a morale and/or terrain difficulty aspect that takes no other factors into account. I am not sure I like that, especially as the French (player) side would not be bound by that limitation. However, OHSW does have the concept of multiple moves being allowed a model, assuming it has enough action points to complete them. If a 1D6 is indicated, I could allow that to refer to that figure being allowed a maximum of one Move action. The rationale being that even if you rolled a maximum of '6', that is still only a single Move. However, if 2D6 is indicated, if the player draws a '7' or better, this allows for two Move actions to be performed by the model, assuming the British has the necessary action points remaining.

Generally speaking, the Attack Order contains a modifier, indicating the aggressiveness of the order. This will be followed as accurately as possible, but until I play through all of the options, I won't know if I have to fudge a bit.

Many of the order indicate 'objectives'. The intent is to use shards to indicate objectives, so that a card draw can determine which way a model moves, but there is only one physical objective for the British in this scenario, so if the objective is mentioned, it means the cannon in the center of the board.

Well that should cover it for now. The next post will go into playing the game using HTAI as the 'artificial intelligence' for the British player in a scenario using the OHSW rules.

Rally Round the King Redux

First, let me start by welcoming new readers Shelldrake, Los, Robert Saint James, and Spacejacker (like your blogs and the Gut Check rules look interesting). Hope you enjoy the blog. Also thanks to JF for plugging my blog on his blog, Solo Nexus.

So, as you may have guessed, I have decided to give Rally Round the King (RRtK) another try. I'll be using Comic Life 2 for the graphics and narrative, only breaking out to text for discussion about mechanics. I've modified the blog to be about 900 pixels wide, so those with 1024 by 768 resolution should have no problems reading it without having to scroll back and forth. The comic panels should by 800 by 600 pixels, so it should display in reasonable chunks and again not requiring scrolling to see it full size.

Rather than going through the same exercise as last time for terrain and deployment, I will use the same rolls, events, and results. So the troops will still be set up using the same parameters as last game, but I can alter deployment as long as I stay within those parameters.

What I need to change is to ensure that I don't trap troops so that they have no room to maneuver. Primarily this was the Spanish Cavalry (with General) and to a lesser extent the Roman Cavalry (with General). To this end I found that 'missing rule': Expansion.

Assume that the unit in the rear is to close to the line in front of it. It can neither wheel left nor right, and a facing change of 90º is not allowed. So it appears that the unit is stuck, unless the line moves forward.

However, the expansion rule allows a unit from the rear ranks to move out to the flanks, so long as the distance does not exceed the unit's movement. So to solve the problem above, the unit first moves forward into contact with the body to its front.

The following turn, the body expands, allowing the unit to move out to the flank. Note that it can do this even if the body is in melee contact (and is the primary way to expand the battle line and attempt to overlap your opponent).

Another rule that will come into play is Facing the Enemy. This rule states that if a unit is facing an enemy unit and is within charge distance of that enemy unit, the unit's choices are to move forward or remain stationary. I asked on the Two Hour Wargames forum if "remaining stationary" meant that it could voluntarily halt (it is not one of the reasons that is listed on why a body halts) and the answer was yes. So that changes the possible responses in the movement decision tables that I was describing in a previous blog entry.

In gameplay I will play the missile rules as designed, no moving and firing. Also, like Drums and Shakos Large Battles (see my Dale's Wargames blog for the review and playtest of these excellent Napoleonic rules), I have to be meticulous about not being so generous with the movement. It irritates me that a 15º wheel penalizes a unit as much as a 45º wheel, but that is the way the rules are. Units basically move straight forward until they collide, unless they are skirmishers.

New Decision Charts

As I indicated in a previous blog entry you can use the same Reaction Test mechanism to make the tactical decisions that RRtK does not make, namely:

• Was a unit to be activated?
• Did a unit move the minimum, maximum, or some value in between?
• Did a unit maneuver (move other than straight forward)?

It occurred to me, however, as I was drawing the tables up that I was violating my most basic rule of solo gaming, which was not to alter the game rules substantially, especially where you are messing with the math. By determining whether a unit made an optimal move or a sub-optimal one based on passing its ability score on two, one, or no dice, I was in effect making a morale check to move!

It seemed novel at the time the idea sprang upon me, and to be honest I think it would make for a fun method for programming an opponent, but I think those sort of rules would also need to be applied to the player's force in some way also. Making movement morale-based is a big change and not something you would want to apply unequally. (Of course, it really depends upon what you are looking for in your games. In this case, it was not to deviate from the Rules As Written too much. I did that last time.)

For this game I decided to go back and use Mythic for the three decisions above, however I tended to state the questions much simple, like: "Do I activate A, B, and C" this turn?" If that failed then you can always assume it was just one of those three that made it a no (unless it was exceptional, then it would be two).

On with the Battle!

[1] Rather than rely on the trick to move up to a second rank and expand on the following turn (as indicated at the beginning of the blog), I decided that the General and Cavalry bodyguard would need to be on the flank of the battle line so that when it moved straight forward it would already be in position. The Light Horse on the left, being a skirmisher, could easily maneuver to wherever it needed to go.

[2] This was due to the deployment rules stating that the unit needed to be in the left section. In the initial game I had simply placed it to the left, but not in the correct 8" wide section. This creates a sizable gap ...

[3] As with the Spanish General, the Roman Consul with his bodyguard positions itself so that a simple move forward puts in on the flank of the heavy infantry, rather than requiring an expansion to come up from the rear rank.

The exchange between the skirmishers in the woods show how important support can be. The Roman Velites both fired, but inflicted no hits on the Spanish. Nonetheless, the Spanish had to take a Received Fire test. I rolled double '6' for the check. Because the unit on the right had both rear and flank support it held (with two passes), however the unit on the left only had flank support so it had two failures and routed!

This makes me wonder about the definition of "support" and how I placed my troops. I assumed that because the scutari in the second rank was only in corner-to-corner contact that it would, at best, only provide flank support. However, you cannot support from the same flank twice. (Or am I thinking of DBA?) If I had placed my figures as shown to the right, the scutari should have been able to provide rear support for both, meaning neither would have routed in this instance.

Is RRtK more nuanced (or fiddly) than I thought or am I simply filling the holes in the rules with logical extensions?

As you play with RRtK (or other THW games) more, you realize that you really need to be careful and make sure you take all the tests necessary. Charges, for example, can go very long distances as you charge, react to received fire (allowing you to advance again), which is turn can cause another test, and so on. Charges double the distance allowed are very possible.

Another nuance to these rules to be aware of is that dual-armed troops are melee troops, thus are not subject to the Mandatory Fire rule. This effectively means that dual-armed melee troops cannot fire unless dictated by a reaction test!

It is also important that you get the unit activation sequence correct. If you don't, you can get some odd results, like this next turn ...

 If you didn't catch what was wrong, then good!

[4] Even though the Spanish General passed his reaction test, mounted that do not rout their infantry opponent must retire, taking one hit as they retreat.

The skirmish in the woods shows how successfully passing several Received Fire tests can result in units being mauled in missile exchanges. In this case the Spanish kept passing its tests despite getting hit each time. It finally had to retire. All of this is out of the hands of the gamer (solo or otherwise) of course as it is built into the reaction tables.

As you can see, a little more of my love for DBA slipped in. I cannot help but think of flanking an enemy and forcing him to react to you as 'Barkering'.
At this point I was starting to be amazed how the Spanish were standing up. Melee troops can stay in melee as long as they don't fail two dice, not one, so they have some real staying power. I was beginning to question the armor class (AC) rating I have given the Republican Romans, but as I was playing the 2nd Punic War, it is right. The reason for the pause, however is because the Spanish have to roll a '5'+ to get a single hit while the Romans get a hit on a '3' through '5' and two hits on a '6'! This makes it very hard for the Spanish to win in melee (as it should).

Now that the main battle line has routed, the end is probably near. However, as an equal number of Spanish scutari and Roman hastati have routed, it might be tough to call this one.

[5] Normally a unit firing missiles can only inflict one hit per unit firing. Further, because the 'arc' of fire is so limited (straight ahead) this picture would lead you to believe that only one unit could have fired and that the two hits are a mistake. However, I did not show each step of the process to charge, fire, and melee. When the cavalry unit charged the Spanish, it was overlapped by both units; thus both were eligible to fire. When melee came around, the cavalry unit is forced to line up on one or the other, which is what the picture shows.

[6] Yup! Both rolled a '6'. Apparently those dice needed to be switched out, however, and they kept rolling double sixes ...

I decided to call it quits at this point. The good thing about solo gaming is that it is not a competition (although it may be part of a campaign), so eking out every last victory point is not necessary. The Spanish had lost two slingers, one caetrati, and four scutari. The Romans had lost one velite, two hastati, and one equites (cavalry). The Spanish can certainly feel pretty good about how well they did in open battle. Nonetheless, I think the Romans can be declared the victors.

Summary

The best aspect of RRtK is the grinding, attritional feel of the game. (I just need to work on getting that feel without markers or rosters in my other games.) Sometimes I feel like the reaction results do not have enough granularity of result; it sometimes feel like all or nothing. Maybe I am talking heretically, but what is wrong with using three dice, or more?

Game play still feels stiff and rigid, however, because of the lack of maneuverability and fire arc. Given the small width of a base, I could see where people might argue whether a unit is within the arc or not for firing. One degree off and you get no fire.

Although I did enjoy this game, I would probably take elements from these rules and use them in another game rather than the other way around. There is some good stuff however.

Other Decision Making Methods

What I would like is to use another decision-making mechanism for a replay of the last battle, rather than simply repeating the use of Mythic to make decisions. Although I have no problem using Mythic, especially for the major decisions of battle tactics and troop deployments, but it gets tedious answering four or five questions each turn just to simply verify the most probable course of action. (Although it does have the interesting side effect of introducing random events into the game.) So, I started breaking out the old stand-by books, like Charles Grant's Programmed Wargame Scenarios and Donald Featherstone's Solo Wargaming looking for ideas. One thing I have found with the 'old school' authors is that, because they wrote their own rules to use, they had no problems introducing new mechanisms that completely altered what I call 'the math of the game'. Examples would be chance cards, tactical cards, regimental cards, etc., all which would modify the core rules in some regard, such as adding +1 to melee combat or subtracting -1 from a morale check.

I thought about adding some of these types of rules, but to be honest they start to get hard to remember. (I am old and forgetful, after all.) Some ideas you might want to toy with:

• Allow a unit to be a little better or worse on this day of battle: for example, roll 1D6 and on the roll of a '1' the unit is -1 REP, while on the roll of a '6' the unit is +1 REP. This should probably only be done for a few units and not the entire force.
• Allow the unit to adjust their AC +1 or -1 using the same method above. This adjustment to AC is only used for determining casualties in missile and melee combat; movement is not affected.

Another way is to alter the actual game mechanics in small ways.

• Each time a body moves roll two differently colored D6, designating one as 'Fast' and one as 'Slow'. If the Fast die rolls higher than the Slow die, +1" of movement is added to the maximum. If the Slow die is higher, -1" of movement is subtracted from the maximum. (Remember, the minimum move is ½ the maximum.) If any portion of the move is in non-open terrain (or across a linear obstacle), you can change the meaning to something that makes movement even slower on average.

If you are really bold, you can alter the mechanics even more.

• For heavy infantry movement, each turn roll 2D6 - 1 for  the maximum number of inches the body can move. For light infantry use 2D6 + 1 and for mounted use 3D6 + 1. Terrain will slow the body down by removing the lowest rolled die.
• Set a maximum number of dice in a pool for an army. The number of represents the fatigue and 'heart' of the army; the more dice an army possesses in their pool the more heart it has and the more fatigue it can accumulate. Each time dice are rolled for any reason they are permanently removed from the army's dice pool, never to be used again (in that game). So, if an army has 100 dice in its pool, it will only roll a total of 100 dice before the army collapses in defeat.

I prefer to minimize the amount of modifications I make to the core rules, especially something that alters the math of the game, and I don't like trying to remember lots of special rules that don't apply to all of the units of the same type (or at least appear the same). There is one area where I think you can add a little interest and not throw off the game too much: re-rolls. There are times when you really want to re-roll a failed die roll at a critical point in the game. Just as the suggestion above indicates you can create a dice pool, you can create a re-roll pool. The idea is that you have a certain number of dice that can be re-rolled during the game. For example, if you have two re-rolls in your pool you can designate any die rolled to be re-rolled, discarding one die from the pool each time you use a re-roll. (You may want to place some limits, like no die can be re-rolled more than once and that the second die roll stands, even if worse ... but you may not!)

One concept that I liked from the game Memoir '44 was that there are these cards called Combat Cards which make small modifications to the combat when the player uses the card (for example, adding one die to combat or reducing the opponent's attack by one die). This alleviates the need to remember which unit has this modifier; it is assigned when the card is played. The interesting part was that theses cards were accumulated primarily by playing cards that are generally considered the worst cards. So basically, if you got dealt a bad hand of cards you could offset your luck by accumulating Combat Cards. You can use the same concept for re-rolls. Each time a player fails both dice in a reaction test and does not use a re-roll he gains a free re-roll to use later. Simple to keep track of and not very over-powering.

In the end, however, most of these methods simply add a chaos factor to the game and make it less predictable, which is interesting for the gamer. But rarely do they add to the type or number of decisions that the solo gamer has to make, nor does it help him to objectively make that decision as if an opponent had made it. So far, the only two decision making mechanisms this blog has explored are rule-based and probability-based. These two methods have several factors in common:

1. They use logic as their basis.
2. They take into account all of the current factors in play.
3. There is a degree of interpretation of the results.

Generally these are all good points to a system - one doesn't want to play again dim-witted or irrational opponents, for example - but sometimes they can lead to predictable play. What would be ideal is to find a tactical decision making method that meets the following criteria:

1. Very quick resolution.
2. Little is left to the interpretation of the player.
3. Some element of surprise is introduced.

Decisions, decisions ...

First, let's start by examining the decisions that needed to be made in the last game.

• Was a unit to be activated?
• Did a unit move the minimum, maximum, or some value in between?
• Did a unit maneuver (move other than straight forward)?

These three decisions encompassed all those made post-deployment. The rules took care of the rest (who to fire at, the effects of fire, who to charge, the effects of melee, etc.).

Was a Unit to be Activated?

This decision is one of the tougher ones in that it is a 'decision bundle', or a group of decisions, and each combination of decisions can produce a different result. For example, if you have units A, B, and C but can only activate two units in a turn, your choices are: none; only A; only B; only C; A and B; A and C; or B and C. Seven different choices. The combinations get even more complex when you have 12 units and three activations.

Did a Unit Move the Minimum, Maximum, or Some Value in Between?

How much a unit moves is largely governed by its intent. A unit of heavy infantry intending to close into melee would rarely want to move less than maximum speed. Moving less potentially puts the unit under more missile fire while it closes and  allows the enemy more time to react to the attack, bringing up supports.

A unit providing flank support, however, may want to move less than maximum movement, especially if moving faster will cause it move past the position of support (i.e. get ahead of the unit being supported). This is especially true of light infantry or cavalry, supporting the flank of heavy infantry, which move much slower.

Another reason for moving slower is to delay melee combat, allowing the unit to fire missile weapons more often. Generally speaking, however, if you are moving the minimum, you are probably trying to delay impact. This is useful even for troops without missile weapons, if your troops are heading towards an impact you are likely to lose.

Did a Unit Maneuver?

Generally speaking, this is not much of a problem for armies with lots of non-skirmishing units. Maneuvering is a good way of 'bleeding off speed', but that seems like a cheesy reason to do it. More likely you are reacting to a unit that advanced too far and got flanked. Cavalry, however, does has a modicum of maneuverability.

With skirmishers, however, this is a big decision. Generally it is easier to ask the question in terms of "where on the board (and facing which direction) do I want my skirmisher to end up at?"

Charts, charts, and more charts ...

If you don't like charts, don't play Two Hour Wargames rules. They love charts. The reaction system is essentially programming a unit's set of possible responses, assigning probabilities, and codifying it in a chart. Mythic uses charts. One thing that kept leaping out at me while reviewing the old masters (and 12 issues of Lone Warrior) is that solo gamers seem to love charts! So maybe our mechanism should be chart-based!

So, what are charts? As I said, they are a codified set of possible responses with assigned probabilities. If 'X' happens on the roll of a '1' and 'Y' happens on the roll of '2' through '6' you have defined two possible responses to whatever the chart represents, and assigned the probability of each response. As long as there are not a lot of modifiers to the die roll, charts meets the first criteria of 'very quick resolution'. Unless you have done a poor job of defining terms, charts also meet the criteria of 'little left to the interpretation of the player'. Whether or not the criteria of 'some element of surprise is introduced' is met all depends upon whether you allow for a response that is generally outside of the norm (but still possible).

Let take a concrete example. The Roman heavy infantry (Principes) were assigned to advance directly towards the enemy in the center and attempt to penetrate their line. As they have no missile weapons, and the enemy do, there is little reason for them to delay (i.e. move less than a full move each turn). So, given an enemy unit straight ahead of the unit, the range of their responses is:

• Move the maximum movement allowed straight ahead.
• Move the minimum movement allowed straight ahead.
• Move some distance between minimum and the maximum allowed straight ahead.

Note that there is no option to not move at all; halting is not a voluntary option, save if the original activation order specified a point on the board where the unit was to stop ¹. Again, if you think of moving maximum as the default choice, what would the exceptions to moving maximum be?

• When facing a missile unit and the maximum move would not take you into contact, but would take you into its missile range, you want to stop outside of missile range, if possible (i.e. it is still within your minimum move distance).
• When moving less than the maximum move (but at least the minimum move) distance would allow a friendly unit to catch up and provide support.
• To expand the formation to avoid overlaps in an upcoming melee combat.

Of course, if the unit no longer has an enemy directly ahead, the options change. But for now, let's consider this simple case. How best to represent the decision making process for which option to use? Interestingly, Rally Round the King (RRtK) provides a good one: the reaction check. Think about it. How I move in relation to the enemy is a reaction. So why not use the reaction check mechanism for making this decision. In fact, basing it on REP (with attendant pluses and minuses due to hits and support) makes sense in this context and is something we have probably already memorized. So, you might have the following for the Roman heavy infantry:

Reason	Pass 2D6	Pass 1D6	Pass 0D6
Center Battle Line Moves	If outside of missile range and overlapped, expand.	–	If overlapped, expand.
	If outside of missile range, a unit that can provide support needs to catch up to provide it, and a minimum move will allow that unit to catch up, move the maximum distance that will still allow the unit to catch up.	–	If outside of missile range, a unit that can provide support needs to catch up to provide it, and a minimum move will allow that unit to catch up, move the minimum move allowed.
	If moving the maximum distance allowed takes you into enemy missile range, but not into contact, move just outside of missile range if legal.	If moving the maximum distance allowed takes you into enemy missile range, but not into contact, move the minimum distance allowed.	–
	Move the maximum distance allowed.	Move the maximum distance allowed.	Move the minimum distance allowed.

There is really no limit to the number of tables that you can do like this; just keep them separate from the normal reaction tables so you don't end up flipping around too much.

Mind you this takes some work beforehand, but all good things typically do. This falls in line with my idea of writing out a detailed battle plan and then writing a decision-making process to go with it. I think that for the most part, however, this can be reused quite a bit. The result will likely be the Typical Army Behavior Jay referred to in his blog entry and the Enemy Behavior in Action article referred to in issue LW 166 of Lone Warrior.

One of the reasons I like this method is because it is so THW-like.

¹ Update: I posed a question to the Two Hour Wargame forum and there is another way to voluntarily halt. As I am only presenting ideas here and not complete solutions, I am choosing to ignore this other option for now.

Solo Gaming and Reaction Systems Test (5)

I decided to continue on a little more. It appears that I made two (more) mistakes, one of which were some missing pages.

Roman Turn 2

The Roman Velites were a little beat up (two hits each) in the initial skirmish, having lost in an exchange and been forced to retire. Everything else had not moved.

The basic idea was to advance with the main battle line full speed and have the two wing groups advance, echeloned slightly back. However, the Balearic slingers were in a vulnerable position, with the flank facing the Roman cavalry on the other side of the hill and already having accumulated two hits. So I decided to see if the Roman commander would launch the cavalry for a quick kill.

Given that the Velites retired and no other Roman troops advanced the previous turn, the Roman commander would have to use his three activation points to order the advance of the main battle line and wing supports, so a cavalry attack would mean something else would not activate. Further, due to the position of the Roman commander with relation to the enemy slingers, he was not really in a position to see the vulnerability, nor were the Roman cavalry (due to the intervening hill), so I rated the chance for this cavalry attack to be low. The roll was not sufficiently low enough so the same choices as last turn were presented and accepted (only without an event interrupting the battle plan).

First to advance were the Velites, who made the edge of the woods. In visibility of the enemy skirmishers, but out of missile range. Next was the main battle line. This advanced at full speed, causing the Spanish on the left flank to make a Threat check, but it was passed without a problem. (Had the Romans advanced to within 3" missile range the Spanish would have been able to fire. Note that had the Romans has sufficient movement to either move within threat range but out of skirmish fire range, that would have been an additional decision to be adjudicated. As it was, they were just in Threat range and sufficiently out of javelin range.)

Spanish Turn 2

With all of the Romans so far away, the only logical move was for the slingers and caetrai to get back in action. No exceptional rolls indicated that any other unit would be brought forward yet.

First the slingers moved back into position in front of the Roman Principes. (Still playing the move and fire rules.) The slingers let loose on the Principes, missing them by a hair, but close enough to irritate them.

The Principes rolled an Advance ½ Move result which would have put them past the slingers, so this requires an additional Want to Charge check, which they pass with ease.

The slingers pass partially and fire their slings one last time and head for home. At least they inflicted a hit first!

The Spanish caetrati move against the Roman velites and chuck their javelins, inflicting a single hit. This is enough for the Romans, who roll badly and rout off of the board.

Meanwhile, the scutari chuck their javelins at the flank of the Roman battle line and get suitable attention.

The Romans turn to flank and get an Advance ½ Move result, but fail their Want to Charge test. Here is the situation at the end of the turn.

The Spanish battle line must definitely advance next turn, assuming their reaction to the Roman advance doesn't spoil their plans.

Roman Turn 3

With one wing gone and the main battle line out-pacing their supports, it is time to throw the cavalry forward, before they get far behind. The main Roman battle line is already in motion, so it does not need to be activated; nor does the Hastati on the hill. However, the Principes that turned to flank halted when attempting to charge, so it needs to be activated, as do the two cavalry units. As the Roman commander can activate three bodies, he can activate all of the halted bodies if he wants to. So, is there any reason why he should not activate anyone? A roll of the dice indicate all are going in, however both cavalry units are to merge at the top of the hill on the (Roman) left flank. Note that this "condition" means the body will halt upon reaching its destination, so is akin to moving the reserve.

The poor hapless Romans on the right have heard stories about what happens to soldiers in the woods! They refuse to charge once again.

In the center the Roman line charges and the Spanish stand and fire. The javelin fire is murderous, inflicting one hit on each Principes unit.

The Spanish take the worst of the clash, receiving more hits than taken, but they hold. The Romans left-center, however, has taken too much and gives ground.

Meanwhile, on the Roman left flank the Hastati advance, threatening the scutari guarding the flank, but not in range of being fired upon. (The Romans had a choice here and Mythic indicated that it made no sense to expose the troops to fire.) The Spanish morale held in the Threat check, however.

On the hill, the first of the Roman cavalry units arrives, with the General still out of view of much of the battle.

Spanish Turn 3

The situation for the Spanish actually looks pretty good. Although both sides have lost two skirmishing units, the Romans have been hurt a bit by javelin fire from the Spanish scutari. It will be interesting to see how the Spanish commander acts.

Let me apologize right now for the total screw-up of this game. Thank goodness I was not reviewing and playtesting these rules! Also, I am experimenting with some new software, hence the sudden change in appearance of the graphics. I use a Macintosh, but own some graphics software for Windows which I am very comfortable with, so I tend to use them using Windows 7 under VMware. I finally decided to bite the bullet and search out some graphic software for the Macintosh to replace my beloved copy of Macromedia (yeah, it is that old!) Fireworks so I could do everything in the Macintosh environment. I used Preview to crop pictures and lower the resolution, then used Comic Life 2 to assemble it into a "comic". I think I like the effect, but I am not sure yet. I still need to tweak the page size and resolution so it is not so large. But, you tell me what you think. I think that the comic can provide the visuals and the narrative, while the surrounding text provides the dry descriptions of the solo mechanics.

Summary

I think, in hindsight, it was a mistake to allow missile units to move and fire, but only another game will tell, and to be honest, I am not so sure I am fond of these rules. I think I am just too used to DBA and how they play that it is hard to wrap my mind around how these should work.

Clearly I made mistakes in decisions.  Units move much more quickly in these rules, so you cannot afford to dawdle. The key is to put units in motion, but not too soon. You can always slow a unit down to ½ speed if they are outpacing supporting units.

The biggest problem (but I am sure is a design decision) is that units are not maneuverable. I noticed this when I was considering what to do with the Spanish General. It could not wheel left or right 90º (it was trapped by the Spanish scutari line in front) and a 90º face, lateral move, oblique move, and pivot are all not allowed by any troops. I was too bunched up on the Spanish baseline (which was also a function of the smaller board size). Very different from DBA, of course, which allows a single element to move freely. I am not sure which is more realistic.

The Romans lost because the battle line did not expand frontage after they passed through the pass between the woods and the hill. This meant that in the first round of melee it was two units facing three and in the second round, three units facing one. The Romans simply got crushed at those odds.

On a side note, Ed from Two Hour Wargames just announced a new, free addition for Rally Round the King. Here was his press release.

Dave Gray, the co-author of RRtK is working on 120 historical armies spread over four periods. The RRtK Historical Sampler (see the picture on the [THW Yahoo] group home page) should be released within the week. It has 12 historical armies and a new campaign system called the Local Campaign.

Look for it as a free PDF.

This may be just the impetus I need to give these rules another go. That and reading the rules a little closer. All in all, I would probably have to tweak these rules so much that they would not look like the originals. At that point it would only be confusing to someone who uses the Rules As Written.

Looking Forward

I need to find another mechanism to study. There are few rules out there that claim to be solo friendly. As I have been delving deeper into solo gaming I am finding more mechanisms that are solo unfriendly than the opposite. Suggestions are always welcome.

At some point I need to tackle a mainstream game and do something more than simply "play both sides to the best of my ability". That works, but not for long.

Solo Gaming and Reaction Systems Test (4)

New Readers Welcome

Welcome to new readers JF and Jacko. Hope you like the blog.

 Preliminaries

Shaun brought up some great points in the comments on the last blog entry, mainly that I was playing the rules wrong! Using the provenance of Rally Round the King (Warrior Heroes before it and Warrior Kings before that) he showed that there is no concept of moving and firing and therefore no concept of voluntary fire.

I'll be honest, that rule is bad design and now reminds me of why I set these rules aside.

1. It does not model skirmishers very well, which generally use movement as a defense mechanism.
2. It does not model mounted skirmishers at all.
3. It creates a reverse Gotcha'! with skirmishing against heavy infantry.

What the Heck is a Reverse Gotcha'!?

The first time I heard the term "Gotcha'! Gaming" was from Wally Simon in the old PW Review gaming journal. It basically describes the effect of the worst type of IGO-UGO games (which Two Hour Wargames professes to cure with their reaction system). Take a certain space fantasy miniatures game that is tremendously popular. Their rules allow side A to move up into weapons range of their opponent, fire to full effect, remove casualties from side B, all before side B can do anything. Gotcha'!

A reverse Gotcha'! comes about when you change the action allowance from move and fire to move or fire. Side B gets to yell Gotcha'! when side A moves into range. In RRtK this happens with missile troops if they cannot move and fire. They are forced to stop when within missile range (3" for skirmishers), but if they cannot fire they will get charged by the enemy. So they will have to pass a Being Charged test, which is pretty hard for a thin line of skirmishers. Even if they succeed in the test is it not possible to fire in defense (they are not Dual Armed). Essentially this means that there is no offensive missile fire unless the enemy chooses to stand there in front of you and take it and no defensive fire for skirmishers. Found a missing page!

I think I have shown the concepts that I want to with these rules, which is primarily how to use Mythic to make major decisions like deployment, battle tactics, and precedence for receiving activation (PIPs in DBx parlance).

Given that these rules are broken, I will pass on completing the game. I know that NUTS! is not broken, and I do want to do a skirmish game, so I may pick up the reaction system banner on them soon.

Solo Gaming and Reaction Systems Test (3)

Welcome to new reader 'Lone Wolf Warrior' (aka THAT Graham Empson). Hope you enjoy the blog.

With deployment out of the way it is finally time to get stuck in. As the Romans are attacking, they get to move first. Here is the troop disposition at the start. The Romans are at the top and look "blue".

The turn sequence in Rally Round the King (RRtK) is basically:

1. Indicate the body (group of units that are touching) that is rightmost and in the front.
2. If it is not active, the player may spend a point of War Rating to activate it.
3. If activated, move the body.
4. If within missile range of an enemy, it will fire.
5. If currently in melee, it will resolve that melee.
6. If any movement, charge, melee, or fire causes Reaction Tests, these tests are taken.
7. After all actions and reactions are resolved, move to the next body. Activation moves from right to left; front to back where two bodies are equally distant from the right flank.
8. When all bodies are complete, the players turn is complete and play passes to the opposing player.

So, one less decision to make (which unit to think about activating next), as it is governed by the rules.

Roman Turn 1

As the Roman NPG has a War Rating of '3' and there are five separate bodies, only three will be able to activate. As the Roman battle tactics (determined last episode) was that the wings would hold back, while the center attempted to penetrate the enemy battle line, they seem most likely to move forward. The wings are to guard against the main battle line being encircled, so they are next most likely, with the cavalry on the wide flank and in reserve the least likely to advance at this point. So I start asking questions and rolling dice.

The main battle line (Near Sure Thing), Velites (Near Sure Thing), and Hastati (Very Likely) are all selected to be activated.

 Every time a body moves it can elect to go from 50% of the slowest unit's maximum movement to its full movement. For the Romans, there is really little reason to go less than full speed, so the odds will be high. Starting with the right flank, the Velites roll first (Near Sure Thing) and get an Exceptional Yes (taken to mean that there is no cause to roll again until circumstances change), but also getting an even-causing doubles ('NPC Negative', 'Trick', 'Failure', roll indicated it was the Roman NPG that something negative happened to). I roll another die ('76') to determine how "negative" the result is (the higher the more negative) and come to a conclusion that the Romans were trying to pull a stratagem to steal a march on the Spanish (i.e. one free turn of movement) and it failed, back-firing on them. The signal was given and the Velites moved forward, but the remaining troops forfeit their activation.

Generally speaking, I don't like to 'break the rules' as they are given in a game, but I feel this result is justified. The RRtK rules say you can activate up to your War Rating, but it never states you have to use all of the points. In fact, as the battle goes on and all units are in motion, the Commanding General has little to do until he commits himself and his bodyguard to the fray.

Spanish Turn 1

Reviewing the battle plan, the left wing is to advance into the woods and secure it, then harass the Roman battle line from the flank while the slingers harass them from the front. When the Roman line is weakened, the Spanish Scutari and cavalry will counter-attack and sweep away the weakened units. The Scutari on the right are to fend off any opposition that attempts to flank the main Spanish battle line. This makes the three bodies to activate the left flank and the slingers. All others need not activate.

I ask the questions and get that the left flank will advance (Sure Thing), as will the slingers (Near Sure Thing). However, when asking whether everyone else would stand their positions (Likely), I got a No, so I followed up by asking if the Light Cavalry was to swing out to the right flank of the Scutari on the right, in order to guard against the flanking Roman Cavalry and received a Yes.

I follow these up with questions about moving maximum and receive Yes to the Light Cavalry and the left flank. The slingers in the center have two factors to consider:

1. Moving maximum puts them within charge range of the enemy battle line (6"), but not within missile range (3"), so it makes sense to move only 1/2.
2. Moving up will put them within missile range of the Velites in the woods, so they will have to stop and fire anyway.

As the Velites were within 1/2 move of the slingers, they could not stay out of their range, so there was no reason to ask a question about their move.

The Light Cavalry, being the rightmost to activate, moved to the right of the Scutari line and formed up as part of that body. (As they are skirmishers, they can move and face in any direction freely, so getting to that position is relatively easy.) At this point I consider the unit Halted and no longer active. Although you automatically halt when you reach a terrain piece designated in your orders, I have always interpreted this to also mean when you reach a designated station (such as at the end of a line).

The slingers move forward until they come within the 45º angle to fire and with only 1" of woods to pass through and then halt. Only the left unit can fire and it inflicts a hit on the leftmost Velite.

This is where the THW reaction system comes into play. The Velites have to take a Received Fire test to see how they react to being under fire. Their result was to return fire on the slingers.

The Velites return fire, inflicting a hit in turn on the leftmost slinger. The slingers now react passing once for the unit hit and passing twice for the unit on the right. The left slinger retires one move, unfortunately carrying it through the right slinger unit, which is a skirmisher, resulting in it routing (and being removed from the board). You can see it in the picture with two green dots (hit markers) at the foot of the hill.

The Caetrati and Scutari on the left flank advance into the woods, spotting the Velites – that clearly ambushed the slingers – toss their javelins and in the ensuing exchange, drive the Velites out of the woods (they retire, each with two hits).

This is not at all how I expected the game would go, at this point, but it is interesting. Results in RRtK tend to be very harsh and decisive. Just as small units don't survive well in some games, small bodies don't in RRtK because you receive a modifier to your reaction test for each supporting unit in contact with you, up to three. That effectively turns a REP 4 unit into a REP 7 unit.

Just a note about the Spanish turn. Let me say in my own defense that the bone-headed move by the slingers was largely due to my unfamiliarity with the rules. I view it as similar to when you learn in DBA that a unit recoiling into another friendly unit that is not lined up 'just so' results in the recoiler being destroyed. (By the way, that is not true in the new beta DBA3.0.)

Had I been more familiar with the rules I would have not tried to get fancy and have the slingers facing the Roman battle line while still firing at a flanking Velite; I would have faced both slingers at the Velites flank and been done with it. Not only would it have doubled the firepower, but the failed roll would not have routed the second slinger unit as the first would not have retired through it.

Ah well. It is one of those lessons you only have to learn once!

At this point I am stopping for the evening. I would like some feedback on whether it is better to get these 'episodes' in more frequent, but smaller chunks or just get it over with even if it takes a week (or more) to get it done. Let me know, either through email or a comment on the blog.

Solo Gaming and Reaction Systems Test (2)

Welcome to new reader "Lentulus". You may have to read back a few entries as I am going to jump straight into where I left off last time.

Troop Deployment

After terrain is decided and baselines indicated, each player starts placing troops. As neither side has significantly out-scouted the other each side places three units at a time, starting with the defender. On page 52 of the Rally Round the King (RRtK) rules, in the Solo Gaming section, there are recommendations on how to use "game driven forces" (i.e. programmed opponents) in deciding the battle tactics, troop deployments (in general terms, see below), and a basic narrative on how the battle should proceed.

The Spanish are rated Battle Tactics "C", which is an army defensive in nature that tries to weaken the enemy with missile fire. They tend to go for the flanks (which was established during our Q&A when the Spanish NPG was determining which baseline to take). A D6 is rolled and compared to a chart to find that the battle plan is 'Counterattack', or a defensive posture to absorb the enemy attack, then countering with a substantial reserve. The troop allocation is 60% of the troops to the center (of which up to 30% can be held in reserve), and 20% on each flank. As the Spanish have 12 units that is 2.4 – 7.2 (3.6) – 2.4 bases per section (from left to right).

The first task is to apportion the troops to each sector, then determine the order that they be placed. Note that the Commanding General must be placed in the first round. So, might as well figure out where the NPG goes first. Points to consider:

• Loss of the Commanding General causes a reaction check with the entire army, so do not commit him lightly.
• The stand with the Commanding General gets a large boost in REP (+2), so the unit will generally do what you want it to do (i.e. it will pass most reactions tests).
• The Spanish Commanding General is attached to the Heavy Cavalry, which is the most powerful unit on the Spanish side, so not committing the unit is a waste.
• Heavy Cavalry moved poorly through woods
• The Spanish Commanding General can activate up to three units each turn.
• The Reserve is the best place for a unit that can react well and can hit hard when it arrives.
• The battle plan calls for a counterattack once the enemy is worn down.

All of these factors point heavily to the Spanish Commanding General being allocated to the reserve, so there is little reason to ask anything other than the most direct question: Will the Spanish General be placed in the Reserve? (A Sure Thing 90%) Yes (rolled '74').

The next group to consider are the Balearic Slingers. This is a powerful missile unit (although rated as skirmishers) and their placement is considered of prime importance. Here are some points to consider:

• Skirmisher range is 3", so there will be no long range fire.
• You want to ensure that these skirmishers stay out of melee for as long as possible.
• Being uphill not only gives you a melee benefit, but a reaction check benefit as well; woods and open terrain do not.
• You cannot see out of a woods unless within 1" of the edge. Within a woods you can see up to 6".
• The javelin-armed Scutari have the same range as the slingers and both are +1 to the die roll, so they effectively have the same firepower.

The issue here is really one of whether you should send the slingers to the woods, to the hill, or in front of the battle line in the center. Given the short range, moving through the woods will not restrict the number of turns they can fire, but will likely restrict them to what they can fire at, given the visibility restrictions. Being in the open in the center gives no advantage compared to being on the hill, but units in the center will more than likely be facing off against the Roman Hastati, which needs to be worn down. On the hill, they would likely face the Roman cavalry and/or the Velites.

Question: Will the Scutari be used to secure the hill? (Likely 75%) Exceptional No (rolled '100').

So, what exactly does an 'exceptional yes' or 'exceptional no' mean? Generally, it means an emphatic answer. How that is interpreted is up to the player. In this case I interpret it to mean that not only will the Scutari not be used to secure the hill, but their reserve will not reinforce it if it is secured by other troops. The problem here is figuring out why they won't do this.

In addition to the 'exceptional no' answer, doubles were rolled. In Mythic this represents a chance that an event may occur. In our case, it has. A D100 is roll and looked up on the Event Focus table, another D100 is looked up on the Event Meaning: Action table, and a final D100 is looked up on the Event Meaning: Subject table. These three tables produce a phrase which must be interpreted and given meaning in context of the story. (Remember, Mythic is primarily a tool for narrative game play, so the story element is important.)

The phrase rolled for the Spanish: 'Move Away from a [Story] Thread', 'Neglect', and 'Goals'. (Okay, hang on a minute while I put on my tap dancing shoes. Time to get creative!)

So, the first part is to interpret what a 'story thread' means in the context of using Mythic as decision-making tool for miniature wargaming. Up to this point the narrative for the Spanish has been to meet three goals (story threads):

1. Secure the hill on the right flank and use it as a platform for launching missile attacks on the enemy battle line.
2. Secure the woods on the left flank and use it as a platform for launching missile attacks on the enemy battle line.
3. When the enemy battle is sufficiently weakened, counterattack using the reserve.

'Moving away from a story thread' is to de-emphasize one of those threads (but not to end it, that is another entry on the Event Focus table). In this case, one of the goals will be neglected. Put another way, a little bit of error, fog of war, commander incompetence, or what have you, has crept into the battle plan. So, which goal? Given that this whole mess started with an 'exceptional no' when referring to the hill on the right flank, it appears that the 'exceptional' part is that not only will the hill not be secured by the Scutari, it will not be secured at all. A question remains as to what 'secured' means, so we need to sort that out.

Question: Does 'not secured' mean that insufficient troops will be ordered to occupy it? (Likely 75%) Yes (rolled '28')

We already know that Scutari will not be used to secure the hill, nor the Heavy Cavalry, as it is already committed to the reserve, so that leaves the Light Cavalry and the skirmishers. As only 20% or 2 units can be committed to this flank, and that the two Caetrati units are the weaker of the skirmishers, it makes sense that they are the ones committed. Are the two Caetrati units to be committed to the hill? (Very Likely 85%) Exceptional No (rolled '99')!

Note that although doubles are rolled, this does not generate an event as the number in the one's column has to be equal or less than the Chaos Factor (which we have still to discuss), which is currently at '5'.

With two 'exceptional no' results, this is starting to sound very likely that no troops will be sent to this flank.

We have the answer from the RRtK rules that 20% of the force will be allocated to the right flank. We also have the answer that 'not secured' means 'insufficient troops', but I think it is safe to say that no troops qualifies as insufficient. We really only have three units left, the Light Cavalry and the two slinger units. Normally, as you keep asking questions like "is it this unit?", you increase the odds that it is the next most logical unit. However, that would be the process if the answers were simply "no". In this case, both answers were "exceptional no", so rather than choosing the next most logical unit, I think "no troops" jumps to the head of the line. So, I have to ask the question: Are there to be no troops sent to occupy the hill? (Likely 75%) Yes (rolled '31').

At this point it would be the responsibility of the battle report narrative to explain why this is going to occur. But the good thing is, we have something additional in our rule base to work with, for good or ill.

So, we are still left with determining which additional two units to place in the defender's first round. Also, two units must be allocated to the right flank, if we are to fulfill the indicated battle tactics roll made earlier. If we are not making an attempt to seize the hill we are presumably going to have a defensive line facing off against it, probably refused to the rear to avoid contact as long as possible. As skirmishers cannot hold against the Roman cavalry that is likely to attack on the flanks, it needs to be something more substantial. Again, the Scutari make the most sense. Will two Scutari face the hill in defense? (A Near Sure Thing 90%) Exceptional Yes (rolled a '6') I will take the exception to indicate that not only am I right about the two Scutari being in this position, but I have already assessed the plan with them; they are to refuse the right flank and ensure that the center is not attacked in flank.

At this point you might be thinking that this is way too much work, but it actually goes fast. The work is in writing this down for you and vocalizing my thought process. Mind you, that doesn't mean that nothing gets written down. Mythic includes some nice worksheets to help you remember plot lines, decisions, odds that you have set, and so on. I find them handy, even for miniatures play, but especially for a campaign, where the character of the NPG starts to come about.

We now have the right flank set, along with one of the reserve units. Unit placement rules in RRtK help me in some regards, as there is a minimum distance it can be from the sideline. Given the small deployment area, I will simply place the troops as close to the baseline as reasonable (1") and with a 1" gap between the troops and the line that divides the center and right sections.

Romans

Spanish

Let's look at the Romans' battle tactics. They are type A and their roll indicates that the plan is to 'Penetrate the Center' or have the heaviest melee units in the center with a skirmish screen. The wings serve to ensure that the center does not get encircled. 60% of the units are in the center with only 10% in reserve, and 20% on each flank. That is 2.4 - 7.2 (1.2) - 2.4 in unit distribution, from left to right.

At this point I will only point out exceptional events and die rolls.

Again, as the Commanding General must be placed in the first round, I determine if he is in the Reserve (to me, the most logical place) and find that he is. When it comes to deploying troops, I will save the flanks for last. I place some heavy infantry in the center and the board now looks like so.

Romans

Spanish

As we place three units each round, there will be a total of four rounds of placement. The idea is to keep building off of the previous decisions and in response to the enemy's deployment, if appropriate.

Rather than drag this out, the Spanish decided to attack a little more strongly on the left, sending their Caetrati and one Scutari as far forward as possible, to capture the woods and harass the Romans as they pass between the hill and the woods. The Romans countered with their Velites opposing them. Hopefully they will be able to occupy the Spanish sufficiently that the Roman line will pass through unscathed.

On the Roman left they opposed the refused flank of the Spanish with two heavy infantry and the Roman cavalry. The cavalry will attempt to occupy the Scutari while the Hastati flank the Spanish battle line.

In the center the Principes and Triarii (dark red) will march quickly forward and smash into the Spanish line. No real finesse needed here.

Romans

Spanish

Deployment is finally done and the battle plans laid out. The Romans will move first as they are the attacker.

Shaun (of the Shaun's Wargaming with Miniatures blog fame) made an interesting comment in that it does take time to blog out your games, especially when you are trying to put your thought process down too. I point this out not for sympathy or plaudits, but to assure those that read this that it really doesn't take that much additional time and effort to do something like this. In fact, if I gained anything from Bob's articles in Lone Warrior on NW frontier gaming using The Sword and the Flame and Mythic it was that over time you build up a "catalog" of sorts of tables, tips, tricks, and techniques all that build towards a richer gaming experience. I game solo not because I have no face-to-face opponents – I am blessed to have quite a few clubs and hobby shops within easy travel and can find more games to join in any given weekend than I can actually play – but rather that this is the only way I can get such a rich and detailed game that really only I seem to enjoy (around here). Like this blog, I do it for me!

See you next time. I have to carve some wood (see the Wooden Warriors blog) and sling some paint (see the Dale's Wargames blog). I hope to get another game of DBA 3.0 (the latest beta) and post that on the Dale's DBA blog. (Okay, I'm done plugging my blogs now...)