Having contemplated the role of choice in battle report writing for a long time, the six Salem Church battles (seven if we count the introductory tutorial to remote gaming for Andy) provide an opportunity to collect and reflect upon these thoughts in repeated trials. Players made choices. Dice made choices for the players too. Each contest produced different results. Once the fighting stops and the writer sits down to the keyboard, another set of choices begins. What are the choices a writer faces when reporting on a game? These choices revolve around how to report the six battles when the core situation or beginning state is familiar.
All battles began the same but each of the six battles developed its own narrative and character. The writer ought to identify the different challenges faced because differences make reporting a worthwhile exercise. Let me briefly summarize what I saw as the key theme of each battle before diving into my thoughts on writing.
They are:
• Sedgwick REJECTed at Salem Church centers on Richard’s decisive decision to disengage after seeing Bartlett’s Brigade wrecked in the early turns.
• Salem Church Game #2 sees Matt put Bartlett on the offensive rather than allowing the Federal Left to be overwhelmed. Here, the BatRep’s emphasis falls upon sustained aggression and the contrast with Bartlett’s experience in the first game.
• Salem Church: A Battle of Attrition follows Vol’s repeated attacks and the mounting losses that brought both armies close to breaking.
• Rematch with Matt at Salem Church begins with my decision to attack on the Federal Right rather than attempt to reproduce Matt’s earlier success with Bartlett.
• Rematch with Vol at Salem Church frames the contest around Vol’s return to Federal command and his attempt to improve upon a narrow defeat in our first contest.
• Last Stand at Salem Church introduces Peter’s observation that substantial Federal formations north of the road had not always reached the fighting. I expected that those troops would matter this time.
These are not simply six variations on “the Federals advanced.” Players choose how to fight the battle in their own way. Writers choose how to present it. Writers’ choices certainly influence how the battle unfolds in the reader's eyes. The writer’s decisions change the reader's understanding of the action but not the result. Each account can answer a different question. Choosing that question gives the BatRep direction.
Knowing the outcome further complicates matters for the writer. An unsuccessful attack can appear obviously a mistake once its outcome is known. It was not necessarily obvious when ordered. A case in point is when Matt and I swapped sides to replay the scenario. Matt’s earlier Federal victory offered a successful approach I could have copied. I chose another approach and got beaten again! My defeat did not prove that copying Matt would have worked better. We never played that alternative. In retrospect, my choice appeared viable at the time until Matt’s response muddled my plan.
This uncertainty also explains why I wrote my own account even when Peter had already produced his own riveting account. My goal was not to correct his version, but to preserve a different perspective. We played the same game without looking at precisely the same problems. I could explain what occupied my attention. Without seeing Peter's account, I could not be certain about decisions rolling around in his mind.
There is another choice in writing especially when told by one of the players. Explaining a close defeat may feel like defending it. How often can I mention that a brigade was one hit from breaking before the reader suspects I am trying to soften the result?
In the first game against Vol, Brown (USA) broke on Turn 5. With a successful Federal attack, I suspected Wilcox (CSA) might have followed on Turn 6, but Wilcox did not actually break because the whole Federal Army broke on the wrecking of Brown. That possibility explains why the contest felt so close. My comment of “One more hit might have won the battle” describes an opportunity. An opponent’s failed attack does not reinforce the prudence of everything I did leading up to this point.
Over these six BatReps, my task was not to invent six different stories. The games and players supplied those unique narratives. My job as battle chronicler was to recognize the differences and choose what would help the reader understand the decisions at the table. At times, choices meant leaving out some events, emphasizing other choices, and explaining why the next attack mattered. A BatRep need not contain everything I remember, or every photo taken. More detail is useful only when it adds to understanding the decisions made and the battle outcome. Otherwise, cut or summarize.
Writing the BatRep and pushing “publish” does not necessarily finish the job. Richard’s comments made the opening account more useful by supplying reasoning I could not. Perhaps that is a sensible place to leave a BatRep? That is, complete enough to follow, but not so tightly wrapped that nothing remains to discuss in the commentary and post-game analysis.
The players made their choices at the table. Writing gave me choices in retelling the story. My account need not be the last word. Commentary has a role in choice as well.








Wow - you put a lot of thought and analysis into your BatReps Jon - it has left me feeling a bit inadequate about my airy-fairy efforts! We would expect no less of an ex data scientist, of course 😊😉😁
ReplyDeleteKeith, I probably put too much thought and analysis into every thing.
DeleteAs I have mentioned before my favourite parts of your AAR are the opening dispositions and the butchers bill at the end. That helps to contextualise everything that occurs in between. The other bits I always enjoy reading about in AARs are those exceptionally good or bad runs of dice rolls which normally mean units are able to pull off something exceptional and usually result in a game highlight.
ReplyDeleteThanks, Lawrence! Maybe I should simplify my BatReps by featuring opening deployments and Butcher’s Bill only? That would speed up my turn-around time immensely.
DeleteWell, they certainly are the highlights for me. but of course you need all the other narrative in the middle for it to make sense.
DeleteI need the middle, for sure.
DeleteYou put a great deal of thought into your battle reports Jonathan. Your post is a great primer on how to write an effective AAR.
ReplyDeleteI should add more arrows to my photos to show who moved where and why. Often a photo without description just becomes eye candy, although with your figures and terrain that would be no problem 😁
It is very useful when you describe the two sides' plans and how they work out and it is something I need to adopt.
Thank you, Ben! I need to keep these thoughts in mind when writing BatReps always. Having six games featuring the same battle was an excellent opportunity to write up a bit of a compare and contrast. Photos without caption or accompanying narrative are almost meaningless to me and, as you say, become eye candy.
DeleteA really interesting read Jon, you certainly have put a lot of thought into this post. Like Lawrence I tend to study the starting positions and then look at the butchers bill to give me an idea of how it unfolds then I go back and read the battle report in full.
ReplyDelete
DeleteMuch appreciated, Donnie! Yes, this post required a lot of thought. The notion for this post (well, title, at least!) has been in my Drafts folder for long time. The half dozen replays of Salem Church provided the data needed to gather my thoughts and put it all down in print. Very good to see that you eventually work your way back to reading through the whole post. That is encouraging. Thank you!
An interesting look back and analysis of the six games and their battle reports. I always enjoy reading your report of our games, and I am often surprised at what bits I either forgot or did not think were key during the game.
ReplyDeleteThank you, Peter, and double thanks for being one of the participants! When playing, we often have our own perspective on what the critical points of battle are especially since we often have different goals and objectives.
DeleteI always struggle a bit when writing up multiple iterations of the same battle, so those are some useful thoughts. A one off is far easier as it is all fresh.
ReplyDeleteThanks, Martin! I enjoy your multi-battle BatReps very much. A one-off report is easier but familiarity in repeating a game has advantages too.
DeleteA splendid analysis of the games, I am amazed that you retain so much of what has happened and when during the games. Reading the various reports and your breakdown of the various games here, as had me thinking if we really need rule writers to add extra “friction” in the rules when dice throw results and players quite easily add their own?
ReplyDeleteVery good to see that you enjoyed my ruminations, Phil! I agree with you that players, dice, and tabletop situation all add plenty of friction into a game. Why force more?
DeleteEnjoyed your post, Jonathan. You make a number of pertinent points. Ben makes a good point about arrows on the photos. They help illustrate the narrative and its place on the battlefield. As you imply, you are the editor working on communicating the intentions, sweep and crucial moments. Sometimes just throwing all the photos in the post without providing a sense of movement can be like flicking through a family album without anyone to tell you who's who, where they are and what they were doing.
ReplyDeleteFortunately, you avoid the pitfalls and consistently produce enjoyable and readable reports in which the flow of battle can be followed.
Interesting post.
Thanks, Richard! Your key decision in Game #1 got this whole ball of ramblings rolling. I agree that viewing a screen full of game photos is exactly like flicking through an old family album or someone’s travel photos having no context or explanation. Like you, I tend to flick through this wall of game photos in the same way. Great analogy!
DeleteInteresting to have the clarity provided by your analysis. It does seem a good the way to go
ReplyDeleteStephen
Pleased that my ramblings provide some clarity, Stephen. Great to see you back among the commentary!
Delete