Category Archives: Wargames

Creating Victory Conditions in General Staff

The General Staff Wargaming System provides users with the tools to create scenarios of their own design. These scenarios can be historical battles or they can be ‘what if’ scenarios (e.g. what if Custer had brought Gatling guns to the Little Big Horn or what if Robert E. Lee fought Wellington). To determine the victor of these scenarios or battles we need to have a predetermined set of Victory Conditions. Below is a screen shot of the Edit Scenario Victory Conditions screen:

The Victory Point editing screen in the General Staff Scenario Editor. Click to enlarge.

And below is a screen shot of the self-checking error function for setting Victory Points:

General Staff automatically checks for impossible victory conditions. Click to enlarge.

The General Staff Wargaming System is designed to give maximum flexibility to the scenario designer. It fully supports creating scenarios from 18th and 19th century armies and any map.

How to Edit Unit Speeds in General Staff

We recently had a series of very spirited discussions about the speed of units in various formations and across different terrain types during the Napoleonic Era in the Facebook Wargaming groups. A number of people were very kind to forward documents, tables and charts that had estimates of unit speeds. But, one thing that quickly became apparent was there was quite a bit of disagreement about, “how fast could a unit march,” in the 19th century.

Furthermore, we hadn’t even begun to talk about battles that took place in bad weather (the battles of Stone’s River and Fort Donnelson during the American Civil War come to mind).

The solution, obviously, was to allow the user (the scenario designer) to have complete control over these values. Consequently, we’ve added a very easy to use utility to facilitate editing and displaying unit speeds in various formations across different terrains.

Below is a video we created that demonstrates these utilities:

Announcing the Scenario Editor!

The Scenario Editor Module for General Staff allows the user to combine any two armies created in the Army Design Module with any map created in the Map Design Module and create a scenario or battle. In the screen capture before we’ve combined the Allied Anglo-Portuguese Army from the Battle of Albuera (May 16, 1811) as the Blue Army with Napoleon’s Imperial Guard as the Red Army and placed them on a map of our own design.

Screen shot of the General Staff Scenario Editor. Note that the time to deliver orders via courier between units is displayed. Click to enlarge.

Also, note that when you slick on a headquarters unit the route, distance and time that a courier will take to deliver orders to the next subordinate unite are displayed. This is just the beginning because General Staff is actually two wargames in one.

We will be posting a video showing off some of the new features shortly.

 

 

Gameplay Survey 1: Unit Complexity.

When I first started thinking about designing General Staff I envisioned a simple game that was almost chess-like in parts and that was designed to introduce novices to wargames. I thought that the Xbox would be the ideal platform.

After talking to two major digital wargame publishers I was told:

There is absolutely no wargame market for the Xbox and it was idiotic to even think that there was.

Traditional wargame buyers want more complex games; not introductory games.

Wargame buyers (can we just say Grognards?) still fondly remember UMS, UMS 2 and The War College (UMS 3) and would certainly support a major update.

Consequently, I have had to readjust my thinking about the gameplay and design of General Staff. Maybe the wargame you want to buy is different from the wargame that I was planning on making. To better understand what exactly customers want from General Staff I’m going to be posting a series of surveys about very specific gameplay and design issues. I’m going to lay out the pros and cons of the various options and then I’m going to ask you to please vote and give me feedback.


Simple unit details:

My original design called for a very simple unit structure. Other than a number of bookkeeping variables (such as location, facing, speed, orders, etc.) the only values that we would store were the unit’s type and strength.

The screen captures below show examples of this design.

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

The rules on unit type and strength are:

  1. In any given square there can be a maximum of 4 artillery units, 3 cavalry units or 2 infantry units.
  2. Different unit types cannot occupy the same square.

Advantages of a Simple Unit Structure:

There is a very appealing simplicity to this system. The user can immediately see the strength of forces at any location. As a unit takes losses the number of symbols displayed in the square are decremented until the unit, itself, is removed.

Less data is required to create a scenario.  But, the real problem is trying to assign values to variables like ‘morale’, ‘experience’ or ‘leadership’. Inevitably, these are just value judgments.

It presents a simple and less intimidating interface (no names, ‘strength bars’, etc.) for beginners.

Visually it fits right into the Napoleonic and Victorian topographical battlefield map engravings style that I want to emulate. I, personally, am greatly enamored by this style and would love to maneuver units on these incredible contoured maps:

Bataille de Molino del Rey : 1ere Position [y] 2éme Position (1820) .From: Biblioteca Virtual del Patrimonio Bibliográfico. A superb example of 19th century battlefield map engraving. Click to open link in new window.


Complex unit details:

How much information can we store about every unit on the map? The only limit is the size of available storage; in other words, on modern computing devices, there are no real limits. Below is screen shot (with explanations) of the variables used to calculate combat results in UMS II: Nations at War.

Unit variables used for combat resolution in UMS2. Click to enlarge.

Among the most likely variables to be included in the unit structure are: unit name, leadership value, morale level, strength, fatigue and unit type.

Advantages of a Complex Unit Structure:

Theoretically, the more data you have the more accurate the simulation. Obviously, this depends on the accuracy of the data but as long as the variables are relevant to the simulation and your model is good, the more variables the better.

Simply having a more detailed model with a lot of unit variables may help to sell more units to Grognards.

Disadvantages of a Complex Unit Structure:

More data has to be researched, compiled and entered into the Create Army Module (see here).

This data needs to be displayed in a way that doesn’t overload the user. Below is a screen shot of some tests that I did for an earlier version of General Staff:

Screen capture showing one method of displaying information about a unit. In this case the stored values include Melee attack value, maximum range, ranged attack value, strength, unit quality, formation, morale and fatigue. Click to enlarge.

Screen capture showing one method of displaying information about a unit. In this case the stored values include Melee attack value, maximum range, ranged attack value, strength, unit quality, formation, morale and fatigue. Click to enlarge.

Inevitably, at some point the scenario designer has to make some very arbitrary decisions about a unit’s morale and leadership values.

What is the maximum strength of a unit? Remember we’re talking apples (artillery) and oranges (infantry divisions) here. What does the value ‘strength’ actually mean? Is it the number of men in the unit? Clearly 50 men in an artillery battery have more ‘strength’ than 50 men in a line infantry company. Is there some other modifier (perhaps ‘unit type’) that is necessary to convert a unit’s strength to its combat power? And, what if a scenario designer creates a unit with a strength of 1,000 while other units have values of, say, 10? Will this be an unstoppable behemoth on the battlefield?


So, now it’s time for you to make your feelings known about these issues. Simple or complex unit data structures? What information should be stored about each unit?


You input is very important to us. Please feel free to give us more feedback either via the online form or by emailing me personally at Ezra [at] RiverviewAI.com

General Staff Features

General Staff is a direct descendant of the UMS seies which featured a suite of tools that allowed the user to create new maps, armies and scenarios. Our recent survey indicated that 73% of respondents felt that it was either ‘very important’ or ‘somewhat important’ for General Staff to have these abilities, too. Below is a flow chart of the five modules that make up General Staff:

Flow chart of General Staff. From the main screen the user can either create a new map, create a new army, combine a map and two armies into a new scenario or play a previously created scenario. Click to enlarge.

Flow chart of General Staff. From the main screen the user can either create a new map, create a new army, combine a map and two armies into a new scenario or play a previously created scenario. Click to enlarge.

From the Main Menu the user can select:

The Create Map Module

This module provides all the tools that a user needs to create detailed, authentic-looking maps. The are numerous tiles that represent the eight different terrains (field, water, swamp, city, woods, bridge, road, fort). Additionally, the user can sculpt hills and ridges with the AI automatically adding ‘splash contours’. Rivers and roads are added using a Bézier curve tool.

After the map is completed the user can select the amount of ‘dirtying’ (map folds, coffee stains, age stains, etc.) to be added to the map.

The Create Army Module

Armies can be in either an hierarchical format (see below) or a flat format. A flat format is a data structure without layers of commanders. Next week we will be running a user survey to find if you have a preference for hierarchical or flat army unit structures.

Screen shot from UMS II: Nations at War showing a hierarchical army structure. There are four levels of command in this army structure: Army Group, Army, Corps and Division. Click to enlarge.

The original UMS had a flat army structure while UMS II had a hierarchical unit structure.  For both systems an intuitive click and drag interface is provided for quickly creating, editing and saving armies.

Available unit types include: heavy and light infantry, heavy and light cavalry and heavy and light (horse) artillery. Headquarters and courier units are provided for hierarchical army structures.

Create Scenario Module

In the Create Scenario Module a user can combine any two previously created armies with a previously created map to create a new scenario. Mix and match to your heart’s content! The Napoleonic Imperial Guard against the Army of the Potomac’s First Army Corps on the Gettysburg battlefield! The battle of Marengo re-fought with Russian and Austrian troops! Obviously, you can also create historically accurate scenarios, too.