How Will You Play General Staff?

32 Replies

Every wargame that I’ve designed allows the user to adjust important variables such as leadership and morale and how they affect combat. Usually included is the ability to design your own armies, maps and scenarios as well. However, with the General Staff Wargaming System we’ve added a new feature: the ability to control the realism level before playing a scenario.

The General Staff Wargame has two basic levels of play:

Simulation mode uses HQ units and a chain of command that passes orders down from the General HQ to the sub-commander to the individual unit. How fast the unit responds to the orders are affected by the distance that the courier must travel and the Leadership Value of the HQs.  Simulation mode also employs a more detailed combat resolution model and tracks the actual number of troops in every unit.

An example of Simulation Mode: the path (red line) and time (16 minutes) it will take for a courier to travel from JEB Stuart’s HQ to Munford’s cavalry with orders. Click to enlarge.

Kriegsspiel mode does not have HQ units and friendly units are moved directly and immediately (no transmission of orders via couriers). The combat resolution model is simpler and units have a value of 1-4 displayed by the number of unit icons on the map.

Antietam in Kriegsspiel mode. Notice that there are no HQ units (so no couriers to deliver orders) and units are represented by 1-4 icons. Units in column have a ‘tail’ that indicates the unit strength. Click to enlarge.

In addition to the two game modes (Simulation and Kriegsspiel) there are three Scenario Options:

Order of Battle (OOB) displayed / not displayed. Enemy units with known positions appear dark; enemy units ‘on the map’ but with unknown locations appear grayed out. This, of course, gives the user complete knowledge of the enemy’s OOB and, more importantly, knows when units from certain formations are not directly observable.

A mock up of how the Order of Battle option will appear (note this image was created from screen captures of the Scenario Editor and the Sand Box). Click to enlarge

Only friendly units directly observed by the General HQ are displayed. All other friendly units fade at their last known location. Couriers bring in unit location updates, but they are outdated by the time they arrive.

Only enemy units directly observed by the General HQ are displayed. All other enemy units fade at their last known location. Couriers bring in unit location updates, but they are outdated by the time they arrive.

If both of these above options are selected (only friendly and enemy units that are directly observable by your commanding General HQ) you will be simulating the Fog of War that field commanders of the age of gunpowder experienced.

What General George B. McClellan could actually see at Antietam. Screen shot (General Staff Sand Box). Click to enlarge.

We would like to hear from you and get your opinion on what realism features you will use in General Staff:

“What Ifs” at Little Bighorn

9 Replies

I‘m used to learning a lot when researching a battle but nothing prepared me for the ‘what ifs’ of Little Bighorn. My doctorate is in computer science but I have been an American Civil War buff since I was about five years old. I’m very familiar with brevet Major General George Armstrong Custer’s achievements during the Appomattox campaign where he commanded a division that smashed Pickett’s right flank at Five Forks. I knew that after the war Custer returned to his previous  rank in the U. S. Army of Lt. Colonel, that he fell under a cloud with U. S. Grant, was stripped of his command, and had to beg for it back from President Grant, himself, at the White House.

Brevet Major General George Armstrong Custer taken May 1865. Credit: Civil war photographs, 1861-1865, Library of Congress, Prints and Photographs Division.  Click to enlarge.

And, of course, I knew of the debacle at the Little Bighorn.

After I wrote UMS, the first computer wargame construction system, users began to send me Little Bighorn scenarios that included Gatling guns. I assumed that these were science fiction ‘what if’ scenarios. such as a story I read back in the ’60s about what if Civil War units had automatic weapons from the future. But, recently, while reading Stephen Ambrose’s Crazy Horse and Custer I learned that General Alfred Terry, Custer’s superior and the commander of the expedition, had indeed offered Custer not just three Gatling Guns (manned by troops from the 20th Infantry 1)The Guns Custer Left Behind; Historynet
https://www.historynet.com/guns-custer-left-behind-burden.htm ) but four extra troops from the 2nd U. S. Cavalry.  Custer turned down Terry’s offer of reinforcements and more firepower with these infamous words:

“The Seventh can handle anything it meets.” – Custer to Terry

Photo taken by F. Jay Haynes of one of the Gatling guns that were available to the 7th Cavalry. Click to enlarge.

Screen capture of the Order of Battle of the 7th US Cavalry with the addition of 3 Gatling guns and 4 companies of the 2nd US Cavalry. Click to enlarge.

As for the battle of Little Bighorn, itself, I didn’t know much more than the broad outline that Custer and his command were killed to the last man by an overwhelming number of Native American warriors (this, of course, wasn’t correct as members of Reno’s and Benteen’s columns survived). Custer, himself, was the text book image of hubris and became the butt of late night comedians and humorous pop songs. But the reality turned out to be much more complex and nuanced.

Custer had a reputation of being dashing, headstrong, and gallant; the iconic description of a cavalry commander. The traditional narrative of the disastrous battle of Little Bighorn is that Custer impulsively attacked a vastly superior enemy force; possibly propelled by a belief that Native American warriors were no match for organized cavalry armed with 45-70 trap door carbines. Indeed, Napoleon’s maxim was that, “twenty or more European soldiers armed with the best weapons could take on fifty or even a hundred natives, because of European discipline, training and fire control.” 2)“Crazy Horse and Custer” p. 425 Stephen Ambrose To make matters worse, Custer had pushed the 7th mercilessly and by the time they arrived at the battlefield both men and horses were exhausted.

Custer’s plan of attack is also widely condemned as overly optimistic. He split his command of 616 officers and enlisted men of the 7th cavalry into three battalions. If the four companies of 2nd Cavalry had come along, Custer’s force would be 30% larger.3)Ibid The main force led by himself would be the right flanking column, Reno would have the left flanking attack column and Benteen and the pack train would be in the middle.  Custer also drastically underestimated the Native American force at about 1,500.

In theory, Custer’s plan of attack wasn’t that bad:

  • If Custer was up against a force that was only two or three times his size and
  • If Reno had pressed home his attack drawing the Native American warriors east toward him and
  • If Custer had been able to cross the Little Bighorn above the Native American camp and
  • If Custer had been able to attack the village while the warriors were engaged with Reno

Custer might have, indeed, had a great victory that would have propelled him to the US Presidency (as he had hoped). But none of these suppositions were correct.

Screen shot of the General Staff Scenario Editor where the battle of Little Bighorn scenario is being set up. Not the Order of Battle of the 7th Cavalry (with attached units of the 2nd Cavalry and Gatling guns) on the left. Units are positioned by clicking and dragging them from the Order of Battle Table on the left onto the map. Click to enlarge.

So, the question remains: what value for Leadership would you give to Custer?

Screen shot of the General Staff Army Editor showing the slider that sets the Leadership value for a commander. What value would you give Custer? Click to enlarge

By the way, there will be three separate Little Bighorn scenarios for the General Staff Wargaming System: historically accurate Order of Battle for the 7th Cavalry, the 7th Cavalry plus four companies of the 2nd US Cavalry and 7th Cavalry plus four companies of the 2nd US Cavalry and 3 Gatling guns.

References

References
↑1 The Guns Custer Left Behind; Historynet
https://www.historynet.com/guns-custer-left-behind-burden.htm
↑2 “Crazy Horse and Custer” p. 425 Stephen Ambrose
↑3 Ibid

New Battles on Old Battlefields

6 Replies

Plate 1 from, “The American Kriegsspiel. a Game for Practicing the Art of War upon a Topographical Map,” by W. R. Livermore, Captain, Corps of Engineers, U S Army published in 1882. Click to enlarge.

When I was about ten years old my father brought home an original copy of Esposito’s The West Point Atlas of American Wars. My life was forever changed. I had always been interested in military history and maps but now I could clearly see the complexity of tactical maneuvers and how these battles unfolded.

In previous blogs, I have written about my introduction to wargaming through Avalon Hill’s superb games. While diving deeper into the history of American wargaming I discovered Livermore’s American Kriegsspiel (by the way, it is available online from the Library of Congress here). When I first saw Plate 1, above, I couldn’t help but think of the officers at West Point, ‘practicing the Art of War’ on that black and white map.

Consequently, one of the first things that I wanted to do with the General Staff Map Editor was bring Plate 1 back to life so new battles could be fought on it:

The American Kriegsspiel map imported into the General Staff Map Editor and converted for use with the General Staff Wargaming System. Grid lines are optional. Click to enlarge.

My good friend, Ed Isenberg, did the colorization and we added some new features in the Map Editor to support importing rivers, roads and other terrain features, from a PhotoShop image (for more information see the online documentation for the Map Editor here).

Importing the American Kriegsspiel map into the General Staff Wargaming System was a good beta test of the Map Editor. If you are an early backer you should have the location and password to download it. If, for some reason, you don’t have these, please contact me directly.

One of the interesting features of the General Staff Wargaming System is that any two armies created in the Army Editor can be combined to create a battle scenario on any map created in the Map Editor. Thinking about all the ‘mix and match’ combinations I decided to create an army, in the Army Editor, from the Order of Battle Table (OOB) for the French Imperial Guard, August 1, 1813 from George Nafziger’s, superb “Napoleon at Dresden,” book:

The French Imperial Guard Order of Battle in the General Staff Army Editor. Click to enlarge.

We are currently beta testing the General Staff Scenario Editor. Here I’ve imported the American Kriegsspiel map (from above) and the French Imperial Guard (from above). To position units, just click and drag from the OOB on the left:

Screen shot of the General Staff Scenario Editor where the French Imperial Guard is being positioned on the original American Kriegsspiel map. Click to enlarge.

Hopefully, this will get your imagination going and thinking about what maps, armies and scenarios you would like to see. In addition to the ability to create your own new scenarios on old battlefields, General Staff will ship with 30 historical scenarios (the list is published in previous blogs).

Please feel free to contact me directly if you have any questions.

The Problem With Hexagons

38 Replies

Hexagons are ubiquitous in wargames now (indeed, both Philip Sabin’s War: Studying Conflict Through Simulation Games and Peter Perla’s The Art of Wargaming feature hexagons on their book covers), but this wasn’t always the case. My first wargame – the first board wargame for many of us – was Avalon Hill’s original Gettysburg  (by the way, $75 seems to be the going price for a copy on eBay these days).

No hexagons in Avalon Hill’s original Gettysburg. Remember how the map contained the original starting positions for the Union cavalry and out posts? From author’s collection. (Click to enlarge)

The American Kriegsspiel by Captain Livermore (circa 1882) only had a map grid for estimating distances. We also have a map grid in General Staff to facilitate estimating distances but you can turn the map grid on or off.

Plate 1 from The American Kriegsspiel by Captain Livermore. Click to enlarge. This image is from GrogHeads wonderful blog post on Nineteenth Century Military War Games. Link: http://grogheads.com/featured-posts/5321

And how about this picture from the Naval War College (circa 1940s)? I just needed an excuse to post this photograph:

A Fletcher Pratt Naval War Game in progress. I never understood why they didn’t use upside down periscopes to check broadside angles rather than getting down on the floor. Click to enlarge. From this blog http://wargamingmiscellany.blogspot.com/2016/02/simulating-gunfire-in-naval-wargames.html

It is pretty common knowledge among the wargaming community that Avalon Hill’s owner, Charles Roberts, introduced hexagons to commercial wargaming in the early 1950s .

“Later, he [Roberts] saw a photograph of one of the RAND gaming facilities and noted they were using an hexagonal grid. This grid allowed movement between adjacent hexagons (or hexes, as they are more frequently called) to be equidistant, whereas movement along the diagonals in a square grid covered more distance than movement across the sides of the squares. Roberts immediately saw the usefulness of this technique and adopted to his subsequent games.”

– The Art of Wargaming, Perla, p. 116

In researching how the RAND Corporation – a major post-war defense think tank – came up with the original idea of employing hexagons to simplify movement calculations (as well as the invention of the Combat Resolution Table or CRT) I stumbled upon an amazing document: Some War Games by John Nash and R. M. Thrall (Project RAND, 10 September 1952; available as a free download here). Yes, that is THE John Nash; A Beautiful Mind John Nash; the Nobel Prize recipient John Nash. The Some War Games summary states:

“These games are descendants of the one originally instigated by A. Mood, and are both played on his hexagonal-honey comb-pattern board. – Some War Games Nash & Thrall.

But what appears on Page 1A of Some War Games is even more exciting:

The earliest reference of using hexagons for wargames. “The board is a honeycomb pattern of hexagonal “squares,” the same that was used in Mood’s game” – From Some War Games (Project RAND, Nash & Thrall).

Sadly, I have been unable to find an actual copy or documentation for “Mood’s game,” but did discover that A. Mood was a statistician who wrote the popular text book, “Introduction to the Theory of Statistics,” and, during World War II was involved with the  Applied Mathematics Panel and the Statistical Research Group. Mood was also the author of, “War Gaming as a Technique of Analysis,” September 3, 1954 which is available as a free download here. Unfortunately, I have yet to uncover any images of Mood’s original war game and the very first use of his ‘honeycomb pattern’ board.

Let’s take a quick look at the math behind hexagons:

The cost of moving diagonally as opposed to horizontally or vertically on a map board (from a slide in my PhD Qualifying Exam on least weighted path algorithms).

The problem of quick and easy movement calculation (as shown in the above graphic) is caused by the Pythagorean Theorem. Well, not so much caused, as a result of the theorem:

The distance to a diagonal square, d, is the square root of the square of the hypotenuse (the side opposite the right angle) which is equal to the sum of the squares of the other two sides. We all learned this watching the Scarecrow in the Wizard of Oz, right?

In other words, if everybody could just multiply by 1.41421356 in their heads we wouldn’t even need hexagons! The downside, of course, is now we’ve restricted our original eight axes of movement to six. And there’s another problem; what I call the, “drunken hexagon walk.”

An example of “drunken hexagon walk” syndrome. All we’re trying to do is go in a straight line from Point A to Point B and from Point A to Point C.

In the above diagram we just want to travel in a straight line from Point A to Point B. It’s a thirty degree angle. What could be simpler? How about traveling from Point A to Point C? It’s a straight 90 degree angle. It’s one of the cardinal degrees! What could be simpler than that? Instead our units are twisting and turning first left, then right, then left like a drunk stumbling from one light post to another light post across the street. In theory the units are actually traversing considerably more terrain than they would if they could simply travel in a straight line. This is the downfall of the hex: sometimes it simplifies movement; but just as often it creates absurd movement paths that no actual military unit would ever take.

So, what’s the solution? Clearly, there is no reason why a computer wargame should employ hexes. Computers are very good at multiplying by 1.41421356  or any other number for that matter. Below is a screen shot of General Staff:

Screen shot of General Staff (2nd Saratoga) based on the map of Lt. Wilkinson, “showing the positions of His Excellency General Burgoyne’s Army at Saratoga published in London 1780)  . Click to enlarge.

What’s missing from the General Staff screen shot, above? Well, hexes, obviously. Units move wherever you tell them to in straight lines or following roads precisely if so ordered. And units can obviously face in 360 degrees. Consider this screen shot from the General Staff Sandbox where we’re testing our combat calculations:

Screen shot from the General Staff Sandbox. Notes: 3D unit visibility is turned on, displayed values: unit facing, distance, target bearing, enfilade values, target offset. Click to enlarge.

For board wargames hexagons seem to be a necessary evil unless you want to break out the rulers (that never stopped us with the original Gettysburg or Jutland). But, when it comes to computer wargames, I just don’t see the upside for hexagons but I do see a lot of downside. And that’s why General Staff doesn’t use hexes.

Map Editor Released for Beta-Testing!

7 Replies

We are very pleased to report that the General Staff Black Powder Map Editor has been released into beta-test. This program allows the user to easily create maps for use as a battlefield in the General Staff Wargaming System as shown in this demo:

Important Note: If you were an early backer of the General Staff Wargaming System via Kickstarter or Indiegogo, you should have received an email update informing you of this, the beta test download page and password. If you did not, please contact me directly. Also, a few people became beta testers after the Kickstarter and Indiegogo campaigns. You should have received an email from me with the URL for the download page and password. If you did not, please contact me directly.