Slitherine

quote:

ORIGINAL: Okayrun3254
I have always been interested the Anzio battle. I think it is about the right number of units, and both side have a chance to be on the offensive. I also think it would be a good opportunity to put in some what if's. Like what if the Allies committed another division sooner than later? I always felt the allies did not give the landing enough troops, and if they did, the outcome might have been different.

quote:

ORIGINAL: bcgames
I think the progression of the engine looks like this:

WEGO1: Desert War 1940-42

WEGO2: Stalingrad: Nightmare on the Volga. Introduces bridging and pontoons, ski troops, partisans, security units, supply depots, airfields, and air transport of supplies.

WEGO3: Monty's Front: 21st Army Group. Will introduce airborne and riverine operations.

WEGO4: Title TBD...introduces expanded naval rules (amphibious operations, naval interdiction, counter-naval operations, naval supplies, etc.) Best topics for exploring WEGO4 are Narvik, Seelowe, Sicily/Salerno/Anzio or Normandy/Avalanche.

WEGO5: Title TBD...World War II in Europe and the Mediterranean. I think WEGO5 is the "Operational Art of War" version of the WEGO engine. It is an amalgamation of all the terrain types, unit types, and asset types found in our "previous games" plus those missing. It would add new nations/factional units and assets...AND provide a scenario editor that includes catalogs of units and assets of for all WWII Western Europe/Mediterranean Theaters from 1939-1945...from the Invasion of Poland to the Fall of Berlin. It would also include a list of new scenarios and campaigns that explore the various aspects of these theaters. Maybe a sandbox mod at this point. WEGO5 is a game and a robust toolkit for would-be scenario designers.

Bottomline: I think expanding the capabilities of the WEGO engine takes precedence over topic. The topic chosen best supports the next set of capabilities. In the end there is a well-stocked toolkit of art resources and editors so that fans can explore their interests on the Western Fronts and easily share their scenarios with others.

quote:

ORIGINAL: bcgames

quote:

ORIGINAL: bcgames
I think the progression of the engine looks like this:

WEGO1: Desert War 1940-42

WEGO2: Stalingrad: Nightmare on the Volga. Introduces bridging and pontoons, ski troops, partisans, security units, supply depots, airfields, and air transport of supplies.

WEGO3: Monty's Front: 21st Army Group. Will introduce airborne and riverine operations.

WEGO4: Title TBD...introduces expanded naval rules (amphibious operations, naval interdiction, counter-naval operations, naval supplies, etc.) Best topics for exploring WEGO4 are Narvik, Seelowe, Sicily/Salerno/Anzio or Normandy/Avalanche.

WEGO5: Title TBD...World War II in Europe and the Mediterranean. I think WEGO5 is the "Operational Art of War" version of the WEGO engine. It is an amalgamation of all the terrain types, unit types, and asset types found in our "previous games" plus those missing. It would add new nations/factional units and assets...AND provide a scenario editor that includes catalogs of units and assets of for all WWII Western Europe/Mediterranean Theaters from 1939-1945...from the Invasion of Poland to the Fall of Berlin. It would also include a list of new scenarios and campaigns that explore the various aspects of these theaters. Maybe a sandbox mod at this point. WEGO5 is a game and a robust toolkit for would-be scenario designers.

Bottomline: I think expanding the capabilities of the WEGO engine takes precedence over topic. The topic chosen best supports the next set of capabilities. In the end there is a well-stocked toolkit of art resources and editors so that fans can explore their interests on the Western Fronts and easily share their scenarios with others.

I have invested in research/resources to support this progression...but what do you say? What should WEGO4 and WEGO5 introduce to the system? What should the topic of each be about?

Sell it to our readers.

quote:

ORIGINAL: canuckgamer
...say Guadalcanal?

Anyway just a thought.

quote:

ORIGINAL: Saint Ruth

What does "disrupted" actually mean? Lower quality units take more casualties and have slower recovery, so a disrupted unit is one that can't recieve orders? Or something else as well?

quote:

ORIGINAL: bcgames

I think we have this already...but by a combination of different names--Readiness and Command Control. The lower the readiness level of a unit, the less command control the player has over the unit.

quote:

ORIGINAL: Okayrun3254
...I would assume a unit with low Readiness would be more prone to being overrun.

quote:

ORIGINAL: Okayrun3254
Okay, that makes sense. Sometimes when playing the game I forget about the effect of Readiness on the units being attacked. I would assume a unit with low Readiness would be more prone to being overrun.

quote:

ORIGINAL: bcgames

quote:

ORIGINAL: canuckgamer
...say Guadalcanal?

Anyway just a thought.

Sounds like an interesting topic for a Desert War scenario. I have most of the assets to do it from a Desert War engine experiment I did several years ago:



Current focus is on Stalingrad but I hate getting stuck in a historical rut without relief. We'll see what happens.

quote:

ORIGINAL: bcgames
... The Campaign for Dien Bien Phu and Tet Thua Thien (I Corps circa 1968) are game topics I have studied for years and would love to game (got all the books to get the jobs done).

quote:

ORIGINAL: bcgames

I'm not long for this world so after Monty's Front I'm going to do Second Front: Normandy to Paris,
Bradley's Front: 12th Army Group, and Barbarossa: Army Group Center. I think this path is the best to bring the game engine to maturity. We'll see what happens after that.