Flashpoint Campaigns: Cold War News

[h3]Flashpoint Campaigns: Cold War | AAR | The Albstadt Draw[/h3][p][/p][h3]FLASHPOINT CAMPAIGNS: COLD WAR RELEASES THIS THURSDAY (20TH NOVEMBER) [/h3][p][/p][p]Rendezvous with Destiny

The 1st Battalion of the 502nd was advised of their first task as soon as the 101st unloaded; Soviet rocket batteries were deploying outside Hanau, too close to the Frankfurt HQ to be acceptable; it couldn't be allowed for them to be tempted to use tactical nukes on such a juicy target. The West Germans were desperately holding Hanau with 11 ACR sending a relief column ASAP. Looking at the remainder of the force dispositions... what the hell?[/p][p][/p][p]Grumbling, Lieutenant Colonel Garrison read on and looked at the four offered landing zones, immediately discarding them all-[/p][p]The opposition looked to be 4 battalions pinching Hanau and a regiment on the way.[/p][p][/p][p]He wanted to use the Hemsbach Ridge as a redoubt and shield to protect his Chinook's on the way in. He could attack the high priority rocket batteries and interdict the arriving MRR if he could own that high-ground and occupy Michelbach. He drew his own route and LZ on the provided map and started giving orders. The men were told to eat and grab 4 hours of rest however they could, loading would begin at 2200; the 101st specialized in night actions and there was no way they could wait 24 hours.[/p][p][/p][p]At least he was allowed to know a Spectre would be on-hand.[/p][p][/p][p]About five hours later as the men were boarding he laid out his insertion plan to his Captains. They would be approaching and landing behind the cover of the ridge over Hemsbach. The Observer and Attack helos would be placed to cover their approach and try to get an eye on the rocket batteries and their AD-[/p][p][/p][p][/p][p]The thrumming squadron took off, their escorts swiftly invisible in the distant night. Unfortunately the near-side scouts discovered the hard way that the enemy AD had that vector well covered, both observer helos splashing in the river. There was no other firing until they crossed the river, when some Apaches discovered Soviet scouts. They were taken care of with dispatch-[/p][p][/p][p][/p][p]All of the Chinooks reached their LZs with no issue and swiftly unloaded. Orders were given and the 502nd started moving out carefully through the wooded hills over Hemsbach. There was a brief message of enemy movement to the north but no indication of its importance-[/p][p][/p][p]One of the rocket batteries was discovered right on their doorstep and was swiftly chopped to pieces by more Apaches.[/p][p][/p][p]The sightings to the north turned out to be very important as a tank battalion approached Albstadt. Fortunately there was no sign yet that their positions had been realized. The Chinooks were sent further east to create the illusion that the NATO activity was further off while the troops moved out through the darkness, easily picking their way up the slopes. Their presence was formally revealed when a robust bombardment was opened with every mortar and gun they'd brought with them.[/p][p][/p][p]Over the next 35 minutes the barrage continued, but the companies heading for Michelbach were moving terribly slowly in their caution, causing Garrison to worry he'd made a mistake. Just then word came down that an airstrike was coming in on the enemy Tunguska battery, a great relief as it would allow the Apaches a chance to get a clear shot at the enemy tanks-[/p][p][/p][p]Unfortunately...[/p][p][/p][p]The AD was right next to an HQ unit that was apparently emitting louder than the target, so they were struck instead. They only heard the jets as they skimmed beneath the overcast sky, type unknown.[/p][p][/p][p]This, to put it bluntly, stunk. The Apaches couldn't take risks, and their AT Hummers were taking an even longer time to navigate into position than the troops. They could only use artillery, and watch as the tank battalion cruised through Michelbach and took up positions closer to the river.[/p][p][/p][p]Two hours into the mission the guys were finally approaching Michelbach when the AC-130 arrived. Taking a great risk, they were directed at the pesky AD battery-[/p][p][/p][p]Apparently they were reloading as the big buzzing beehive of oblivion flew up the valley, circled twice and then departed-[/p][p][/p][p]The Apaches finally had free reign. Ten minutes later Michelbach was occupied without opposition, and companies A B & D began to dig in, choosing stout buildings with a commanding field of fire.[/p][p][/p][p]The last of the troops were finally taking up their positions about half-an-hour later when the helo scouts reported significant movement; the MRR was in column advancing down the road, armor in front-[/p][p][/p][p]After assessing the ammo states of all their artillery a Maximum Effort barrage was called for, including the newly arrived 155s across the river. However word had reached General Carter that the West Germans were being hard pressed so “Spooky” was rotated up to them. The 502nd's massed batteries, which had previously offered a few volleys at the initially sighted tank battalion, now opened up with everything they had-[/p][p][/p][p]No one appeared to have paid due attention to Saint Barbara however as the enemy column mysteriously lagged in their advance, causing the cascade of fearsome ordnance to be wasted on a set of recon vehicles. With only a cratered landscape to show for it, now yet another battalion stormed over the rise. It could only come down to the man on the ground-[/p][p][/p][p]30 minutes of desperate firing began, the defenders using their night vision equipment to best advantage as the leading tank battalion disappeared into the fresh moonscape of the small draw that lead up to Albstadt. Some of the AT units had managed to reach a spot to fire from even if they weren't yet in position, and they began scoring hits at even 5km as their crews sighted in with thermals. 15 minutes later however the surviving T-80s crawled out of the cratered landscape of smoke and fumes and advanced into Michelbach-[/p][p][/p][p][/p][p]For ten fearsome minutes the 90 men holding the town took their carefully aimed potshots as the tanks moved into town, from this garage door or that kitchen window, finding that their LAWs were quite capable of disabling the Soviet armor if used with care. The first wave petered out, with surprisingly few casualties-[/p][p][/p][p]Everyone reloaded and the Battalion FS called for another Maximum Effort barrage as Soviet illumination rounds drifted down, but fortunately just west of their positions-[/p][p][/p][p][/p][p]Through the hail of fire the MRR drove into the draw, their leading tanks being the first to clear the demolition yard-[/p][p][/p][p]Minutes started seeming like hours as the armor ground themselves to dust on Michelbach's defenders, shortly followed by the BMPs of the infantry. It was definitely desperate, every battery ruing the minutes they could not fire while they restored their stocks, the companies in front wishing they had time to resupply while all they could do is fire light arms out of windows and doors. The Soviets not only seemed to want to overrun the defenders but also made moves to bypass the town, simply because of the mass of their traffic in the choked streets and fords-[/p][p][/p][p][/p][p]Fifteen more minutes the fighting raged, TOWs streaking overhead from the ridge behind, artillery falling endlessly in the narrow draw, and the men of the Screaming Eagles shooting every target they could pick out, now hardly needing their edge as the Soviets entered the town. They wisely began to cycle resupply so as to maintain as much LAW fire as possible, but the Soviets were starting to leak by. Just then Garrison was informed Task Force Comanche had arrived, but the bad news was that the Germans needed them more than he did according to HQ. Cursing, all he could do was look at the map and listen for radio calls-[/p][p][/p][p][/p][p]5 minutes later, unbelievably, Michelbach proper took their first big casualties. This spot of news was surprising as Garrison had assumed casualties had been badly accumulating. The Soviets in the draw however seemed horribly slowed by the initial errant barrage, and the persistent bombardment was certainly not helping their cause. Their BMPs were starting to back-up in the wasteland just outside of town, a critical opportunity to fire everything at them-[/p][p][/p][p]Then; ...dawn broke. And, suddenly, it seemed doable. In that wasteland of burning vehicles, it seemed more wasn't moving than was. More barrages were drawn up, but it was finally felt that a few speculative volleys at presumed but unknown defensive positions could be afforded. Despite this moment of hope with first light the Soviet artillery began to find their TOW positions on the ridge. Garrison felt they'd take more casualties by breaking out to move than holding, so hold they did-[/p][p][/p][p]Thirty minutes later a moment came where the soldiers in Michelbach realized the gunfire was distant, that their breathing was the loudest sound they could hear. Sergeants started moving around, checking in with the men, calling for medics or giving a hearty clap on the shoulder as need demanded. Colonel Garrison looked at his sighting reports and was shocked to see that their artillery would have to really look for worthy targets. The Hummer ATs by report seemed to be in the worst shape, they weren't meant to sit through artillery, but at least every unit answered. He grimaced at himself as he realized C Company's blocking position to his southwest probably hadn't been necessary at all as none of them had fired a shot at anything.[/p][p][/p][p]Their bombardments continued for another 90 minutes, and then word came from higher up that the enemy seemed to be withdrawing. It was an amazing spectacle when he finally climbed the ridge to lay eyes on the field for himself. The little vale of Albstadt, all 3sq km of it, was a sea of smoke. Little fires poked and sputtered, but the haze of defeat just clung to the ground like a gloomy shawl. Task Force Comanche had succeeded in reinforcing the Germans, who had apparently taken a lot of casualties and were pushed to the bitter edge before they arrived, but thanks to the US Army the day seemed to be won.[/p][p][/p][p][/p][p]Command asked for a debrief, so Garrison told his forward positions tally claims of enemy losses. Of the 4 platoons holding Michelbach;[/p][p][/p][p]3rd Platoon, A Company 2 Tank, 3 APC, 12 Inf, 1 AT, 4 AD, 1 Arty[/p][p]1st Platoon, A Company 2 Tank, 3 APC, 16 Inf, 1 AT, 2 AD[/p][p]2nd Platoon, A Company 6 Tank, 1 APC, 2 Inf[/p][p]1st Platoon, B Company 6 Tank, 5 APC, 9 Inf, 1 AT, 2 AD[/p][p][/p][p]The TOW Humvees supporting the defenders;[/p][p][/p][p]3rd Platoon, D Company 1 Recce, 11 Tank, 12 APC, 1 HQ, 9 SPArty, 10 Utility[/p][p]2nd Platoon, D Company 1 Recce, 7 Tank, 33 APC, 2 SP AT, 1 HQ, 7 Utility[/p][p]1st Platoon, D Company 6 Recce, 3 Tank, 24 APC, 5 SP AT, 1 HQ, 6 Utility[/p][p][/p][p]The airmobile Division Artillery added;[/p][p][/p][p]Battery A 11 APC, 7 Inf, 2 SP AT, 7 AT, 7 HQ, 4 AD, 1 Utility[/p][p]Battery B 16 APC, 7 Inf, 5 AT, 2 HQ, 5 AD, 2 Arty, 3 Utility[/p][p][/p][p]289 Claims from 9 units. There would be a lot of stars handed out.[/p][p][/p][p]It turned out the Germans actually carried their fair share of the fighting, though this was not visible to the 101st. Between the two forces, including 56 Claims from the Apaches, 736 enemy sub-units had been accounted for, set against total sub-unit losses of 144. For NATO definitely not a gross result. And a brilliant day for the 101st![/p]

[p][/p][p]Flashpoint Campaigns: Cold War releases November 20 and will cost $49.99 on launch.[/p][p]As a thank you to our longtime supporters, existing Flashpoint Campaigns: Southern Storm owners will receive a 50% discount when purchasing Flashpoint Campaigns: Cold War. [/p][p]To receive the discount, please select the Flashpoint Campaigns: Cold War Upgrade bundle when making a purchase on Steam or directly through the Matrix Games website.[/p][p]We'd like to thank all our players for their continued support.[/p]

[p]Hello Commanders![/p][p]Actually, hang on just a minute, I need to hop in this helo to ride out to the front. Or wait, was it the truck to the far flank? Hold up, let me check my plan.[/p][p]In all seriousness though, transport plans are an incredibly complex thing. One of the biggest challenges is creating a system that gives players the versatility to do weird, wacky things but which also has the simplicity to be understood. Let’s start with a reference look at what the Pros use when they are planning this stuff.[/p][p][/p][p]Figure 1: What the Pros use to plan these things[/p][p]Well… that’s a lot. How can we make that easier for players to fill out quickly? Fortunately, some of that is pretty easy. Players don’t have control over individual squads, so the game will handle which squad or vehicle gets carried by whichever vehicle is most appropriate. And while timings are important, in general in our game everything is done ASAP. So the units need to know the timings, but the player just needs to know that the units will do things without delay.[/p][p]Another thing we can do is to break this up a bit. The table above is for what is called a Lift, which is the plan for all the units involved and will take the different units to multiple locations from multiple locations. We’ve broken this down into the players only needing to plan a single Serial at a time. A Serial has a single, specific pickup location and a single, specific drop-off location. With those changes in mind let us see what we have left.[/p][p][/p][p]Figure 2: Sample Plan[/p][p]This is a pretty simple plan as all things go, but it serves as a good example for looking at the various elements at your fingertips. The top section is pretty similar to the Air Movement Table above, showing us which transport unit is carrying which passengers. Below that we can see the path the transport will take, where it’s going to pick up the passengers and where it will drop them off. I have utilized the ability to set six waypoints to have the transport helicopter do some exfil as well. In the next section we can see which units have been attached as escort duty to this plan. Issuing this plan will give the respective orders to all of our units involved.[/p][p]Escorts and Transports will move in formation with each other, great for keeping your transports under the protection of any escorts and avoiding having your troops arrive one at a time where they can be easily be picked off. If you already saw our pre-release stream then you know these plans can involve many more units of course, but in case you didn’t and want to check it out: [/p][p][dynamiclink][/dynamiclink][/p][p]Now, I think it’s great being able to do this sort of thing. But I promised you versatility, didn’t I? So let’s see what that can look like.[/p][p][/p][p]Figure 3: Now it gets weird[/p][p]Since it’s probably not immediately obvious, let me explain the madness I have concocted here. We have a transport unit consisting of a couple of Chinook helicopters. Inside each of those Chinooks is a platoon of America’s brave men and some friends. But the transport mission those Chinooks are going to undertake is to go pick up a couple of Kiowa helicopters. How are they going to do that? Well the Kiowas will get sling-loaded underneath the Chinooks. Now that’s a bit strange, but why stop there? If you’re not familiar with the Kiowa, on the outside of it are a couple of benches that Joe Smith and a few buddies can ride on. So while the Kiowa is getting strapped in we’ve got a couple of mortar teams lashing themselves to the side of these Kiowas. Why are they riding the Kiowas instead of the Chinooks? I don’t know, I guess they just want to feel the wind in their hair. Or maybe it’s ‘cuz I told them to for this arbitrary example.[/p][p]Alright, you probably don’t want to do that, but what might you actually use this for? You could use this for transporting some wheeled units with some infantry that can use the wheeled transport to sneak close to an objective or observation point. With any luck we can expand this to cover other transport types like amphibious landings in future updates and content.[/p][p]There are a lot of nuances that Tactical Transport lets us utilize and explore in the game. An entire new range of possible scenarios we can develop and add to the game as we continue to support it and expand the series in the future. For any wily users who want to make their own scenarios or even edit the unit data the potential here is immense. If you’re as excited as I am about this, post your favorite picture of an unlikely military transport in action. Here’s mine:[/p][p]Figure 4: Ok, so the chopper isn't being carried, but it's still funny.[/p]

[p]Andrew Spearin, Producer, On Target Simulations[/p][p][/p][p]Introduction

The purpose of this AAR is to showcase how playing Flashpoint Campaigns: Cold War is less about gaming the systems, and more of an exercise in thinking and acting as a commander of ground forces. We'll take an analytical approach to how we planned our operations and see how the scenario unfolded; highlighting the strong points and invite any discussion on points to improve.

We are using the Every Cat is Black at Night play through from the October 16th, 2025 gameplay livestream on the SlitherineTV Twitch channel. You can watch the full battle in real-time action here. Read on below as we break down in further detail.

This will be a multi-part AAR posted below, with this initial post providing a situational picture of the scenario. Next, we'll look at the general plan for our primary course of action. We'll chronologically follow the main events as they unfolded. Finally, we'll assess the end results.
[/p][hr][/hr][p]
1. Situation:[/p][p][/p][p]Figure 1: Area of Operation, Most Likely ECOA

Every Cat is Black at Night D+1 | 21 July 1989, 2300hrs - 0500hrs | West Germany vs Czechoslovakia @ Landau ad Isar Scenario by Jo Lima; Mike Johnstone | Map by William van der Sterren[/p][hr][/hr][p]Player 1:
NATO: 4th PanzerGrenadier Division \[4.PzGrenDiv]
Commander: Generalmajor Berthold \[Andrew Spearin]
Second-in-Command: Oberst Borsack \[Gary Chezem]

Player 2:
Warsaw Pact: 9th Tank Division \[9. Tank Divize]
Commander: generálmajor Weiss \[CPU][/p][hr][/hr][p]
As the battle in Straubing developed, the Czechoslovakian 9th Tank Division began to drift south towards Landau ad Isar. With the Czechoslovakian 2nd Motor Rifle Division locked in combat with the West German forces in Straubing, the surrounding countryside south of the city held promise for quick exploitation. Unfortunately, the day was lost in the engagements in Straubing, and it was nighttime before the 9th was in a position to exploit the temporary local advantage the Czechoslovakian forces had.

In the 9th Tank Division HQ, there was severe indecision about making a nocturnal advance in the barely reconnoitered ground. Unlike their fellow countrymen north of Straubin, the Czechoslovakian forces in this area had been plagued by indecision and stop-and-go movement. The 2nd Motor Rifle Division was in a difficult position since, even though it had succeeded in opening a gap in the 9th Tank Division, it had entangled itself with the West German forces in Straubing. This earned the Divisional Commander a stern rebuke from the Army HQ, which was still demanding continued pressure and relentless advance.

The West German 4th PzG Division had reasons to feel marginally more optimistic. Not only had they stopped two Czechoslovakian divisions, but they could now use the night to maneuver reinforcements and consolidate their defense. At a higher level, NATO had concerns over the fact that the Czechoslovakians had secured a bridgehead over the Donau and that there were no forces to make an immediate counter. They were going to have to rely on aerial and artillery attacks to eliminate and harass the bridgehead forces. There was also concern over the gap south of Straubing. It was uncertain whether the Czechoslovakians would exploit it before the 4th PzG Division could plug it. The Divisional Commander of the 4th PzG Division wanted to consolidate his defense and counter-attack at first light on 22 July. For that purpose, the commander was moving armored forces hastily toward the area. Unfortunately, the counter-attack against the bridgehead was not meant to be.

During the early evening of the 21st, the Czechoslovakian High Command, under Soviet pressure, took control of operations in this area. In a frantic affair, the forward groups of the 9th Tank Division were consolidated into a mighty armored fist with orders to make a night drive towards Landau ad Isar and beyond if possible. As they started the advance, they realized they had just moved towards a gap in NATO's defenses. Being the defender in their own land, the HQ 4th PzG Division was quickly made aware of this. The division immediately began rushing forward with whatever mobile forces they could assemble to throw against the flank of the advancing Czechoslovakians.[/p][hr][/hr][p]
Annex A: Order of Battle (ORBAT) 4.PzGrenDiv
[/p]

• [p]HQ 4. PzGrenDiv[/p]
  • [p]HQ JgBtl 47[/p]
    • [p]HQ 2/JgBtl 47[/p]
      • [p]1/2/JgBtl 47[/p]
      • [p]2/2/JgBtl 47[/p]
      • [p]3/2/JgBtl 47[/p]
    • [p]HQ 3/JgBtl 47[/p]
      • [p]1/3/JgBtl 47[/p]
      • [p]2/3/JgBtl 47[/p]
      • [p]3/3/JgBtl 47[/p]
    • [p]HQ 4/JgBtl 47[/p]
      • [p]1/4/JgBtl 47[/p]
      • [p]2/4/JgBtl 47[/p]
      • [p]3/4/JgBtl 47[/p]
    • [p]HQ 5/JgBtl 47[/p]
      • [p]1/5/JgBtl 47[/p]
      • [p]2/5/JgBtl 47[/p]
  • [p]HQ PzAufklBtl 4[/p]
    • [p]HQ 2/PzAufklBtl 4[/p]
      • [p]1/2/PzAufklBtl 4[/p]
      • [p]2/2/PzAufklBtl 4[/p]
      • [p]3/2/PzAufklBtl 4[/p]
      • [p]4/Radarzug 4[/p]
    • [p]HQ 3/PzAufklBtl 4[/p]
      • [p]1/3/PzAufklBtl 4[/p]
      • [p]2/3/PzAufklBtl 4[/p]
      • [p]3/3/PzAufklBtl 4[/p]
      • [p]6/Radarzug 4[/p]
    • [p]HQ 4/PzAufklBtl 4[/p]
      • [p]1/4/PzAufklBtl 4[/p]
      • [p]2/4/PzAufklBtl 4[/p]
      • [p]3/4/PzAufklBtl 4[/p]
      • [p]4/4/PzAufklBtl 4[/p]
      • [p]5/4/PzAufklBtl 4[/p]
      • [p]6/4/PzAufklBtl 4[/p]
      • [p]8/Radarzug 4[/p]
    • [p]HQ 5./PzAufklBtl 4[/p]
      • [p]1/5/PzAufklBtl 4[/p]
      • [p]3/5/PzAufklBtl 4[/p]
        • [p]2/5/PzAufklBtl 4[/p]
      • [p]10/Radarzug 4[/p]
  • [p]HQ 4/RakArtBtl 42[/p]
    • [p]1/4/RakArtBtl 42[/p]
    • [p]2/4/RakArtBtl 42[/p]
  • [p]HQ 5/RakArtBtl 42[/p]
    • [p]1/5/RakArtBtl 42[/p]
    • [p]2/5/RakArtBtl 42[/p]
  • [p]WG WLR[/p]

[hr][/hr][p]
Annex B: Intelligence Preparation of the Battlefield (IPB)[/p][p]Area of Operations
Landau an der Isar, Bayern, West-Germany | 48°40'00"N 12°42'00" | 20 x 15 km area

Named Areas of Interest (NAI):[/p]

1. [p]APPLE: A high value objective along the A92 mobility corridor; anticipated as a chokepoint for the main effort[/p]
2. [p]BERRY: Left flank area with minor objective[/p]
3. [p]CHERRY: Right flank area overlapping PIR EAST[/p]
4. [p]DRAGON: Blocking position at a critical junction along the mobility corridor that leads to Landau an der Isar[/p]
5. [p]ELDER: High value objective area[/p]
6. [p]FIG: Critical objective area at western edge of the AO[/p]

[p]Priority Intelligence Requirements (PIR):[/p]

1. [p]NORTH: required to monitor for a left flank maneuvre[/p]
2. [p]EAST: required to monitor a right flank maneuvre[/p]

[p]Terrain & Weather Analysis

Weather forecast is clear, with no moon 0% illumination.
Dawn is at 02:56

Enemy Forces

The 18th Tank Regiment of the 9th Czechoslovakian Tank Division is the expected opposing force.

Intel reports indicate that local enemy forces may contain 50 to 60 Recce, over 80 Tank, over 80 APC, over 80 Inf, 6 to 10 SP AT, 10 to 20 AT, over 80 HQ, 20 to 30 AD, 6 to 10 SPArty, 40 to 50 Arty, 30 to 40 Utility and 1 to 5 WLR subunits.

A typical force structure for a Czechoslovakian armoured reconnaissance element could look like this:[/p][p]A typical force structure for a Czechoslovakian tank battalion could look like this:[/p][p]NOTE: Intelligence reports T-72 tanks are equipped in the forward elements of this force.[/p][p]A typical force structure for a Czechoslovakian artillery battalion could look like this:[/p][p]NOTE: Intelligence reports 130mm M46 are equipped with this artillery battalion. They are likely equipped with illumination rounds to enhance their night fighting capability.[/p][p]Enemy Doctrine

Expect a high tempo as the enemy tank division is pushing towards a breakthrough.
Reconnaissance elements will be in the lead, likely taking main roadways until making contact.
Expect T-72 tanks as their primary force, followed by motor rifle companies and second echelon tanks.
Artillery with this division is limited, but still effective.

Enemy Courses of Action (ECOAs)

Most Likely ECOA:
Main effort moving fast along mobility corridor towards APPLE

Most Dangerous ECOA:
Forces split with flanking elements through BERRY and/or CHERRY
High mobility advance party moving faster than our force can arrive to DRAGON, ELDER and FIG

Intelligence Gaps
Our forces are moving into the AO from the north-west and currently do not have active information from any NAI or PIR. Rapid movement of armoured reconnaissance to monitor PIRs is imperative.

Assessment
According to enemy doctrine, the MLECOA and MDECOA are both anticipated.[/p][hr][/hr][p]
2. Mission

Block further penetration by enemy forces along the A92 corridor.[/p][p]3. NATO Planning

Knowing that the 2ic has experience combat on this battleground before, the Generalmajor consulted an opinion as an initial consideration.
[/p]

[p]Oberst Borsack wrote:In the past, I've tried to take advantage of the southern side of the river... it's a good flanking route. However, you have to really commit to it or else you end up having forces where they are not needed.

Maybe just a town and high country defense of the objectives.[/p]

[p]Time is of the essence for this meeting engagement, and a flank maneuvre south of the river would be time consuming and risky. The 2ic's advice will remain a consideration if resources allow.

ELDER will be a focus area for consolidating infantry to conduct a stalwart defensive position along the mobility corridor.

We also require infantry, supported by tanks, in BERRY which contains a tertiary objective. These forces will be used to slow the advance and potentially launch a counterattack into APPLE, if the opportunity presents itself.

Armoured forces will screen and attempt to slow down the enemy main effort in APPLE and BERRY.

2ic chimed in with some good advice, this time, regarding the deployment of tanks in BERRY:
[/p]

[p]Obsert Borsack wrote:It might be good to put one platoon on the north side of the river and the other two on the southern side because we're not going to stop them from taking the APPLE objective, so if we can hit them on the way by...[/p]

[p]With the first delay force ready, we noticed a treeline south of CHERRY that offers a concealed location to monitor PIR EAST and intercept a potential enemy flanking maneuvre.

The initial orders we issue to our units are going to set the entire battle's trajectory, so we must carefully plan and prepare to pivot our COA as the situation changes.[/p][hr][/hr][p]
4. Execution[/p][p]Turn 1 (Setup): 23:00[/p][p]
[/p][p]The initial advance party is small: a handful of tanks, infantry and armoured reconnaissance with ground radar. We need to be economical about sending them into our initial priority areas and establish pickets to monitor the mobility corridor.

Orders:

- 3/PzAufklBtl 4 equipped with Leopard 1A5 tanks, armed with 105mm L7 cannon and equipped with nightvision are tasked to BERRY, setting positions on both sides of the Ressinger Bach.

- 5/PzAufklBtl 4 are typically armoured reconnaissance scout teams, but are bolstered by MG3 machine gun teams and a Carl Gustav team. So they will need to perform as mobile infantry to begin with until they are reinforced. They are being sent to the town of GANACKER and setup defensive positions to cover the objective in DRAGON.

- 2/5/PzAufklBtl 4 draws the short straw and is detached to seize the treeline south of CHERRY to monitor PIR EAST.

- Our two TPz Fuchs + RATAC units with ground search radar and being deployed in depth positions and set up to detect the approaching enemy.

[/p][hr][/hr][p]
Turn 2: 23:23[/p][p][/p][p]As the intial orders are carried out by our advance party, our first reinforcements arrive. A troop of Leopards accompanied by another RATAC enter the AO from the north.

Orders:

- 4/Radarzug 4 will move 1.5 km east and monitor PIR NORTH, hopefully to give us our first detection of the approaching enemy.

- 2/PzAufklBtl 4 is tasked to move hasty south to GANACKER and pivot east to set up defensive line in the treeline covering CHERRY and PIR EAST.

[/p][hr][/hr][p]
Turn 3: 23:46[/p][p][/p][p][/p][p]The bulk of our Jaeger Battalion has now arrived in the AO, with an additional troop of Leopards and a few SpPz Luchs A3 recce units. We can use these units to bolster our advance party troops and establish a new defensive line in ELDER.

The objective in APPLE has fallen to the enemy. We have no contact reports from the area, but it's a reasonable assumption these are the advance reconnaissance units moving along the mobility corridor.

Radar detects our first enemy contact: 10 to 20 tanks moving south on St2325 into PIR NORTH.

Orders:

- 5 and 6/4/PzAufklBtl 4 are sent to cross the Isar at LANDAU and move hasty east and prepare to cross back north. 2ic gets his wish granted for this maneuvre.

- 4/PzAufklBtl 4 Leopards head south to reinforce the infantry at GANACKER.

- 2/JgBtl 47 mount up in their Unimog 1300 L utility vehicles and deploy defenses in HAIDLFING and support the 3/PzAufklBtl Leopard tanks in BERRY. 4/4/PzAufklBtl 4 will move with 3/4 to screen forward of the infantry and tanks, gaining sight on enemy forces in the vicinity of APPLE.

- 3/JgBtl 47 will move to establish a depth position in ELDER.

- 4/JgBtl 47 were initially intended to bolster DRAGON. However, due to 2ic's worries, this unit is being sent to WAIBLING as a reserve force to rapidly deploy when needed.
[/p][hr][/hr][p]Next: Contact![/p][p][/p][p]You can read the rest of Andrew's AAR as it develops on our forums here[/p]

[p]Flashpoint Campaigns puts the player in the command post, planning and supervising the battle to defeat the opposing forces. As the commander, the player issues orders which are executed by the companies and platoons, represented by unit counters on the map. To make this a dynamic and engaging experience, the game’s AI (artificial intelligence) plays three important roles:[/p][p]1.      A skilled opponent, commanding the enemy forces. Even though scenarios may come with battle plans that define the initial maneuvers, the computer player still needs to supervise all units not involved in those battle plans, and finish the fight with all units once the battle plans have been completed.[/p][p]2.      Tactical and autonomous unit level behavior for platoons and companies on the map operate within the boundaries of the orders and standard operating procedures (SOPs). During the game’s orders resolution phase, where the player commander intervenes, these units execute their given orders and respond per SOP to events and unforeseen situations. The unit’s tactical behavior needs to be sound and competent, so that the battle’s success is determined by the commander’s planning and supervision.[/p][p]3.      Streamline the process of issuing complex orders in a single orders phase, to maneuver in formation, cross future bridges and minefield gaps, or perform follow-on actions after an airborne insertion.[/p][p]Figure 1   Mission briefing graphics and your command vehicle in shown in Flashpoint Campaigns: Cold War[/p][p]In this blog, we want to highlight the improvements for the AI as an opposing commander, for the unit’s tactical behavior, and for assisting the player in issuing complex orders.[/p][p][/p][p]The Computer Player has been upgraded to coordinate fire-support with planned ground maneuvers. When it has available fire-support assets such as artillery, attack helicopters, or close-air-support, it will coordinate fire support as follows: it will first identify the most important planned ground maneuvers, then predict the potential threats on the front and flanks of these ground maneuvers, and finally assign missions to the fire-support assets to destroy or suppress these threats.[/p][p]The Computer Player is capable of this coordination both when the Battle Plans are being executed and when Battle Plans have been completed; the only requirement is that unallocated fire support assets are available (and not tied up in Battle Plan missions of their own).[/p][p]Figure 2   Developer view of the Computer Player’s plans, in which it coordinates fire support assets to support a ground maneuver (diagonally, from the east to southwest) by sending gunships (north of the ground attack maneuver) and plotting artillery strikes (south of the ground attack maneuver)[/p][p]By coordinating fire support with ground maneuvers, the Computer Player becomes a more interesting opponent with stronger combined arms maneuvers.[/p][p][/p][p]Attack helicopters are a symbol of the Cold War era: these “gunships” could be quickly ordered across the battlefield to halt an armored attack or cover an open flank. Well-timed use of these attack helicopters can change the battle and our beta-testers have consistently demonstrated this. However, our beta-testers also reported that the helicopter unit behavior let them down when the gunships attempted to return to their FARP base to replenish ammo.[/p][p]The problem was that the helicopters would take a quick and short route back to the FARP, potentially traversing hostile held terrain and ground covered by known hostile air-defense systems.[/p][p]For Flashpoint Campaigns: Cold War, we introduced the following improvements:[/p]

• [p]helicopters now use the ‘stealth’ pathfinding preference when returning to the FARP, thereby preferring low terrain, valleys, protection from hill sides, and avoiding crossing ridges at the highest point[/p]
• [p]in addition, helicopter pathfinding also considers the map of spotted and recently lost-track-of hostile air-defense systems, aiming to avoid terrain covered by these systems.[/p]

[p]An example is shown below, for a West-German BO-105/PAH-1 anti-tank helicopter section which is trying to return to its FARP, carefully plotting a route which minimizes exposure to known Warsaw Pact air-defense systems:[/p][p][/p][p]Figure 3   The West-German BO-105/PAH-1 returning to base by “threading a needle” through the hostile air defense coverage (shown as red covered hexes)[/p][p]Note that this behavior does not make helicopters invincible: they might still be surprised by SAM missiles from unspotted or relocated air-defense systems.[/p][p]Another example of improved tactical unit behavior is the withdraw movement to a better position. On paper, the original design should work well: after being triggered by a nearby hostile unit, the unit would decide to withdraw, pick a safer location to withdraw to, and finally issue the movement orders to do so. On the game’s battlefields, the resulting behavior was unreliable:[/p]

• [p]the chosen withdraw location chosen was not always the most suitable location[/p]
• [p]the path to that location could expose the unit to increased danger[/p]
• [p]even a seemingly perfect withdrawal path and location could be rendered useless due to new enemy units appearing in the time between the decision and the actual start of the movement (when the unit is fully mounted up)[/p]

[p]To address these issues, we implemented the following changes:[/p][p]The first change was to improve the assessment of good withdraw destinations, now also allowing bridge crossings if necessary. After selecting the best candidate withdraw destinations, these would be filtered to unique locations (removing similar neighboring locations) and ranked for having the safest path to the location, resulting in a single best location to withdraw. If this “best location” offers benefits over the current location, the unit will withdraw.[/p][p]The second change was to revisit, and if necessary, update, the choice of the withdraw destination at the time the unit was all mounted up and ready to move. This allowed the unit to respond to newly spotted hostile units and to hostile units having closed in between the initial decision to withdraw and actual start of the movement.[/p][p]Figure 4   A US Army ‘hammerhead’ M901 ant-tank platoon automatically pulling back to hillside position further away from the threats, using a covered path due to the town and hillside between itself and the Warsaw Pact mechanized forces moving up.[/p][p][/p][p]As commander in Flashpoint Campaigns: Cold War, you issue orders for 15 to 60 minutes of game time. It is important to be able to issue orders for that duration, even when the orders involve coordination between several units’ actions. The game’s AI facilitates this.[/p][p]For example, the commander can order a bridge layer unit to place a bridge across a minor river, and, in the same orders phase, plot a tank company assault across that still-to-be-placed bridge. The AI’s pathfinding knows how to deal with future bridges and supports planning movements beyond the bridge accordingly.[/p][p]For Flashpoint Campaigns: Cold War, we expanded this with the capability to issue follow-on orders to airborne forces that will be inserted, as soon as the orders to corresponding air transport units define the future landing zone. This enables the player to plan and command complex airborne assaults with airborne forces seizing objectives all in a single order phase. This is illustrated below for an airborne engineer unit with orders to blow a bridge immediately after being inserted.[/p][p][/p][p]Figure 5   A small airborne insertion planned for the initial turn, with the transport (white path) inserting the airborne engineer section in a landing zone before exfiltrating. The airborne engineer unit (orange path) being inserted will move to the bridge, demolish it, and subsequent take position in the village.[/p][p][/p][p]In Flashpoint Campaigns: Cold War, we also assist the player with issuing formation movement orders for groups. These formation movement orders reduce the effort to issue orders, and they help those units involved move with greater cohesion, being able to better support another when being engaged. The new formation movement commands allow for column formations to move across roads and complex terrain, and for two-up and three-up formations to maneuver through open terrain.[/p][p]Figure 6   The player’s options for formation movement orders illustrated, with the developer graphics displaying the.[/p][p][/p][p]With these examples, we hope to have given you a glimpse of the improvements that are part of Flashpoint Campaigns: Cold War and perhaps a better understanding of the challenges facing “the computer player.”[/p]