SPI, THE ARDENNES OFFENSIVE (1973)
THE ARDENNES OFFENSIVE is an operational simulation — based on the KURSK Game System — of the German attempt to break through a thinly-held section of the American front in December, 1944. The game was designed by James F. Dunnigan, and published in 1973 by Simulations Publications, Incorporated (SPI).
HISTORICAL BACKGROUND
The German plan was a simple one: the Wehrmacht would tear a hole in a weak section of the American line and then rush powerful panzer forces through the newly-formed gap; as soon as the leading panzers had forced a crossing of the Meuse River and gained freedom of maneuver, they would then pivot northwest and drive on the Allied supply port of Antwerp.
Subsequent events would show that von Manteuffel’s men had made a costly mistake. The hasty decision to bypass Bastogne, although the local panzer commanders didn’t realize it at the time, had put the whole German offensive in jeopardy. And it was a lost opportunity that would come back to haunt the Germans as the battle wore on.
DESCRIPTION THE ARDENNES OFFENSIVE is a two-player operational (division/brigade/regiment) level simulation of the decisive period — 16 December, 1944 through 2 January, 1945 — during which the outcome of Hitler’s final desperate gamble — the last great German offensive in the West — was decided. The playing area of the game map represents the Ardennes, a forested region where the frontiers of Germany, Belgium, France, and Luxembourg all intersect. This was the area in which most of the major action of the historical battle actually took place. The two-color game map is relatively unambiguous, although a few terrain changes are required; these, however, have been noted in the game errata. In addition, for ease of set-up, the historical positions for all of the starting units are printed on the game map.  THE ARDENNES OFFENSIVE is played in game turns which are further divided into a German and an Allied player turn. One player controls the Germans, and the other player commands the American and British forces that fought to thwart Hitler’s offensive plans. The German player is always the first to act. Each player turn proceeds in the following order: the Reinforcement Phase; the Supply Determination Phase; the Initial Movement Phase; the Combat Phase; and the Mechanized Movement Phase. On the first game turn only, the Allied player may not move any of his eligible units during the Initial Movement Phase. Interestingly, neither player may move any otherwise eligible units during the Mechanized Movement Phase if they fought during the immediately preceding Combat Phase. For this reason, unengaged mechanized reserves are critically important for both sides.  Supply, as it did in the historical campaign, plays a critical role in THE ARDENNES OFFENSIVE; for this reason, the rules governing the determination of supply status for both sides are both detailed and comparatively complicated. Supply effects, on the other hand, are fairly straight forward: “supplied” units operate using their face combat and movement values; “unsupplied” units are halved on attack and in movement; “isolated” units are both halved on defense and in movement, and their attack strength is reduced to zero. Zones of Control (ZOCs) are “rigid” and individual units must halt movement upon entering and may not exit an enemy ZOC, unless stacked with one or more other friendly units. In this case, one unit “absorbs” the enemy ZOC, allowing the other units in the hex to exit or even to infiltrate around the enemy unit’s flanks. Stacking of combat units is limited to one “division equivalent” per hex. There are no artillery units included in the counter-mix; however, the influence of artillery on the battle is neatly reproduced through an abstract but restrictive (for the German player, at least) set of "bridge interdiction" rules. Combat is resolved using an “odds differential” Combat Results Table (CRT), but there are two different CRTs: the Initial German CRT and the Standard CRT. As is typical with the KURSK family of games, combat results tend to be of the “bloodless” variety with most battles producing retreat results (in varying numbers of hexes) for one or the other player. Defender Eliminated and Exchange results do not even appear until odds of 4 to 1, or higher. Terrain Effects are relatively uncomplicated. As might be expected, rivers represent a serious barrier to movement and the “West Wall” hexes multiply the defensive value of defending German units. The most important terrain effect is that of towns: units defending in towns are affected only by DE and Exchange results; all retreat results (whether DR or AR) are ignored. Needless-to-say, this rule has a profound effect on the overall flow of the game.  Victory is determined on the basis of victory points; these points can be amassed by the German player through the capture of geographical objectives, and, for both players, through the destruction of enemy combat strength. THE ARDENNES OFFENSIVE, besides the Historical Game, also offers nine additional scenarios, each of which allows the players to experiment with different set-up and reinforcement options. Conveniently, these alternative game situations have been scored by the designer as to which side they favor, and so can be used to vary lines of play or to adjust play-balance between unequal opponents. There are no “optional rules.” A PERSONAL OBSERVATION
Design Characteristics:
Game Components:
Recommended ReadingSee my blog post Book Reviews of most of these titles; all six of which are strongly recommended for those readers interested in further historical background.THE WEST POINT ATLAS OF AMERICAN WARS (Complete 2-Volume Set)  ; edited by Brigadier General Vincent J. Esposito; Frederick A. Praeger, Inc. (1959); ASIN: B000MTBTEU
HAPPY THANKSGIVING! As we celebrate this Thanksgiving with our families and friends, let us take a moment to remember all those whose lives and circumstances have been made more precarious by our Nation’s current economic problems. And let us also remember those who presently serve in faraway places on our behalf. This year has been a challenging time for many Americans, but let us hope and pray that the year to come will be better and more prosperous for all of our fellow citizens, both friends and strangers, alike. SPI, SINAI (1973)
SINAI is a historical simulation of the 1956, 1967, and 1973 Arab-Israeli Wars. The game also includes a collection of hypothetical (what if?) scenarios for an Arab-Israeli War that might have occurred (but didn’t) in the mid 1970’s. SINAI was designed by James F. Dunnigan and published in 1973 by Simulations Publications, Incorporated (SPI).
HISTORICAL BACKGROUNDOctober 6, 1973 was Yom Kippur (the Day of Atonement), the holiest day in the Jewish calendar. It was also the day on which Syria and Egypt suddenly attacked an unprepared Israel on two fronts simultaneously. The sudden large-scale offensive by Syrian forces on the thinly-held Golan Heights, in concert with the totally unforeseen, but crushing Egyptian breakthrough of the Bar-Lev Line on the east bank of the Suez Canal rocked the political and military leadership of Israel as few events had before. For the first few days after the initial Arab attacks, the Israeli Prime Minister, Golda Meir, feared for the very survival of the Jewish State. However, it did not take long for the Israeli military leadership to recover its balance and to mount a counterattack. . On 8 October 1973, General Schmuel Gonen, Commander of the Israeli Southern Front, ordered a full-scale armored offensive against the hastily-prepared Egyptian Sinai defenses east of the Suez Canal. His goal was to smash into the advanced Egyptian positions, break through and then push his armor into the enemy rear to rescue any surviving Israeli soldiers still holding out in parts of the Bar-Lev Line. Unlike previous Israeli-Arab engagements, however, the unthinkable happened: Egyptian soldiers held their ground and decimated the attacking Israeli armor with long-range Sagger missiles. General Gonen, shaken and confused by the unexpected failure of his attack, lapsed into a mental fugue; stunned by the defeat of his plan, the Israeli commander was unable to decide what to do next. Clearly, the resilience and defensive skill of the Egyptian Army had been a complete surprise to the Israeli Defense Forces (IDF) High Command, but something still had to be done about Sadat’s army on the east bank of the Suez Canal. A static IDF defense was not the answer; the Israeli tanks tied up against Egypt were desperately needed on the Golan Heights, where the Syrians continued to vigorously press their attack against the out-numbered Israeli defenders. On 10 October, Gonen was quietly replaced by General Chaim Bar-Lev. By 11 October, Bar-Lev and two of his senior commanders, Major Generals Ariel Sharon and Avraham “Bren” Adan, had come up with a completely new plan of action: one that, all three men fervently hoped, would both encircle the Egyptian Third Army and reverse the military situation on the east bank of the Canal. Their plan was based on newly-obtained American reconnaissance photos that had revealed a narrow gap between the Egyptian Second and Third Armies. This audacious Israeli armored offensive was code-named “Operation Stouthearted Men,” and it would begin with Sharon’s division driving through the gap in the Egyptian front, while Adan’s division attacked the exposed flanks of the Second and Third Egyptian Armies. Once Sharon’s unit had slipped through the enemy lines, it would then advance on Deversoir, destroy any Egyptian forces that it encountered there, and then move on to quickly seize bridgeheads on both banks of the Suez Canal. If Sharon was successful in this critical first phase of his mission, a mobile bridging-train would immediately rush to the newly-captured bridgeheads, and once the portable bridge was emplaced, Israeli forces would pour cross the Canal and completely cut the Egyptian Third Army off from food, ammunition, and most importantly, from water. Unfortunately, time was rapidly running out for the IDF. Faced with temporary stalemates in both the Sinai and on the Golan Heights, what Israel now needed more than anything else was a decisive battlefield victory: one that would transform the strategic situation and force the Jewish State’s enemies to seek peace on Israeli terms. And such a victory would have to come soon, before a UN ceasefire resolution could be forced on Israel that would end all fighting and preserve the existing Arab territorial gains. This daring armored operation, General Bar-Lev believed, could produce just such a victory. The jump-off date for “Operation Stouthearted Men” was fixed for 15 October, 1973. The ferocious clash that would result from this Israeli armored operation, however, would — in a matter of a few days — come to be known by a completely different name: the “Battle of Chinese Farm.” DESCRIPTION SINAI is a battalion/brigade level simulation of three of the most important wars that have, over the years, periodically erupted in the Middle East ever since the establishment, under UN auspices, of the Jewish State of Israel on 15 May, 1948. The planned centerpiece of this set of games was originally the ’67 War, but in the process of designing SINAI, the Yom Kippur (or Ramadan or October) War broke out. This unexpected development obliged SPI to postpone final publication of the game until the ’73 War had ended, and another set of scenarios based on the (then) latest installment in the chronicle of Arab-Israeli conflicts could be designed, developed, and play tested. The rapidly-changing face of the Yom Kippur War presented an unusual situation for the designer, Jim Dunnigan, who for the first time in his professional life, had to test his design assumptions against daily and sometimes contradictory newspaper stories. The effect on SINAI of these contemporaneous reports is inescapable. It is clear from the similar game systems used for the ’56 and ’67 Wars, and the significantly different system used for the ’73 War (and the hypothetical mid-70’s scenarios) that the unfolding battlefield developments led the designer to conclude that the force structures, doctrines, and weaponry of the belligerents had changed significantly from 1967 to 1973. The ’56 and ’67 War scenarios in SINAI are played in game turns, each of which represents twelve hours of real time. The (12 hour) turn sequences for both the ’56 and ’67 War scenarios are identical, and follow a rigid sequence of player operations: (Israeli) supply phase; movement phase; combat phase; (Arab) command and control phase; supply phase; movement phase; combat phase; and Jordanian participation phase. Game mechanics for both scenarios are logical and uncluttered. Stacking is limited to three units per hex, and zones of control (ZOCs) are “rigid” but not “sticky.” Combat between adjacent units is voluntary, and “overrun” attacks are possible if the attacker can muster a sufficiently high attack differential against a weakly-defended enemy hex. The Supply Rules are comparatively simple: units are either “supplied” or “unsupplied.” However, the Supply Effects differ for the two sides: “unsupplied” Arab units may not attack, and are halved for movement and defense; “unsupplied” Israeli units, on the other hand, are halved in movement and attack, but their defense strength is unaffected. Interestingly, the game uses a “strength differential” rather than an “odds differential” type of Combat results Table (CRT). Terrain Effects are important both to movement and to combat, and, as might be expected, these rules affect the two sides very differently. The ’67 War scenarios also introduce Air Rules, but these are highly abstracted and, not surprisingly, strongly favor the Israeli player. If all of this wasn’t enough, Special Rules limiting Arab cooperation, command and control, movement, morale (panic), and supply capabilities all operate to further constrain the Arab player’s strategic and tactical options. In short: the Israeli player’s units have greater combat power, better mobility, fewer supply problems, and no command and control restrictions. They also have, in the ’67 War scenarios, absolute air superiority, and an airmobile unit available, as well.  In the ’73 War (and hypothetical mid-70’s) scenarios, the structure of the simulation is altered in a number of important ways. These scenarios increase the time period covered by each game turn from twelve to twenty-four hours, and they also use a variation of the KURSK Game System as the basis for the game’s basic design architecture. The new (24 hour) turn sequence proceeds as follows: (Arab) first supply phase; first movement phase; combat phase; Jordanian participation phase; second supply phase; second movement phase; (Israeli) first supply phase; first movement phase; combat phase; second supply phase, and second movement phase. The increased mobility of both sides along with the two impulse movement system tends to produce a much more dynamic and fluid battle area than in the previous scenarios. The Air Rules for the ‘70s scenarios are also much kinder to the Arab player; the power of the Israeli Air Force, particularly in the early going, is severely curtailed. In addition, the ’73 War scenarios include a number of other important rules changes that benefit the Arab player: the Arab command and control and panic rules disappear; movement capabilities are improved; the Arab player has “surface to air” (SAM) missiles; and the supply rules for Arab combat are less restrictive.  SINAI, as already noted, offers three main historical scenario packages (or games within a game): the 1956 War; the 1967 War; and the 1973 War. Given the volatile nature of Middle East politics, however, SINAI also includes — besides the historical games — a set of hypothetical scenarios for renewed conflict between Israel and its Arab neighbors sometime in the mid-seventies. In addition to these historical and hypothetical situations, the game presents a series of “what if?” scenarios for the players to explore. These optional scenarios all benefit the Arab player to one degree or another, and include changes to the historical situation such as, but not limited to: free set-up; Israel napping (caught by surprise); better Syrian and Egyptian officer corps; increased Arab cooperation; and a combination of all of the above in the Arab fantasy “Jihad” scenario.A PERSONAL OBSERVATION The ’56 and ’67 Wars were quick, decisive Israeli victories; the ’73 “Yom Kippur” War, on the other hand, was clearly different in a number of important ways. Some examples of these important differences are immediately obvious: the Arabs struck first, achieving strategic and tactical surprise; Soviet anti-tank weapons contributed greatly to the defensive combat power of the Arab forces; and heavy concentrations of SAM missile sites were very effective in neutralizing the Israeli Air Force in the early stages of the war. The historical scenarios covering the ’56 and ’67 Wars are, as might be expected, pretty much a romp for the IDF (Israeli Defense Forces), although the victory conditions and optional rules can make these games a lot more competitive. The scenarios for the ’73 War, as well as those for the hypothetical mid-70’s War, make for much more interesting and competitive games. As has already been noted earlier, the Arab Armies improved dramatically between 1967 and 1973. Israel’s enemies came surprisingly close to victory in the Yom Kippur War, SINAI attempts to help its players understand how this happened and why.Unfortunately, despite its many good points, SINAI — like many of James F. Dunnigan’s early designs — is a disappointment; and, taken as a whole, it can probably best be described as an ambitious and intriguing “near miss.” The ’56 and ’67 historical scenarios both require a lot of fiddling with the victory conditions to produce anything approximating a reasonable amount of play balance; a fact that, not surprisingly, makes it hard for most players to summon up much enthusiasm when it comes to commanding the seriously out-classed Arab armies in these earlier scenarios. The ’73 and mid-’70s scenarios are much more interesting, yet they each seem to lack something intangible, both as games and as simulations. Of course, it is possible that the constant changes in the game’s developmental trajectory forced by the day-to-day news reports coming in from the battlefield were, in 1973, a little more than Dunnigan or SPI could handle at the time. This is not to say that SINAI is a particularly bad game, only that it has a curiously “cobbled together” feel, and that it probably could have been — had it not been rushed into print — considerably better with a little additional effort. Clearly, Dunnigan was in a hurry to publish this title, and it shows. For supporting evidence for this last argument, by the way, one only has to look at John Hill’s excellent and richly-textured treatment of the ’73 War, BAR-LEV, which appeared some time after SINAI, in 1974. The difference in quality between the two games is glaring. Design Characteristics:
Game Components:
SPI, NAPOLEON AT WATERLOO (1971, 1979)
NAPOLEON AT WATERLOO is an grand tactical (division/brigade) level simulation of the climactic clash between the French Army, under Napoleon, and the Anglo-Allied Army, commanded by the Duke of Wellington, near the Belgian Hamlet of Waterloo, on 18 June, 1815. NAPOLEON AT WATERLOO was originally mailed, at no charge, to new subscribers of S&T Magazine. It was intended to be a simple, introductory game for those new to conflict simulations. The game was published in two versions: the original (two-color) brown on tan edition which was offered during the very early days of SPI (beginning in 1971); and a later (1979) edition, in which SPI reformatted the rules, colorized the game map, and added a colored title sheet. NAPOLEON AT WATERLOO was designed by James F. Dunnigan, and first published in 1971 by Simulations Publications, Incorporated (SPI).
HISTORICAL BACKGROUND Emperor Napoleon Bonaparte astride his stallion Marengo at Waterloo.The morning of 18 June 1815 dawned cold and overcast, but with the promise of fairer weather as the day wore on. It had rained steadily during the previous day and through much of the night. The change in weather was a welcome relief to the soldiers who were bivouacked in the open. With the morning’s first light, thousands of men stirred and stoked their campfires; those among them who had found food — often no more than a potato — ate, and were happy to have anything at all. Two armies, only a mile or two apart, began the mundane business of preparing for battle. The shambling disorder of milling men and snorting horses gradually gave way to the discipline of the military camp. And, on the commands of their officers and other ranks, men began to assemble: noisy chaos gave way to order; companies came together to become battalions, and then battalions assembled and became regiments. With an unexpected sort of rough grace, the regiments formed into columns and, on the shouted orders of their officers, thousands of grim-faced soldiers gradually began to array themselves across the valley from each other; each in their own carefully-dressed lines.  Arthur Wellesley, Duke of Wellington, inspires his troops at Waterloo. Initially, despite the flurry of preparation on both sides, nothing much happened. The morning sun climbed higher in the sky, and the soldiers of the two armies: 67,000 men under the Duke of Wellington; and 72,000 commanded by Napoleon; all stood in bright, multi-colored ranks facing each other across a shallow valley matted with rain-soaked grass. Movement and even time, itself, seemed to come to a stop; in spite of all of the early morning’s bustle and hurried activity: no one on either side of the valley, except for quartermasters and dispatch riders, stirred from their serried ranks. Hours passed. Both splendidly uniformed hosts stood silently, fixed in place, like insects in amber. Then, abruptly and without warning, the stillness was broken. The soldiers in the ranks of both armies were suddenly startled by the first sounds of canon fire coming from somewhere on the French left. The Battle of Waterloo had begun at last with a French bombardment of the Anglo-Allied outpost that occupied the château of Hougoumont. No one then, or now, can be sure of the exact time of these first canon shots, but the cannonade probably began around 11:30 am. Whenever it was, the French artillery had sounded the overture for the bloody drama to come. The unnatural quiet of the morning had finally ended for the men warily watching each other across a sodden expanse of ryegrass. This tiny corner of Belgium had become a battlefield, and the morning’s unexpected quiet would now — on a patch of muddy ground no more than two miles wide and two-thirds of a mile across — give way to the noisy, cruel, and violent business of war. DESCRIPTION NAPOLEON AT WATERLOO is, as the title implies, a two-player simulation of, quite probably, the most famous single military engagement in history. At Waterloo, the two greatest generals of their age, Napoleon and Wellington, faced each other across a battlefield in Belgium for the first and only time in their long military careers. On the fateful morning of June 18th, 1815, the out-numbered Wellington had decided to offer battle to the French army confident that, unbeknownst to Napoleon, the Prussian army, under Marshal Blucher, planned to march to the Iron Duke’s aid. Thus, NAPOLEON AT WATERLOO is a race to see if Napoleon’s troops can break the poly-glot Anglo-Allied army before the Prussians arrive to turn the tide of the battle against the French. The game is played in game turns, each of which is composed of a French followed by Prussian Anglo-Allied (P.A.A.) player turn. Each player turn follows the same sequence, and is divided into two simple phases: the Movement Phase; and the Combat Phase.  NAPOLEON AT WATERLOO presents beginning players with game mechanics that are both simple and intuitively logical. To keep things uncomplicated, stacking is prohibited and terrain effects are minimal. In addition, because of the limited time-scale of the game, there are no supply rules. Zones of Control (ZOCs) are both 'rigid' and 'sticky'. This means that units must stop upone entering an enemy ZOC and may not exit such a ZOC except as a result of combat. In addition, combat between adjacent units is mandatory and is resolved using a traditional 'Odds Differential' Combat Results Table (CRT). Interestingly, although it is an introductory game, NAPOLEON AT WATERLOO does expose players to a number of useful game concepts; these basic concepts include: “locking” Zones of Control, Ranged Artillery, and the importance of Morale. And, while the consensus among experienced players is that the French have a marked advantage, it is still a surprisingly enjoyable game to play for both the French and the P.A.A. players. Player victory depends on the elimination of enemy units. The goal of each side is to inflict sufficient casualties on the other to cause the Demoralization of the enemy army. Each game turn represents one hour of real time, and a complete game is ten turns long. NAPOLEON AT WATERLOO offers players only the Historical Scenario, and there are no optional rules. However, based on this introductory title’s wide-spread, if unexpected popularity, Dunnigan decided to revisit and upgrade his original design. The result of this second look, by the game’s original designer, was the Advanced NAW EXPANSION KIT. This expansion, which included new, more-detailed rules (stacking was permitted and artillery attacks were resolved separately) and an expanded number of new (brigade-strength) replacement counters, was intended to meet the demands of those players who already owned the basic game, but who wanted to add increased tactical complexity and realism to the original simulation. A PERSONAL OBSERVATION Every once in awhile, I still dig out and set-up my old, much-worn, brown on tan copy of NAPOLEON AT WATERLOO, and whenever I do, I still feel a momentary rush of nostalgia for the early days of wargaming. This was not my first wargame, but it was the first of Dunnigan’s designs that I actually liked. I suspect that in this regard, I am probably not alone. It is also one of the best 'introductory' conflict simulations ever published, and it still holds up as an enjoyable “beer and pretzels” game, even today. But over and above all that, this simple little game also turned out, quite unexpectedly, to be a ground-breaking design. Ironically, the basic game system first introduced in NAPOLEON AT WATERLOO has proven, over time, to be one of the most popular and durable game platforms ever devised. Clean, simple, and eminently playable, the NAW Game System became the standard design architecture for most of SPI’s subsequent Napoleonic games, many of its Civil War games, and even a few titles that dealt with more modern combat situations. Thus, this game system appears in a broad array of later SPI titles such as BORODINO, AUSTERLITZ, the NAPOLEON AT WAR Quadrigame, the NAPOLEON’S LAST BATTLES Quadrigame, the BLUE & GRAY I and II Quadrigames, ROAD TO RICHMOND, 6th FLEET, and BATTLE FOR GERMANY, just to name a few.Design Characteristics:
Game Components:
Recommended ReadingSee my blog post Book Reviews of Waterloo, Day of Battle, and The Campaigns of Napoleon and Face of Battle; books that I recommend as highly-readable sources for those visitors who are interested in further historical background.For decorating the game room with a Napoleonic theme: SPI/TSR, LA GRANDE ARMÉE (1987)
LA GRANDE ARMÉE (1987) is an operational level simulation of Napoleon’s major campaigns in Central and Eastern Europe during the period 1805-1815. LA GRANDE ARMÉE was designed by Mark D. Acres and published in 1987 by Simulations Publications Inc. (SPI), which by this time had become a division of TSR, Inc.
HISTORICAL BACKGROUNDOn 22 September 1805, the seasoned General Mack, accompanied by Archduke Ferdinand, advanced at the head of 70,000 Austrian soldiers towards the Black Forest crossings near the Rhine River. This advance, Mack believed, would serve two ends: it would intimidate the pro-French Bavarians into abandoning their support for Napoleon; and it would also discourage any French forces in the area from moving east into the Danube River Valley.The Austrian military commander was largely unconcerned about the threat of French offensive operations because, like most of the senior Austrian and Russian officers and nobles of the newly-formed Third Coalition, he believed that Napoleon would, as he had in the past, make his main effort against the Coalition forces in Italy. In the unlikely event that Napoleon’s army did strike east, Mack’s Austrians were expected only to temporarily slow the French advance until Kutusov’s Russians, approaching by way of Vienna, could join with Mack’s troops on the Danube. Thus, in keeping with this plan and supremely confident of allied prospects, Mack had decided that his army should adopt, as its center of operations, the ancient fortress of Ulm which was strategically sited at the confluence of the Iller and Danube Rivers. This decision, it soon became obvious, was a costly miscalculation on the part of General Mack. It would not be his last. Within a week of the Austrian army’s ill-considered advance to Ulm, powerful French forces suddenly appeared without warning to the Austrian army’s front; and Coalition misapprehensions as to Bonaparte’s plan of campaign were immediately dispelled. Napoleon had again completely outwitted his enemies and seized the initiative by choosing to move directly against Austria, and not to march against the allied armies in Italy, as his Third Coalition adversaries expected. The French offensive was stunning in its speed and ferocity. In the final three days of September, Napoleon force-marched the 210,000 men of the French Grande Armée east into Bavaria in search of a decisive engagement with the Austrian army. The French Emperor, with characteristic decisiveness and energy, had, through furious marching, catapulted his army against the allied forces in the Danube region before they could even react. Blinded by Murat’s cavalry and unsure as to either French strength or intentions, Mack hesitated. His delay proved fatal. By the time the Austrian commander realized his danger, it was already too late. Events were moving too quickly for the allied situation to be saved, and even as Mack’s army began a belated withdrawal towards the east, Napoleon’s hard-marching soldiers were already enveloping the allied flanks. Despite several courageous Austrian attempts to break through the French cordon, the Austrian commander and much of his army was trapped. The inevitable end to this Coalition debacle was not long in coming; almost exactly one month later, the unlucky General Mack was compelled to parade a force of 25,000 infantry and 2,000 cavalry out of Ulm to surrender to the victorious French Army drawn up at the foot of the Michelsberg Heights. Napoleon's Ulm campaign had been a military masterpiece: an entire enemy army had been destroyed at almost no military cost to Napoleon’s Grande Armée. Moreover, Ulm was only a portent of things to come for the now reeling allies: another military disaster still lay in the future for the surviving soldiers of the Third Coalition; and Napoleon’s star would reach its zenith near the Moravian village of Austerlitz on 2 December 1805. DESCRIPTION LA GRANDE ARMÉE (1987) is a brigade/division level simulation of the series of campaigns waged by Napoleon against the various coalitions that united to oppose French military, economic, and political power in Central Europe from 1805 through 1815. Although this game shares the same title as the SPI game: LA GRANDE ARMÉE, that was designed by John Young and published fifteen years earlier in 1972; it is neither an expansion nor a refinement of the original game. Rather, it is much more reminiscent in feel and scale to Kevin Zucker’s design, NAPOLEON AT BAY. As an interesting aside (at least to me), Kevin Zucker was responsible for the four-color game maps in the new version; and they’re gorgeous. The cardboard game counters are easy to read and functional, but unlike those of many more recent Napoleonic titles, are not particularly colorful or visually interesting. Still, although significantly different from its predecessor, this newer version does offer an intriguing and richly-detailed approach to the problems confronting commanders during the wars of the Napoleonic Era. Regrettably, the game is not particularly accessible to beginning players: the rules, for example, are both lengthy and oddly-organized, and the game mechanics are not simple. Moreover, almost all of the additional simulation detail is unoriginal: in short, almost everything that sets this game apart from John Michael Young’s earlier SPI design can be traced to the game systems of other, widely-available Napoleonic games. This is not necessarily a bad thing, but it does suggest that this title’s author drew heavily on previous Napoleonic and Civil War designs for his simulation architecture and game mechanics.  The outline of the typical game turn in LA GRANDE ARMÉE (1987) reveals a great deal about the focus of the newer version’s design. Each game turn follows the same sequence of play: the Command Phase (both players secretly decide which of their commanders will command and which will receive orders); the Initiative Phase (the French player rolls to see who will move first); the Weather Phase; First Player Skirmish Phase; First Player Movement Phase; First Player Battle Phase; the Second Player Skirmish Phase; Second Player Movement Phase; Second Player Combat Phase; the joint Supply Phase; the joint Siege and Assault Phase; and the joint Rally Phase. Unlike the original 1972 version of LA GRANDE ARMÉE players certainly won’t finish the Ulm-Austerlitz scenario in a few hours; but for those looking for a detailed simulation of Napoleonic Warfare with a strong emphasis on command and control, and logistics, this game certainly attempts, at least, to fill the bill.  LA GRANDE ARMÉE (1987) offers eight comparatively short scenarios covering Napoleon’s operations against particular nations and/or coalitions; these are: the 1805 Campaign (France versus Austria and Russia); the 1806 Campaign against Prussia; the 1806-1807 Campaign (France versus Prussia and Russia); the 1809 Campaign against Austria; the 1812 Campaign against Russia; the 1813 Campaign (France versus Russia and Prussia, and eventually Austria and Sweden); the 1814 Campaign for the defense of France against the same coalition; and finally, the Campaign of the 100 Days (France versus Prussia and Britain). In addition to the shorter scenarios, the game also offers three Grand Campaign scenarios: Grand Campaign I (1805-1807); Grand Campaign II (1812-1814); and Grand Campaign III (1805-1815). A PERSONAL OBSERVATIONNapoleon Bonaparte once observed that, in the course of his long military career, he had fought over seventy battles. He was not exaggerating. His record, whatever one’s personal opinion of the French Emperor, is one of amazing martial accomplishments. Thus, it is not surprising that the many campaigns of Napoleon have, over the years, provided game designers with a bountiful source of subjects for conflict simulations. Whatever else can be said about it, the Napoleonic Era is simply a great historical period to draw upon for game topics. Most Napoleonic games, not surprisingly, have focused on individual battles. In addition to specific Napoleonic battles, however, a number of designers have also looked at particular campaigns for inspiration, and many of these designs — NAPOLEON’S LAST BATTLES (1976), 1815 (1975), LEIPZIG (1972), and 1812 (1972), to name a few — have been both interesting as simulations, and enjoyable as games. A few foolhardy designers, however, have been still more ambitious and have attempted to simulate the whole or at least the greater part of the Napoleonic Wars.LA GRANDE ARMÉE (1987), like WAR & PEACE (1980) and EMPIRES IN ARMS (1986), just to name two other examples, is an attempt to simulate — on a strategic/operational level — both individual campaigns and, for those gamers with too much time on their hands, the whole (or at least the greater part) of the Napoleonic Wars. In the case of this particular title, the designer’s success in meeting this complex set of simulation goals has, to say the least, been notably uneven. When it comes to modeling individual Napoleonic campaigns, LA GRANDE ARMÉE — like a number of other, earlier titles — seems to do a workmanlike, if uninspired, job of it. However, to actually play the game requires a bit of patience and inventiveness on the part of players because gaps in the game system seem to show up at the most inopportune of times. This has led some critics of the game to suggest that the TSR version of LA GRANDE ARMÉE is unplayable; that's probably going a little too far. On the other hand, as noted earlier, this new title really introduces nothing that is truly original or innovative into the Napoleonic design mix; which is to say that the game system when it can be teased into working, still feels very familiar in a derivative, "cut and paste" sort of way. To make matters worse, the “really big” 1805-1815 Campaign Game III just doesn’t — based on my own admittedly limited experience — seem to hang together at all when it comes to presenting a seamless, integrated simulation of all of Napoleon's major campaigns in Central Europe. To be fair, this is neither unusual nor that much of a surprise. Because of the very real limits that time and money impose on any commercial game’s development, it is very rare for a campaign monster game to work exactly as the designer intended, without post-publication tweaks to fix the inevitable problems that didn’t show up during the developer’s original play tests. Still, while these types of design stumbles may have been acceptable when GDW's DNO first appeared in 1973, it is really frustrating to find the same types of problems in a game published fourteen years later. So where does all this leave us? First, although I am personally very fond of the older, John Young version of LA GRANDE ARMÉE, I am, none-the-less, willing to weakly recommend LA GRANDE ARMÉE (1987) as a flawed, but salvagable game system for anyone with the willingness to do the many fixes necessary to make the game work. However, for the player with a serious and wide-ranging interest in the various Central European campaigns of the Napoleonic Era, this title, although interesting, is probably more trouble than it is worth. Stated differently, as a comprehensive simulation treatment of the most important decade of the Napoleonic Wars, 1805-1815, I am only barely persuaded that LA GRANDE ARMÉE can, even with a considerable amount of post-publication player input, be made to deliver a manageable and realistic simulation of 19th Century European warfare. In view of that, when it comes to doing a good job of recreating, in abstract form, the entire Napoleonic Era, I am therefore strongly disposed to favor the less orthodox, more politically-grounded, and inclusive EMPIRES IN ARMS over LA GRANDE ARMÉE (1987). EMPIRES IN ARMS may be weak as a military simulation, but it covers all of Europe and it still seems to get a surprising number of this fascinating historical period’s other 'important' elements right. And besides, its graphics are uniformly excellent, and with a decent mix of knowledgeable, experienced opponents, it is a real blast to play! Design Characteristics:
Game Components:
Recommended ReadingSee my blog post Book Review of this title that I recommend for further historical background. Recommended ArtworkHere's a Giclee print map of the battle available in various sizes that is great for a Napoleonic themed game room's wall. HAPPY VETERANS DAY!A Time to Honor Those who have Secured Our Freedoms and Our Way of Life throughout the History of This RepublicThis Veterans Day is, because of the recent tragedy at Fort Hood, an especially poignant reminder of the many extraordinary sacrifices that our men and women in uniform, both at home and abroad, make daily on our behalf.  Being a Vietnam veteran, myself, and given America’s checkered history it its treatment of its veterans, I have probably not treated this holiday with as much seriousness as it deserves. However, as I have gotten older, I have come to realize that while our country may occasionally suffer its lapses when it comes to recognizing those who now bear, and who have borne the past burden of the nation’s defense; in the end, the fundamental decency and goodness of ordinary Americans comes through again and again. So, on this Veterans Day, I salute the servicemen and women who repeatedly go into harm’s way on our behalf, and I also salute the countless numbers of civilians who, in ways too numerous to recount, honor the service of our veterans, both past and present. Finally, in keeping with my thoughts on this Veterans Day, I have decided to include a short discussion of the origins of this, often misunderstood, national holiday. A Brief History of this Special Day of Remembrance On the 11th hour of the 11th day of the 11th month of 1918, World War I — the “War to End All Wars” — finally came to an end with the formal acceptance by representatives of the German government of the Allied terms for an Armistice. The Continent was again at peace, and the carnage of four years of industrialized warfare, after consuming the greater part of a generation of European youth, had finally sputtered to an end. After the guns became silent in 1918, many European countries came to commemorate November 11th as a day of remembrance and thanksgiving. In the British Commonwealth, the red Poppy became the symbol for the end of the First World War’s bloodshed and the advent of peace, and remains so to this day. Across the Atlantic, American President Woodrow Wilson proclaimed the national observance of the first Armistice Day for November 11, 1919. Seven years later, the U.S. Congress passed a concurrent resolution calling for the President to again declare a formal observance of November 11th as a day of remembrance for all those Americans who had fallen during the Great War. Finally, on 13 May, 1938, the U.S. Congress enacted legislation to make Armistice Day a legal holiday.  In 1953, thanks mainly to the efforts of an ordinary store owner named Al King from Emporia, Kansas, a movement gathered momentum in the United States to transform Armistice Day into a national holiday that would celebrate the sacrifices of all American veterans, not just those who had served and died during World War I. This change was formally recognized when President Dwight Eisenhower signed the new measure into law on 26 May, 1954. A few months later, Congress amended the language of this act to replace the word “Armistice” with that of “Veterans” and, with this final change, our current federally-mandated holiday took on its present-day form.As the preceding account illustrates, our understanding and appreciation of Veterans Day and what it represents has gone through a number of changes over the years, but the dependence of our society on the sacrifices of veterans has been a constant reminder that the American way of life comes at a cost, and that we, as a nation, are fortunate that one generation after another of our fellow citizens has been willing to bear that cost. SPI, FULDA GAP (1977)
The FULDA GAP is an operational-level simulation of a hypothetical attack into West Germany by Soviet-led Warsaw Pact forces in the late 1970’s. FULDA GAP uses the PANZERGRUPPE GUDERIAN Game System and was designed by James F. Dunnigan. It was published in 1977 by Simulations Publications, Incorporated (SPI).
HISTORICAL BACKGROUNDAlmost from the day that Nazi Germany surrendered to the Allies in 1945, the newly-partitioned country became a flashpoint for Cold War tensions between the Eastern Bloc, dominated by the Soviet Union, and NATO, under the leadership of the United States. On 24 June 1948, the Soviets blockaded Berlin by closing off all rail and road access to the American, British, and French zones of the city in an attempt to gain complete control of the divided former German Capital. The United States, Great Britain, and other members of the British Commonwealth responded with the Berlin Airlift. Hurriedly organized and directed by American general Curtis LeMay, the operation proved to be a stunning success. At its peak, the airlift was delivering over 13,000 tons of food to the beleaguered city every day. After months of East-West tension, and faced with an embarrassing political and military failure, the Soviets finally ended the blockade on 12 May 1949. However, they did not abandon their designs on achieving control of West Germany.Given the ongoing belligerence of the Communist leadership in the Kremlin; their ruthless suppression of the peoples of Eastern Europe, and their aggressive political adventurism in Africa and Latin America, the possibility of a Warsaw Pact invasion of Western Europe quickly became a key feature of NATO planning as the Cold War continued. The two most likely routes for a Soviet mechanized offensive into West Germany were obvious: the North German Plain, and the Fulda Gap. However, given the strategic Cold War importance of Frankfurt, as West Germany’s economic heart, the Fulda Gap was considered to be the primary axis for a Warsaw Pact attack against the NATO forces arrayed to defend Germany. Because of this fact, military planners on both sides of the “Iron Curtain” saw the Fulda Gap as the most likely site of the first major battle of a 1970s war between East and West. The Fulda Gap is, geographically speaking, unremarkable. It is a swath of low ground that lies between the Hohe Rhön and Knüllegebirge mountains near the East German border, and the Spessart and Vogelsberg mountains farther to the west. This low-lying corridor runs along the Fulda River and then through the Fliede and Kinzig Valleys and debouches onto the open terrain bordering the Main River near Offenbach in the north and Wurzburg in the south. Militarily speaking, this relatively flat ground was considered, by both NATO and Warsaw Pact operational planners, to be excellent terrain for large-scale mechanized operations.  During the 1970s and 80s, the forces squaring off across the East-West German border were well-known to each other. If the Warsaw Pact launched an offensive through the Gap, it would undoubtedly be spearheaded by the Soviet 8th Guards Army, based in East Germany. The Soviet 1st Guards Tank Army would, NATO planners thought, follow-up the initial attackers and serve as a reserve force for the Soviet first wave. The 8th Guards Army's objective, if war broke out, would be simple: batter its way through any NATO forces that blocked its path and seize Frankfurt am Main. On the NATO side, the responsibility for defending the Gap between 1972 and 1994 rested with the US Vth Corps. The American trip-wire unit closest to the East German border — the NATO force assigned to meet the initial Soviet assault — would be the 11th Armored Cavalry Regiment. The 3rd Armored Division and the 8th (Mechanized) Infantry Division were slated to move east immediately to support the troopers of the 11th Cavalry Regiment. Their orders were blunt and unequivocal: they were to hold the Gap until NATO reinforcements could reach the front. An American fighting withdrawal, considering the strategic importance of Frankfurt, was not considered to be an option. DESCRIPTION The Fulda Gap is an area in southern Germany that, for more than a generation during the Cold War, American and Soviet planners viewed as a potential battlefield in any conflict between NATO and Warsaw Pact Forces. FULDA GAP is a semi-historical simulation of such a confrontation on a regiment/brigade level. The FULDA GAP four-color game map covers an area of southern Germany that extends from Koln in the north to Mannheim in the south, and from Bonn in the west to Bamberg in the east. The back-printed game counters represent the actual NATO and Warsaw Pact units (typically regiments and brigades) that would have fought each other had war broken out in Germany during the period covered by the game. All of the formations in the game begin play as 'untried' units; their actual combat strength is determined through a semi-random process only when they engage in combat for the first time. Zones of control (ZOCs), as might be expected, are semi-active and 'sticky': this means that units must stop upon entering an enemy ZOC and may only exit either as a result of combat or through 'disengagement'. To model the complex elements of modern warfare, the FULDA GAP game system weaves a number of innovative design features into a well-tested turn sequence. The standard game turn sequence proceeds as follows (the Soviet player is always the first player): Initial Movement Phase; Combat Phase; Secondary Movement Phase; and Reorganization Phase. The Advanced game rules add a Joint Air Superiority Turn prior to the start of the regular game turn. Once the air war sub-routine ends, the Advanced game turn begins with the addition of a Nuclear Planning Phase, and a Nuclear Strike Phase to the standard player turn sequence. The rules for combat in FULDA GAP are generally familiar and, because of the important role of ranged artillery for both offensive and defensive fire, are somewhat reminiscent of those for MODERN BATTLES (1975). Regular combat between adjacent units is voluntary and is resolved using a conventional odds-differential Combat Results Table (CRT). However, while the CRT is familiar, the various combat results are not. Instead of stipulating step or strength losses, individual combat results specify losses in terms of Retreat Points (RPs). This somewhat unorthodox approach works well because terrain effects are also presented in terms of RP values. Thus, if a phasing player is attacking a unit defending in a rough terrain hex (RP value of 3) and receives a combat result of 2 or less, the defender would not be required to retreat; however, if, instead, the combat result is 5 RPs, the defender would then be obliged to retreat two hexes (assuming the flight hexes were clear terrain): 3 hexes for the rough terrain hex (3 RPs, remember), and 1 RP for each of the 1 RP valued clear terrain hexes. Interestingly, although this combat results system is somewhat cumbersome to describe, it actually works very well in the context of the game.  FULDA GAP does not lack for operational detail. The game includes rules on, among other things: limited intelligence (untried unit strengths), step-reduction, sophisticated movement and logistical subroutines, Soviet doctrine, and NATO replacements. Also there are additional rules covering divisional integrity, disengagement from combat, artillery, field fortifications, attack helicopters, air power, airmobile operations, Soviet paratroops, ECM, chemical warfare, and nuclear weapons. Essentially, if you read or heard about a military capability for either side during the 1970’s, then you’ll probably find it in this game design.  The winner in FULDA GAP is determined on the basis of accrued victory points. Both sides gain victory points for destroying enemy units; in addition, the Warsaw Pact player also receives points for satisfying certain teritorial objectives (i.e., getting supplied WP units across the Rhine River or controlling the north-south autobahn).FULDA GAP offers three short scenarios: the Tripwire Scenario, in which Warsaw Pact forces attack into Germany without warning (7 game turns); the Advance Warning Scenario, in which NATO forces have enough warning of the impending Soviet attack to begin to concentrate and deploy for battle (7 turns); and the D+7 Scenario, in which both armies have mobilized and completed their initial preparations for the impending campaign (7 game turns). These scenarios can be played using either the standard or advanced game rules. In addition, players may also opt for either the standard or advanced version of the Campaign Scenario (14 turns). The advanced version of the rules introduces several new subroutines into the sequence of play. These new phases involve the use of air power, nuclear weapons, and special units, such as: Soviet paratroops, attack helicopters, airmobile units, and NATO airbases. A PERSONAL OBSERVATIONFULDA GAP, looking back, can probably best be described as an innovative, but ultimately disappointing Dunnigan 'near miss'; and like SPI’s FIREFIGHT, it never really succeeded in capturing the interest of most gamers. This is unfortunate because, despite its several imperfections, FULDA GAP is still an interesting treatment of a hypothetical confrontation between Warsaw Pact and NATO forces in Germany in the 1970s. A number of modern-era design concepts made their first appearance in this title. For this reason, it is not surprising that despite using a familiar game system for its basic mechanics, FULDA GAP is not a simple game. Moreover, it is not an updated version of SPI’s earlier foray into a hypothetical East-West battle for control of Western Europe: the 1973 title, NATO. In truth, other than the fact that both modern-era games use a variant of the KURSK Game System as their basic design architecture, the two titles have almost nothing else in common. And because Dunnigan’s nuanced design incorporates newer, more advanced weapons systems into its game mechanics, combat operations take on a quality distinctly different from SPI’s simulations dealing with World War II operational combat. Purely from a design standpoint, this was probably unavoidable. The hypothetical European battlefield of the 70s and 80s, because of Cold War technological advances, is a very lethal environment indeed; and FULDA GAP demonstrates very clearly, if only in game terms, that to be seen and targeted in the modern combat zone is to be destroyed. That being said, there are other modern-era simulations — SPI’s THE NEXT WAR and Victory Games’ GULF STRIKE come immediately to mind — that probably do a better job of representing the complex interactions of the different combat arms on the contemporary battlefield. Nonetheless, this title does offer those who are interested in recent (the last thirty years or so) military affairs, a fascinating, manageable, and challenging simulation of the first days of the war that might have been, but thankfully, wasn’t.Design Characteristics:
Game Components:
Subscribe to:
Posts (Atom)
Subscribe To
Posts
All Comments
Popular Posts
About Me
My Nephew Joe and Three Marine Buddies
|
