Tag Archives: Movement

Wargames, Slopes & the High Ground

Rules for how slopes effect attack and defense from Avalon Hill’s Gettysburg (1960 edition). Author’s collection. Click to enlarge.

One of the first rules that we all learned when we began to play wargames (at least this was true of early Avalon Hill games for me way back in the 1960s) was that if the defending unit was on a hill and the attacking unit was on the slope, the defender’s ‘defense factor’ was doubled. Under some circumstances, a defending unit could even have its defense factor tripled (see right). And, yes, there were situations (see below) where an enfilading attacking unit could negate the defenders 2:1 advantage.  For my entire wargaming life – over fifty years now – this basic rule of thumb applied: a unit on a hill was twice as strong, defensively, than it would be on the plains below.  I’ve used this ‘defensive factor multiplier’ in every wargame I’ve designed going back to UMS in the 1980s. I never gave  it a second’s thought. Until now.

Detail of rules from Avalon Hill’s Waterloo (1962) showing when a defender’s strength is doubled on a hill and when the effect is negated.

General Staff has no concept of “defense factor.” Think about it, what is a ‘defensive factor’? It seems to act like armor of some sort. It certainly is a valid concept in naval warfare or armored warfare or jousting, but it doesn’t apply in 18th and 19th century warfare that General Staff: Black Powder is designed to simulate. Instead, units in General Staff are weapons platforms. Units project firepower which result in casualties. Indeed, all combat resolution boils down to this equation: How many casualties did this unit inflict on that unit?

Since there is no ‘defensive factor’ to multiply by two for being on a hill defending against an attacker climbing a slope, how or what does General Staff multiply or divide? What is the source for the 2:1 defense factor multiplier for having the high ground? These were the questions that I recently investigated.

It turns out there has been very little research done on the subject of military movement on slopes of various degrees, and the effect of angle of slope on defending a position against a unit attacking up slope.  Yes, the U. S. Army has published this on foot marches and slopes but it doesn’t cover 19th century cavalry, artillery, horse artillery, etc.).1)I contacted respected military historian and researcher Brent Nosworthy who wrote back, “The effects of slopes on the speed of movement and the cohesion of troops is a very interesting question indeed. I am enclosing a rough draft of a chapter from The Metrics of War booklet I was working on last year. I think here and there is some information as to how it affected beast of burden’s ability to draw artillery. There were several articles about defending and attacking heights in Rider, John (Editor); British Military Library: A Complete Body of Military Knowledge; second edition, 2 volumes, London, 1798-1801. I cannot remember if there were specific references to these issues in these articles. I also recommend if you have not already consulted: Tielke, Johann Gottlieb, The field engineer; or instructions upon every branch of field fortification: … with plans and explanatory notes. Translated from the fourth … London, 2 volumes, 1789. Russell, John (Lieutenant – 96th Regiment of Foot); A Series of Military Experiments of Attack and Defence, Made in Hyde-Park, in 1802, London, 1806. Adye, Ralph Willet; The Bombardier, and Pocket Gunner, Second Edition, London, 1802. However, I am not certain they contain any references to the effect of the angle of slope on speed and cohesion.”

What I was looking for was a table that cross-indexed angle of slope with its effect on attack, defense and movement. What I found was Table D, (below) from the rules for Charles Totten’s Strategos: The Advanced Game. on the Grogheads.com site:

From. “Charles Totten’s Strategos: The Advanced Game.” found at Grogheads.com. Published in 1890.

What this chart shows is:

  • Unit types respond differently to moving up or down different slopes; e.g. no artillery can ascend a slope greater than 15°, no cavalry can descend a slope greater than 30°, and infantry can only ascend slopes of greater than 30° in skirmish formation.
  • Having superior elevation does not impart any defensive advantage by itself.
  • Having superior elevation on a steep slope can actually be a defensive disadvantage; e.g. artillery cannot fire down a 15° slope, and cavalry cannot charge down slopes greater than 15°.
  • Units firing uphill have increasingly less effect as the angle of slope increases; e.g. infantry has limited or no effect firing uphill at greater than a 20° slope, cavalry cannot charge up a slope greater than 15°, and artillery has no effect when firing up a slope greater 15°. Indeed, this is where the the traditional defensive advantage of holding the high ground derives from: defensive fire is not more effective, rather offensive fire is much less effective when attacking uphill.

If we look at two battles of the American Civil War that are known for assaults up steep slopes (Fredericksburg, December 13, 1862 and Missionary Ridge, November 23, 1863) we find that the values in Table D, above, are largely validated.

Detail of map of Missionary Ridge from the Library of Congress. The crest of the ridge is about 275 feet above the plain below. In numerous places, the slope is greater than 20°.

The story of the successful Union attack on Missionary Ridge is legendary: Union forces originally assigned to capture the rifle pits at the base of the ridge pushed up the slope without orders, primarily to escape defensive fire from above. They scaled the ridge in a loose, skirmish formation, not firing until they reached the crest.

As we can see from the above map the slope of the Union attack up Missionary Ridge is, at points, greater than 20°. In Brent Nosworthy’s, Roll Call to Destiny: The Soldier’s Eye View of Civil War Battles he writes (page 250), “One of the most notable characteristics of this engagement was the relatively light number of casualties suffered by Van Derveer’s attack force, even though it had to break through two sets of fieldworks.” “To the untrained eye looking at the defenses way up on Missionary Ridge… the Confederate position must have appeared impressive, possibly impregnable, and if not impregnable, then capturable only after the expenditure of many lives. This was the opinion of the Confederate commanders who had chosen to defend the position. (page 252)” “Unfortunately for the Confederates, the military reality was quite the opposite. A high ridge immediately above a steep gradient is one of the worst imaginable defensive positions, about equivalent to placing one’s forces in a line with their back to a river and no avenue of retreat. (page 253). ”

This map of Fredericksburg from the Library of Congress (1931) shows a 90 foot rise in elevation above the plain for Marye’s Heights.

Union forces attacking up the gentler slope at Fredericksburg were not so fortunate. Except in a few steep places that offered shelter from Confederate artillery most of the Union attack was under constant fire. Quoting from Nosworthy’s Roll Call to Destiny (page 129), “a British artist on assignment for the Illustrated London News would recall the effect of the artillery fire on the advancing  Union lines: ‘I could see the grape, shell, and canister from the guns of the Washington Artillery mow great avenues in the masses of Federal troops rushing to the assault.'”

Nosworthy, in, The Bloody Crucible of Courage: Fighting Methods and Combat Experience of the Civil War, writes (422-3), “It had long been a general maxim that artillery should only be placed at the top of a slope which it could defend by itself. The artillery had to be able to direct an unobstructed fire against the base of the hill otherwise the enemy force could form in the dead zone and begin its assault up the hill unopposed by the artillery. Officers were cautioned, however, against ever placing artillery on either steep hills or high elevations. Ideally, artillery was placed on elevations whose height was 1% of the distance to the target and were never to be placed upon hills where the elevation was greater than 7% of this distance. When artillery was required to defend a lofty hill or elevation, whose height made it impossible for the artillery to command the base, artillery officers were advised, if at all possible, to place the battery lower along the slope, such as at the halfway point.” The problem of course, was that artillery could not lower the barrels of their guns sufficiently to fire down steep slopes.

Slopes in General Staff

General Staff does not use hexagons or ‘zones’ of any sort. One of the failings of a system using hexes is that the entire hex has one elevation; there are no gradual slopes, just precipitous cliffs. From primary source elevation and topographical maps (like below) three-dimensional battlefields are constructed in the General Staff Map Editor (see below).

Topographical map with contour lines of Keyes’ attack at the battle of 1st Bull Run. From Wikipedia. Click to enlarge.

The General Staff Map Editor has a Terrain Visualizer tool (see below). It allows a line to be drawn between any two points on the map and a cross-section of the terrain and elevation to be displayed.

The area of Keyes’ attack in the General Staff Map Editor showing the cross-section Terrain Visualizer with slope calculations along the blue line drawn between the two user selected red circles. The white circle on the blue line is the current point being displayed by the vertical line in the Terrain Visualizer.

In the above image we see that the steepest part of the slope up Henry House hill is 19°. This is confirmed by the contour map, above and a photograph of the actual area below:

This panorama photographic view of the area covered by Keyes’ attack at 1st Bull Run was taken by Johnnie Jenkins December, 2020. The Robinson House was beyond the large tree, center. Click to enlarge.

As always, please feel free to contact me directly (Ezra[at]RiverviewAI.com) if you have any questions or comments.

References

References
1 I contacted respected military historian and researcher Brent Nosworthy who wrote back, “The effects of slopes on the speed of movement and the cohesion of troops is a very interesting question indeed. I am enclosing a rough draft of a chapter from The Metrics of War booklet I was working on last year. I think here and there is some information as to how it affected beast of burden’s ability to draw artillery. There were several articles about defending and attacking heights in Rider, John (Editor); British Military Library: A Complete Body of Military Knowledge; second edition, 2 volumes, London, 1798-1801. I cannot remember if there were specific references to these issues in these articles. I also recommend if you have not already consulted: Tielke, Johann Gottlieb, The field engineer; or instructions upon every branch of field fortification: … with plans and explanatory notes. Translated from the fourth … London, 2 volumes, 1789. Russell, John (Lieutenant – 96th Regiment of Foot); A Series of Military Experiments of Attack and Defence, Made in Hyde-Park, in 1802, London, 1806. Adye, Ralph Willet; The Bombardier, and Pocket Gunner, Second Edition, London, 1802. However, I am not certain they contain any references to the effect of the angle of slope on speed and cohesion.”

Movement & Maps

Screen shot showing unit movement arrows for the battle of Antietam scenario. Note how movement is stopped by the small creek in the upper left hand corner of the screen. Click to enlarge.

I‘m in self-quarantine. As many of you know, I had a bone marrow / stem cell transplant in 2014 followed by a year of intense chemo. I’m fine (all things considering) but my immune system took a beating. In 2014 H1N1 put me in the hospital for 3 days so I’m taking COVID-19 seriously as, uh, the plague. In a way, being cooped up in the house (the weather hasn’t been cooperating, either, as I had hoped to replace my daily gym workout with long walks with my dog, George) is a lot like a typical upper Midwestern winter: it’s what I call ‘good programming weather’. There’s not much else to do but hunker down and write code. So, obviously, I’m working on General Staff and I wanted to show you an update (above).

General Staff is being written in C# and Windows Programming Foundation (WPF). There are a number of technical reasons why this was a good idea but I’m not overly familiar with WPF and doing some basic things, like creating these transparent movement arrows, took far longer, and involved a lot more programming, than I thought it would.  My partner on this project, Andy O’Neill, is a WPF rockstar; I’m a novice. I would much rather be working on the ‘under the hood’ stuff (like AI) but for the last week or so I’ve been working on movement arrows while Andy is busy with another project (the kind that pays the rent). Anyway, I’m very pleased about how they turned out. Please feel free to write me with comments.

Movement arrows for units at Quatre Bras. Note how blue units are stopped by the stream feeding the large pond. Click to enlarge.

Forward movement of this blue division is stopped by this tiny creek.

But, I also discovered a very interesting problem while testing these movement routines: our maps are too good! If you look at this detail (right) from the Antietam screen capture (above), you’ll see that movement is stopped when it encounters a tiny creek. I’ve walked that area of the Antietam battlefield and that little creek (well, I think it would be more properly called a ‘crick’) wouldn’t stop a division moving forward. However, the movement validation routines stop units from crossing bodies of water (except in column formation while crossing a bridge or a ford).  Ed Kuhrt, who digitized these great maps and copied every small detail was, perhaps, too precise. Definitely better to err on the side of being too precise when it comes to maps, Ed.

We’re seeing the same thing at Quatre Bras (above): the little streams that feed Materne Pond (Etang Materne) are also stopping the French from attacking. I haven’t been to Quatre Bras but I know the French crossed the small streams to attack the Anglo-Allied army’s positions.

Luckily, fixing this is easy. If you have done any work with the General Staff Map Editor you know that erasing terrain features, like water, is quick.

Removing the water in the little stream that feeds Antietam Creek by placing a ‘field’ over the water. Note that the ‘Field’ object is ‘above’ the ‘River’ object on the left Edit Terrain tab. Screen shot. Click to enlarge.

In the above screen shot we’ve opened the Antietam map in the General Staff Map Editor and drawn a ‘Field’ over the ‘crick’ that kept the Union forces from advancing. Note that both the Field and the River are objects and whichever object is higher in the list on the left ‘overwrites’ lower objects. If, for whatever reason, we wanted to restore the water in the creek we could either delete the Field or move it lower down the list than the River object.

Edit: After originally posting this, some readers (see comments, below) suggested that units crossing a small stream should suffer a movement penalty. This is absolutely correct. Instead of ‘painting’ with ‘field’ terrain, I should have used ‘mud’. This allows for a movement penalty (set in the Scenario Editor).

Adjusting unit type speeds across various terrain types in the General Staff Scenario Editor. Screen capture.

And now that that obstacle to movement has been eliminated the I and XII Union Corps can advance:

Now that the water has been removed from the little stream feeding Antietam Creek the Union forces can advance again. Screen shot.

As always, I would love to hear any comments or feedback that you may have.