Click on the image below to see a step by step video tutorial of the Army Editor, Map Editor, and Scenario Editor as the battle of Brandy Station (June 9, 1863) is created using the General Staff: Black Powder Battle Designer Bundle.
Early Backers: If you did not get your Steam key please email Support@RiverviewAI.com. Thanks!
The General Staff: Black Powder Designer Bundle store on Steam. Click on image to go directly to the Steam store.
I am very pleased to announce that the Steam store for General Staff: Black Powder Battle Designer Bundle is now up and active. More importantly, if you are an early backer, you should have received your Steam key to download it by now. If you are an early backer and have not received an email with your Steam key, please contact me directly.
Some important things to know:
The Battle Designer Bundle does not include the actual game! The game is a different install package and, hopefully, will be in beta in the next month or two. If you are an early backer and received a Steam key for the Battle Designer Bundle you will also receive a second Steam key, when available, for the actual game and you will be welcome to participate in beta testing, too.
The Battle Designer Bundle includes everything you need to create your own armies, maps and scenarios for use in the actual game. The Battle Designer Bundle includes the Army Editor, the Map Editor and the Scenario Editor. The Map Editor supports a digitizing tablet (if you’re lucky enough to have one and the talent to use one, I don’t).
I need your suggestions for a battle that I can use to create video tutorials for the Army, Map and Scenario Editors. If you have suggestions, please contact me directly. However, it’s important to remember that I need a good Order of Battle (OOB) table that includes unit strengths. I also need a good quality map that is at least 1155 x 805 pixels (resolution). If it’s an old battle map, I need somebody to take the time to remove the units from the map. For example, here’s the original map of Antietam from the Library of Congress:
Map of the battle of Antietam from the Library of Congress. Willcox, William H. Map of the battlefield of Antietam. [Philada., Lith. of P. S. Duval & Son, 1862] Map. Click to enlarge.
The Antietam map after I removed all the units, cleaned it up, lightened it and rotated it 90 degrees. Click to enlarge.
I’m looking forward to receiving your scenario suggestions and creating the video tutorials. The tutorials will be posted here and on our YouTube channel.
The delay in the transmittal of orders from headquarters and staff is one example of the Friction of War. Note the calculated time for couriers to arrive displayed in the Subordinate Orders list on the left of the screen. The red lines are the routes that couriers from General HQ to Corps HQ to individual units will take. General Staff: Black Powder screen shot. Click to enlarge.
Carl von Clausewitz, in has seminal work, On War, (Book 1, Chapter 7) originated the phrase, “Friction of War”:
Carl von Clausewitz painted by Karl Wilhelm Wach. Credit Wikipedia.
“Friction is the only conception which, in a general way, corresponds to that which distinguishes real war from war on paper. The military machine, the army and all belonging to it, is in fact simple; and appears, on this account, easy to manage. But let us reflect that no part of it is in one piece, that it is composed entirely of individuals, each of which keeps up its own friction in all directions.”
I knew that if General Staff: Black Powder were to be an accurate simulation, and not just ‘war on paper’, that the friction of war would have to be calculated into the command / orders chain. One part of this – the distance the couriers will travel from one headquarters to the next to deliver their orders and the time it takes to travel this distance – can be calculated with reasonable certainty (I’m using the rate of 10.5 kilometers per hour for a horseman, I’m not an expert but this seemed reasonable, and it’s easy to change if somebody has a more accurate value).
Another example of friction of war is factored into the delaying of the arrival of orders is Leadership Value:
In this example, the Imperial couriers will travel over 4.3 kilometers, taking 24 minutes, to deliver their orders. Also, note the cost of the combined Leadership Values. Because Napoleon and Vandamme have very high Leadership Values little additional delay is added. General Staff: Black Powder screen shot. Click to enlarge.
You can specify at what time the order is to be executed (in this case 6:15), however you can not set a time earlier than when the couriers would arrive. This allows for coordination of attacks across units. General Staff: Black Powder screen shot. Click to enlarge.
The other value – and it is arbitrarily set – is the cost of ineptitude, incompetence, lack of motivation, and sloppy staff work. In the above scenario (Ligny) Napoleon’s Leadership is set at 93%:
The slider adjusts Napoleon’s Leadership Value which effects the delay in issuing orders. General Staff: Black Powder Army Editor screen shot. Click to enlarge.
I understand that Napoleon may have been feeling a bit under the weather during the Hundred Days Campaign. You can set his Leadership Value to anything you want in the Army Editor (above).
Major General George B. McClellan’s Leadership Value can be changed in the Army Editor. Click to enlarge.
Did I set McClellan’s Leadership Value too low? He was amazingly incompetent. Note below:
The combination of McClellan’s and Burnside’s extremely low Leadership Values adds an additional 29 minutes to the transmittal of orders. The blue lines trace the route that couriers would travel from McClellan’s headquarters to Burnside’s headquarters and then to each division and battery. General Staff: Black Powder screen shot. Click to enlarge.
The combination of McClellan’s and Ambrose Burnside’s Leadership Values results in almost a half hour delay in transmittal of the orders (remember after receipt of the orders, Burnside has to send couriers to his divisional and battery commanders, too and their Leadership Values effects the delay before their unit executes the order). After factoring the time it would take for a horseman to travel the distance between McClellan’s headquarters to Burnside’s headquarters (14 minutes) the earliest that a unit could be expected to respond to the original order from General Headquarters would be forty-one minutes later (and, in reality, a bit after that because of that unit’s Leadership Value).
The path of the couriers from McClellan’s headquarters, to Burnside’s Headquarters and then out to the divisions and batteries. General Staff: Black Powder screen shot. Click to enlarge.
I have spent some time at Antietam and studied it at length and this delay of about three-quarters of an hour between the time McClellan wanted to issue an order and the men of Burnside’s IX Corps moved out seems if anything, too optimistic of a timetable. In fact, as I write this, I think I need to increase the penalty for poor Leadership Value. McClellan and Burnside couldn’t possibly have got units moving in less than an hour.
As I have begun playtesting General Staff: Black Powder I found the delay between issuing orders and wanting to see something move now was a bit disconcerting. It shouldn’t have been. I’ve read enough military history to know that battlefield orders were often transmitted the night before and moving units around during the battle could be a risky proposition. Some armies, however, were less afflicted with these problems than others, and that I would attribute to ‘leadership value’ which also encompasses the army’s general staff.
If you don’t want to use General Staff: Black Powder as a simulation that inserts a calculated delay between orders and execution, and would rather just move units instantly, there is ‘Game Mode’:
The Select Mode screen in General Staff: Black Powder. The user chooses between ‘game’ and ‘simulation’ with differences in rules and unit icons. Click to enlarge.
Game Mode has the same maps but uses simpler icons and rules. I originally envisioned Game Mode as a way of introducing wargaming to a new generation (I wanted to write it for the XBox). Anyway, it’s included with General Staff: Black Powder.
Lastly, I know everybody is waiting for news about when can I get my hands on the game?!!?!! My friend, Damien, wasn’t able to work on finishing it using Unity so I’m finishing it up using MonoGame. As you can see I’m pretty far along and I think I will be playing the first ‘actual game’ (that is a simulation from start to finish) within the next couple of weeks; maybe sooner. After that, probably at least another month of fixing bugs, but then I’m hoping to set up a Beta download for all the early backers via Steam. We have a space on Steam but I haven’t even begun to build it out. Obviously, I’m just one guy, I’m working as fast as I can, but I think this is all good news. Also, I’m working on a video to show everything off.
As always, if you have any questions or comments, please feel free to contact me directly.
Screenshot of MATE analysis of Gettysburg, Day 3 from the Red (Confederate) position. Click to enlarge.,
General Lee, at Gettysburg, said: “the enemy have the advantage of us in a shorter and inside line and we are too much extended.” – quoted by Major General Isaac Trimble.1)Isaac Trimble, Southern Historical Society Papers, Vol. 26, Richmond, Virginia: Reverend J. William Jones, D.D., MATE, the AI behind General Staff, came to the exact same conclusion:
A portion of MATE’s analysis of Red’s position at Gettysburg, Day 3. Here MATE recognizes that Red has exterior lines and the enemy has a decided advantage.
I have been porting TIGER 2)Tactical Inference GenERator, the AI behind my doctoral thesis and my DARPA sponsored research from C++ to C# and integrating it into the General Staff: Black Powder wargaming system. I have been doing this via the method of first creating a scenario typifying a specific attribute (exterior lines, exposed flanks, choke points, etc.) and then porting the actual code over and feeding it the scenario for analysis. Gettysburg, Day 3, is the canonical example of exterior and interior lines.
92.9% of Subject Matter Experts agree! The Union (Blue) lines at Gettysburg, Day 3, exhibit the attribute of being Interior Lines. Interior lines are good. Exterior lines are bad. From author’s doctoral thesis.
So, first a significant number of Subject Matter Experts (combat commanders, tactics instructors at military academies, etc.,) agree that there is an attribute called ‘Interior Lines’ and that it is exhibited by the Union (Blue) forces at Gettysburg, Day 3. We then create an algorithm that can detect such an attribute and convert it from C++ code to C# code (and substantially rewrite and improve said algorithm in the process) . We then create a Gettysburg, Day 3 scenario using the General Staff Army Editor, the General Staff Map Editor and the General Staff Scenario Editor and feed the scenario3)In Computer Science lingo programs are machines that consume data / tokens to MATE, the General Staff: Black Powder AI. These are the results:
MATE analysis text output (with author’s commentary) of Gettysburg, Day 3, from the Red (Confederate) position. Click to enlarge.
The first time that I presented the Gettysburg, Day 3 scenario as Red to MATE it refused to attack. The enemy has interior lines (1.4, or 40% greater is pretty significant value), you’re attacking uphill (slope > 7%), your attacking units are under enemy ROI (mostly batteries of 12 lb. Napoleon canon shooting explosive shot and then canister and then double-shotted canister) for over a kilometer. Attacking is not a good idea. To get MATE to attack I had to go back to the Map Editor and create a number of new Victory Points; specifically the places where significant roads (Emmitsburg Road, Cashtown Road, Baltimore Pike, etc.) enter the map. Then I went in to the Scenario Editor and assigned appropriate values and current ‘ownership’. Saved it all and fed it back to MATE and the, above, is what I got.
The only way for MATE to win (as Red) is to attack large Victory Point areas (Cemetery Hill and Cemetery Ridge) and hope to destroy significant numbers of Blue (Union) forces along the way to meet the victory conditions set in the Scenario Editor:
Gettysburg, Day 3 Victory Conditions. Screenshot General Staff Scenario Editor.
Anybody who has built a wargame scenario (and I suspect there are more than a few among the readers of this blog) know the drill of going back to edit the OOBs, starting positions, victory conditions, etc. I would just like to say it’s pretty painless using the General Staff Wargaming System. The various editors all integrate seamlessly like Microsoft Office products (they were written in Microsoft WPF by Andy O’Neill who is a Microsoft Gold Developer).
But, the real question that this raises is: why did Lee attack on Gettysburg, Day 3? Blue (the Union) not only had interior lines, an elevated position, but they also had anchored flanks (see #22 above). MATE is running out of options at this point. If you look at the top screenshot you will see yellow numbers in yellow circles. These represent MATE’s three ‘weakest points’ in Blue’s line and it’s not much.
So why did Lee attack?
James Longstreet’s From Manassas to Appomattox states absolutely that
All that I could ask was that the policy of the campaign [Lee’s invasion of the north] should be one of defensive tactics, that we should work so as to force the enemy to attack us, in such good position as we might find in his own country, so well adapted to that purpose, – which might assure us of a grand triumph. To this he readily assented as an important and material adjunct to his general plan. [p. 331]
So, Longstreet, in his autobiography, is saying that Lee agreed that at some point in Pennsylvania, the Army of Northern Virginia would find a good solid defensive position and let Hooker (they didn’t yet know that Meade was the new commander of the Army of the Potomac) smash his army to pieces upon it. James McPherson in, To Conquer a Peace: Lee’s Goals in the Gettysburg Campaign writes:
“In a conversation with General Isaac Trimble on June 27, when most of the Army of Northern Virginia was at Chambersburg, Pa., and when Lee believed the enemy was still south of the Potomac, he told Trimble: “When they hear where we are, they will make forced marches…probably through Frederick, broken down with hunger and hard marching, strung out on a long line and much demoralized, when they come into Pennsylvania. I shall throw an overwhelming force on their advance, crush it, follow up the success, drive one corps back on another, and by successive repulses and surprises, before they can concentrate, create a panic and virtually destroy the army.” Then “the war will be over and we shall achieve the recognition of our independence.”
The argument is that Lee, on the morning of July 3, 1863, found himself in a terrible strategic situation with very few options. It was imperative that Lee must, “destroy the [enemy] army;” nothing less than a great triumph in enemy territory would do. In Lee’s only official report of the battle of Gettysburg, written on July 31, 1863 he states:
The enemy was driven through Gettysburg with heavy loss, including about 5,000 prisoners and several pieces of artillery. He retired to a high range of hills south and east of the town. The attack was not pressed that afternoon, the enemy’s force being unknown, and it being considered advisable to await the arrival of the rest of our troops. Orders were sent back to hasten their march, and, in the meantime, every effort was made to ascertain the numbers and position of the enemy, and find the most favorable point of attack. It had not been intended to fight a general battle at such a distance from our base, unless attacked by the enemy, but, finding ourselves unexpectedly confronted by the Federal Army, it became a matter of difficulty to withdraw through the mountains with our large trains. At the same time, the country was unfavorable for collecting supplies while in the presence of the enemy’s main body, as he was enabled to restrain our foraging parties by occupying the passes of the mountains with regular and local troops. A battle thus became in a measure, unavoidable. Encouraged by the successful issue of the engagement of the first day, and in view of the valuable results that would ensue from the defeat of the army of General Meade, it was thought advisable to renew the attack. . . .
Lee was in for a penny and in for a pound. This was not the defensive battle of Longstreet’s choosing. This was now Lee desperately trying to, “throw an overwhelming force on their advance, crush it, follow up the success, drive one corps back on another, and by successive repulses and surprises, before they can concentrate, create a panic and virtually destroy the army,” but now the enemy had, “retired to a high range of hills south and east of the town.” The Union had flipped Longstreet’s strategy 180 degrees and it was they who had, “force[d] the enemy to attack [them], in such good position as [they] might find.”
I will create some other Gettysburg scenarios including ones with the Union and Confederate cavalry available. While not historical, it might make for some interesting gameplay and Human-Level AI decisions.
As always, please feel free to contact me directly with comments.
Quatre Bras, June 16, 1815. Click to enlarge
Napoleon has humbugged me, by God!” Lord Wellington swore. “He has gained twenty-four hours’ march on me!” 1)David Chandler, Waterloo: The Hundred Days, Macmillan Publishing Co., Inc. New York 1980, p. 85 And, indeed, he had.
The Armée du Nord, racing north on the roadnet from Paris to Brussels, now occupied the crucial strategic ‘central position’ between the Anglo-Allied army under Wellington assembling at Quatre Bras in the west, and the Prussian army under Blücher at Ligny in the east. Napoleon, outnumbered by the combined forces of Wellington and Blücher only had one realistic option: destroy his opponent’s armies separately before they could combine and destroy him.
Napoleon divided the Armée du Nord into two wings (the left commanded by Marshal Ney and the right by the Emperor, himself). The Imperial Guard would serve as the strategic reserve. In our previous blog, we showed the MATE (Machine Analysis of Tactical Environments) artificial intelligence analysis of the battle of Ligny.
The starting positions of the Armée du Nord (Blue) and the Anglo-Allied Army (Red) at the battle of Quatre Bras. Screen shot from General Staff: Black Powder. Click to enlarge.
The positions in the above screen shot come from the West Point Atlas of the Napoleonic Wars and Chandler’s Waterloo: The Hundred Days. I’ve ordered Mike Robinson’s The Battle of Quatre Bras, 1815 (which is very highly regarded) but it’s coming from Europe and will be a while before it arrives. I’ll update the positions accordingly when it arrives.
Today MATE is going to show off a new trick that it learned.
MATE AI analysis of Blue’s position. General Staff screen shot. Click to enlarge.
Text output and author’s commentary of MATE’s analysis of Blue’s position at the battle of Quatre Bras.
The salient points of MATE’s analysis of Blue (Ney’s) position at the battle of Quatre Bras are:
In other words, Battle Groups #3 and #1 will be the Enveloping Force and Battle Groups #0 and #2 will be the Fixing Force as illustrated in the above graphic from the U. S. Army Field Manual 3-21. Algorithms for implementing this maneuver (an early version of MATE) first appear in my paper, Implementing the Five Canonical Offensive Maneuvers in a CGF Environment.
And MATE’s new trick? It’s in line #25, above. If there is a Battle Group that is composed entirely of cavalry and horse artillery, and it is close enough, it will be used as the spearhead for the flanking maneuver.
MATE’s analysis of Ligny. Screen shot from General Staff AI Editor. Click to enlarge.
But, in this situation (Ligny, above) MATE has calculated that Battle Group #1 will get to the crucial Choke Point (labeled in black, above) before the reserve cavalry Battle Group #4 will arrive and would create a tremendous bottleneck at the very choke point that MATE wants to quickly capture. Consequently, the cavalry has been left in reserve.
Can MATE read and analyze any battle map from history?
No. MATE is integrated into the General Staff Wargaming System. MATE can only ‘understand’ Order of Battle (OOB) tables created in the General Staff Army Editor, maps created in the General Staff Map Editor and scenarios created in the General Staff Scenario Editor.
What is meant by a ‘human-level’ artificial intelligence?
Perhaps you have heard of the famous Turing Test (from Alan Turing’s Computing Machinery and Intelligence). In it he describes, “The Imitation Game,” where a computer is in one room behind a closed door, and a human is another room behind a closed door. A third person, the ‘interrogator’, can only ask questions via a teletype (an ancient I/O device consisting of a keyboard and a printer) and must determine in which room the computer is and in which room is the human. In Turing’s original paper the interrogator would ask questions of the two subjects such as, “Please write me a sonnet on the subject of the Forth Bridge,” and, “Add 34957 to 70764.” Currently, no Artificial Intelligence (AI) could pass such a test; the subject area is far too broad. However, it has been my thesis, that an AI could pass such a test if the subject area is restricted to a narrow field of human endeavor, such as commanding units on a battlefield. If, in the above Turing test, the computer in one room was replaced with MATE, the human in the other room was replaced by Napoleon, and the teletype was replaced by the General Staff Wargaming System, I argue that MATE could (or soon will be able to) pass such a test (subject matter experts would not be able to discern if it was MATE or Napoleon giving orders).
Can MATE analyze current military situations?
Though MATE came out of the TIGER (Tactical Inference GenERator) project funded by DARPA, it is currently set up specifically for the General Staff: Black Powder project which limits analysis to scenarios in the 18th and 19th centuries. It is intended that this project will be followed up with General Staff: Modern Warfare to specifically work with 20th and 21st century combat.
References
| ↑1 | David Chandler, Waterloo: The Hundred Days, Macmillan Publishing Co., Inc. New York 1980, p. 85 |
|---|
