Category Archives: Gameplay

How Will You Play General Staff?

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

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
) 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   [ + ]

1. The Guns Custer Left Behind; Historynet
2. Crazy Horse and Custer” p. 425 Stephen Ambrose
3. Ibid

Using General Staff to Create a Simulation of the Battle of Isandlwana (January 22, 1879)

We recently asked you for your favorite 18th and 19th century (‘Age of Gunpowder’) battles to be included free for early backers of General Staff (see this link). We don’t want to spoil any surprises, but the Battle of Isandlwana was one of the top vote-getters.

Screen shot of the General Staff Scenario Design Module showing how to edit specific unit type versus unit type combat equations. In this example Blue Light Infantry (Zulu regiments) have been adjusted downward. Click to enlarge.

The Battle of Isandlwana is an especially challenging scenario to simulate because of the difference in technology (the British were armed with Martini-Henry breech-loading rifles while the Zulu warriors carried the traditional assegai iron spears and cow-hide shields). Yet, there are ‘Light Infantry’ unit types in both the Red and Blue forces, but clearly there is a very big difference between the Red (British) Light Infantry and the Blue (Zulu) Light Infantry units.

General Staff, which is based on the UMS Wargaming System, has the ability to adjust a unit’s combat firepower versus other unit types (see the above screen capture). In the above image we have set Blue’s Light Infantry (Zulu regiments) with a lower Attack Multiplier representing the Zulu troops lack of muskets and rifles. This matrix is available from the General Staff Scenario Design Module.

Screen capture of the British army Order of Battle for Isandlwana . Click to enlarge.

In the above screen capture from the General Staff Army Design Module we see a portion of the British Order of Battle at Isandlwana. The question is: what should Leadership, Morale and Efficiency be set for each of these units? How good were British commanders? What was the morale of native troops? How efficient were they? We would love to hear your comments.

A Tale of Two Wargames

I first conceived of General Staff as a very simple, introductory wargame that might be the first real wargame to be released for the Xbox (clearly, an under-served market). However, two things stopped this plan dead in its tracks: first Microsoft closed down the independent online games channel for Xbox and then, after being approached by a major wargame publisher, I was told that there was, “no market for wargames on the Xbox,” however a new version of my UMS series, could, “sell 25,000 units in its first year.”

So, I went back to the proverbial drawing board but I also asked you, the Grognards, what kind of a game you wanted. And here are the results:

Clearly, almost as many people want a simple, Kriegsspiel type game as want a complex military simulation.

After pondering this conundrum I had an epiphany: ‘simple’ wargames and ‘complex simulations’ actually share about 80% of the same code and data. Why not make a wargame that the user can decide which he wants to play? Sometimes people aren’t up for hours long complex simulations; other times people are.

Screen capture from General Staff showing the set up for ‘Simulation’ mode (note the button in the upper-left hand corner). Click to enlarge.

In the above screen capture the user has selected ‘Simulation’ mode. Note that there are headquarters units displayed. Headquarters play an important role in General Staff in simulation mode. All orders are given through the commanding general to the subordinate commander (via courier) and then (again via courier) to the actual unit. For example:

In this screen capture an order from Marshal Beresford will take 8 minutes of game time to be delivered to ths subordinate commander. (Click to enlarge)

It will take 8 minutes for the courier to ride from Marshal Beresford headquarters to the subordinate’s headquarters.

It will take an additional 6 minutes for a courier to deliver the order to the subordinate infantry unit. Click to enlarge.

Additional time (based on the headquarter’s Leadership value) will be added before the next courier is dispatched to deliver the order to the infantry unit. So for a command to go from Marshal Beresford, to Major General Stewart to Colborne’s Brigade will take a minimum of 14 minutes of game time plus additional time penalties based on the leadership abilities of Beresford and Stewart.

Detailed information about a unit in Simulation mode. Even the number of volleys remaining are tracked. Click to enlarge.

Lastly, the leadership of Colborne’s Brigade is used to calculate how quickly the unit will act upon the received orders. This is an example of the detailed Simulation mode for General Staff.

However, in Kreigsspiel mode,  all headquarters units are removed and the user issues orders directly to the units that immediately respond to the commands.

General Staff in Kreigsspiel mode. Note the button in the upper left-hand corner, headquarters units have been removed and unit strength is either 1,2,3 or 4.

Also, all unit information except a simple value (1-4) is ignored. Kriegsspiel mode is the simple, introductory wargame that I originally envisioned.


Gameplay Surveys 1 & 2 Results.

We just ran two Gameplay Surveys to find out exactly what kind of units and unit structures you wanted to see in General Staff and the results are in. We especially wanted to know, in general terms, if you wanted us to create a classic Kriegsspiel game or a very detailed military simulation like UMS, UMS II and The War College.

Well, here are the results and they’re not what we expected:

48%: I prefer simple unit data; just the unit type and unit strength.

52%: I want to include as much detailed information about a unit as possible.

In other words, about half of you want a simple game and about half want a very detailed game. I must admit, I had to think about this for a while, but I’ve finally come up with a solution. This really isn’t about gameplay, it’s about the information that is stored about each unit and how the information is used for combat resolution. When an army is created using the Army Design Module all the required information will have to be added and stored within the unit data structure. However, when a user selects a scenario to play, the user will be able to decide if they want to play the ‘classic Kriegsspiel‘ or ‘complex simulation’ version.

The half of respondents that want detailed information about units requested the following information be stored for each unit:

Unit Name. For historical or informational purposes such as, “Chasseurs à Cheval Garde” or “Battery B 4th US Artillery.”

Unit Type. Such as, “Heavy Cavalry,” or “Field Artillery.” See below for more survey questions about pre-designed unit types.

Unit Strength. A numeric value of the number of men in the unit. However, in the ‘classic Kriegsspiel‘ version this value would simple be the numbers 1-4 and shown by the number of unit icons displayed (see below):

Screen captures of various unit types and facings in General Staff. Note that unit strength is obvious (1,2,3 or 4). Click to enlarge.

Unit Leadership. A value from 1-10 representing ‘poor’ to ‘superb’ leadership values. This will be displayed as a graph in the game. This value is used in the combat equation and to calculate how fast a unit responds to orders.

Unit Quality. A value from 1-10 representing ‘poor’ to elite’ unit quality values. This will be displayed as a graph in the game. This value is used in the combat equation and to calculate how fast a unit responds to orders.

Unit Morale. A value from 1-10 representing ‘poor’ to ‘elite’ morale. These values will change during the game in response to the results of the unit’s combat. This value will be displayed as a graph in the game and is used in the combat equation.

Ammunition Level. A value indicating the number of volleys remaining for the unit. In the ‘classic Kriegsspiel‘ version of General Staff units have unlimited ammunition.

Our next series of survey questions asked what unit types would you like to see. The following unit types will be available in General Staff:

Infantry (line infantry), Light Infantry (including skirmishers), Cavalry, Light Cavalry (including lancers), Field Artillery, Horse Artillery, Headquarters (see below) and Supply Trains.

We next asked if users wanted a ‘flat’ or ‘hierarchical’ army structure. The hierarchical army structure allows for a Corps → Division → Brigade type structure. Headquarters units will be included and orders will be transmitted via couriers. Users overwhelmingly wanted a hierarchical structure:

88% of users want a hierarchical army structure.

Lastly, we asked you about screen resolution.

75% of users were happy with 1440 x 900 screen resolution.

We understand that 25% of users want a higher resolutions and we’ll do our best to accommodate them.

Feedback from users is very important to us. We want to create the wargame system that you want to buy. If you have other questions or comments please don’t hesitate to contact us here.