Orange Devil posted:

If you can know for sure those AoA3 nerds will show up at exactly minute 100 it is indeed too gamey. Sometimes there’s delays or people stepping on the gas too hard.

Still not at all convinced that if they do have to show up there they should head north rather than west.

Zeppelin Insanity posted:

My understanding is that the arrow just shows they're coming from south, and in my plan would be diverting west as soon as possible. I'll draw something after I digest FF's awesome advice.

And yeah you're right, it probably won't be minute 100. But it's pretty likely it won't be, like, minute 70.

my dad posted:

It's my family's Slava, and I'm watching over my nephews and niece. My younger nephew was having fun playing an RTS very badly, and I had to (gently) physically restrain my older nephew as he was shouting "NOOO HE'S PLAYING IT WRONG NOOOO LET ME DO IT INSTEAD NOOOOO"

my dad posted:

It's my family's Slava, and I'm watching over my nephews and niece. My younger nephew was having fun playing an RTS very badly, and I had to (gently) physically restrain my older nephew as he was shouting "NOOO HE'S PLAYING IT WRONG NOOOO LET ME DO IT INSTEAD NOOOOO"

Orange Devil posted:

FF is just in his happy space if he can do artillery staff work for a competent (read: non-Western) artillery force.

Frosted Flake posted:

Think about timing as part of your overall mission. Yes, that includes avoiding a traffic jam, particularly as the east-west corridor is limited, but it also involves mutual support. Is there any reason why AoA3 couldn't arrive first, pin the enemy on the southern terrain feature, AoA2 begins moving down B505 and clears the northern terrain feature 30 minutes later, and AoA1 drives home down B22 70 minutes in?

If the time units arrive and where is set, that's fine, there are still ways to plan around that, but you want there to be one plan each unit contributes to, rather than 3 separate regimental battles that overstretch your division fires and can't support each other in place and time.



We can start talking about phasing and fire plans (because you'll want preplanned fires to support this manoeuvre scheme) when you have determined your initial disposition and timings, as well as overall intent. This is just an example.

Orange Devil posted:

I gotta say, imagine having been born in East Germany or Poland or something in say, the early 1960s, and realizing that actually things are going pretty well and these countrymen of yours with their lust for bananas and jeans are about to utterly wreck themselves but being unable to convince anyone of this and then having to live through another 50-60 years of the fallout. I don't know how you wouldn't end up on a street corner just screaming "I loving told you so" at people.

ANNEX B - FORMAT FOR AN ESTIMATE (This is a guide not a rigid format) posted:

Issuing HQ
Location
Date and Time of Issue

ESTIMATE FOR (TITLE) References:

A. Appropriate maps, charts and reports
B. Supporting estimates
C. Directives and commander's planning guidance

1. Situation. A short summary of the situation

2. Mission. State the mission that was determined in the orientation step 2. It may be necessary to include a subparagraph to detail any limitations to the mission. Include centres of gravity if known or determined.

3. Assumptions. Include only those assumptions required to complete the estimate. Assumptions
made by the commander are to be considered as facts for planning purposes.

4. Factors Affecting the Achievement of the Mission:

a. Describe the factors, which affect the mission. This can be in either narrative or tabular form. After each factor, list the deductions drawn from the facts. Conclusions should be concise and relevant; ideally, they should be expressed as a building block of information, for example:

(1) Offensive air operations cannot commence before day 12; and

(2) The maximum size force which can be sustained for the period is one mechanized division or one reinforced air mobile division; and

b. Group the deductions by function to assist the development of COAs. It may be necessary to revise deductions, as later aspects of the estimate affect earlier conclusions.

5. COAs:

a. Describe the COAs open to the opposing force. Ideally, this should be a series of feasible options of varying potential impact on our capacity within the theatre. It is always prudent to identify that COA which has the most serious impact on our capacity, regardless of the likelihood of it occurring. This provides an objective starting point for the array of COAs taken by the opposing force; and

b. Describe the COAs, which our forces have the operational and logistic capacity to execute. These COAs should only be limited by the guidance provided in the initiating directive/Wng O. The description should include:

(1) CONOPS;
(2) Probable Tasks / Missions;
(3) Task Organization;
(4) Critical Support Requirements (Engineering, Movement, Logistics, Sustainment, Financial); and
(5) Impact of this COA on other CF Ops, Training, procurement, or OGDs.

6. Comparison and analysis of COAs. Compare each of our own COAs against the opposing force's potential. This comparison should be as objective as possible using the deductions derived previously from the estimate. It is appropriate to set this comparison out in tabular form to focus on specific elements, particularly the comparison of time, space and mass. For example:

COA 1 - An amphibious assault preceded by naval and air bombardment. (More text as required.)



7. Summary of our COAs.

a. COA X. In separate paragraphs, describe the strengths and weakness of each COA;

b. Identify which opposing force COA is believed to be the most likely with respect to their capabilities and suspected intentions; and

c. Identify the criteria chosen for establishing the relative ranking of the COAs with respect to the most likely opposing COA. (for example, relative combat power, Force protection, ease of execution, sustainment, cost, political acceptability, impact on other commitments, etc). Conclude by identifying the COA, which best meets the mission and caters for the opposing force's capability. This may be done in tabular format and may require the staff to weight the criteria to establish a clear ranking.

8. Selecting Preferred COA. A statement of the preferred COA resulting from the above
assessment.

9. Outline Plan. An outline plan based on the preferred COA(s) is prepared, but only in sufficient detail to enable the staff to undertake the development of the decision brief and CONOPS.

Div Arty Estimate (example) posted:

Issuing HQ: [Name of Your HQ]
Location: [Location of the Operation]
Date and Time of Issue: [Date and Time]

ESTIMATE FOR DIVISIONAL ARTILLERY

References:
A. Appropriate maps, charts, and reports
B. Supporting estimates
C. Directives and commander's planning guidance

1. Situation:
The operation involves securing and holding river crossings against a formidable NATO defense. We have numerical superiority and better equipment, but we must consider the possibility of a strong enemy counterattack, especially from U.S. Abrams tanks.

2. Mission:
As the Divisional Artillery Commander, our mission is to provide effective artillery support to the division's efforts in securing and holding river crossings. This support includes suppression of enemy artillery, countering enemy armor threats, and enabling the division's advance.

3. Assumptions:
- We assume mild air superiority and that the enemy will deploy M113s rather than Bradleys.
- We have limited intel, and the enemy may employ unexpected tactics or surprises.
- The terrain poses challenges, especially along B22 and B505 roads.

4. Factors Affecting the Achievement of the Mission:
a. Terrain and enemy positions along B22 and B505 roads present challenges.
b. The possibility of enemy Abrams tanks requires a plan for countering armored threats.
c. Traffic management and unit timing are critical due to variable turn lengths.

5. COAs for Divisional Artillery:
- COA 1: Deploy all Akatsya batteries on the map initially, providing immediate fire support. Grads remain off-map.
- COA 2: Keep one section (3 batteries) of Akatsyas off-map to screen initial deployments. Grads remain off-map for concentrated firepower later.

6. Comparison and Analysis of COAs:
- COA 1 provides immediate artillery support but risks exposure.
- COA 2 offers a screening element but delays the full firepower of the Akatsyas.

7. Summary of Divisional Artillery COAs:
a. COA 1: Provides rapid artillery support but risks early exposure.
b. COA 2: Offers screening and delayed firepower, reducing initial risk.

8. Selecting Preferred Divisional Artillery COA:
- The preferred COA is COA 2, as it balances initial security with the ability to deliver sustained firepower.

9. Outline Plan for Divisional Artillery:
- Deploy one section of Akatsyas off-map initially.
- Grads remain off-map for concentrated later barrages.
- Coordinate with artillery observers and reconnaissance units for target acquisition.
- Prioritize counter-battery fire against enemy artillery threats.

10. Staff Recommendations:
- Maintain flexibility and adapt to changing conditions.
- Coordinate closely with reconnaissance and observation units.
- Maintain effective communication with divisional command.
- Be prepared for rapid deployment of Grads when the critical moment arises.

Commentary posted:

In accordance with Soviet attack doctrine, DHQ should consider the following principles:

- Conduct aggressive reconnaissance.
- Breach enemy defense at weak points or gaps.
- Maneuver against enemy flanks and rear.
- Bypass strongpoints when possible.
- Rapidly maneuver forces and fires in the decisive direction.
- Mass fires for maximum impact.
- Strike rapidly and deeply into the enemy's rear.
- Maintain momentum under all conditions.
- Employ EW to disrupt enemy communications.

my dad posted:

It's my family's Slava, and I'm watching over my nephews and niece. My younger nephew was having fun playing an RTS very badly, and I had to (gently) physically restrain my older nephew as he was shouting "NOOO HE'S PLAYING IT WRONG NOOOO LET ME DO IT INSTEAD NOOOOO"

Zeppelin Insanity posted:

CASE ONE
The numerical superiority intel reports indicates that NATO cannot defend everywhere equally.
The two highways are the obvious main route of attack, so we can reasonably expect them to have the strongest defence.
other elements to either bypass the enemy


ARTILLERY - on or off map
So, I either
-have all of my Akatsyas on the map - which will have to be protected, and probably arrive at some point in the marching order rather than immediately, thus preventing divisional fires for the first few turns. Regiments have their own Gvozdikas and mortars.


SPOTTERS
I also have two spotter elements and one recon element. My initial thoughts were that they should accompany the main advance, relatively near the front, but not at the head of the column so they don't get blown up immediately.

Frosted Flake posted:

Orange Devil posted:

Friendly Force Estimates posted:

Friendly forces: 79th Guards Tank Division composed of 3 Guards Tank Regiments and 1 Motor Rifle Regiment
Supported by
Division Mi-24s (9) and Mi-2s (8)
Army EW - Medium EW throughout whole operation, with a 3x 1 hour-long high level windows available.
Army ELINT during a 1:20 window, allowing 3 targets for intel collection
3 Flights of 2 Su-17 CAS
2 Flights of 2 Su-25 CAS
Fighters guarantee slight air superiority throughout whole operation, and can conduct 2x 1-hour long surges of higher air superiority.

Total vehicles:
T-80 BV - 167
T-80 B1 - 74
BMP-1P - 144
BMP-2 - 128
2S1 Gvozdika - 72 (those would be regimental, so not mine)
2S12 Sani 120mm Mortar - 36 (regimental, not minie)
2S3M Akatsiya - 54 (these are mine)
BM-21 Grad - 18 (these are mine)
BM-27 Uragan - 12 (Army, so must be requested)
BRDM-2 Konkurs/AT-5 Spandrel - 9
Strela 10M/SA-13 Gopher - 12
Strela 1M/SA-9 Gaskin - 4
Osa-AK/SA-8 Gecko - 12
Mechanized Infantry (ingame unit, I assume platoons?) - 54
Fagot \ AT-4 Spigot (as in infantry, not vehicle mounted) - 3
Igla \ SA-18 Grouse (MANPADS) - 51

That's from the overview. For some reason it doesn't seem to include everything, since there's also 3 PDFs with different information. I used the overview because I don't know if anyone feels like going through so many pages.
Full Roster
Fire Support (overlaps with other 2 PDFs)
Air (overlaps with other 2 PDFs)

Enemy Force Estimates posted:

3rd Brigade of US 1st Armored Division, composed of 2 Infantry Battalions and 1 Tank Battalion, likely supported by a recent transfer of another Tank Battalion and Self-propelled Howitzer battery.
"NATO is likely to divert multiple fires and assets"

Current force estimate:
M1 IP Abrams - 58
M1A1 Abrams - 58
M901 - 12
Mechanized Rifle Infantry - 72 (armed with Dragons, max range 1000m)
M106A1 Mortars - 24
OH-58C Kiowa - 8
AH-1F Cobra (with TOW-2s) - 9
M48A1 Chaparral - 4
M109A2 - 24

I am assuming this is an undercount.

The New Plan posted:

COLOURS
RED arrows represents main effort.
DARK BLUE areas represent critical areas threatening main effort.
LIGHT BLUE represents problematic potential ambush or overwatch positions.
PURPLE represents potential enemy positions that would be problematic, but are less likely due to their extreme east position.
Within the following plans, regiments have been given colours: GREEN, YELLOW, ORANGE, PINK. Exact assignments to be decided by CIC. Recommend YELLOW be Motor Rifle Regiment.

MARCHING ORDER

AoA 1 (CENTER):
1. YELLOW RECON and ORANGE RECON arriving first.
2. Rest of YELLOW regiment
3. Rest of ORANGE regiment.
4. DAG 1, DAG 2 and Div HQ (if on-map).

AoA 2 (NORTH):
1. GREEN RECON and PINK RECON arriving first.
2. Rest of GREEN regiment.
3. Rest of PINK regiment.

AoA 3 (SOUTH): UNUSED

REGIMENTAL ASSIGNMENTS

1. YELLOW Regiment
1.1. Send Combat Recon Patrol towards dark blue zone (Hohenhausling-Drusendorf an dem Aufsess).
1.2. Detach one infantry battalion to set up defensive positions around Hollfeld, protecting DAG and Div HQ. Ensure anti-air coverage over DAG and Div HQ. Leave DAG sufficient room to relocate to avoid counter-battery fire.
1.3. Rest of regiment is to proceed towards dark blue zone (Hohenhausling-Drusendorf an dem Aufsess) and prevent enemy from threatening Highway B22.
1.4. If no significant resistance is encountered, regiment (minus detached battalion) is to proceed to hills around Zeckendorf\Ludwag\Wurau, clear them and provide overwatch during assault over Schesslitz.
1.5. Once Schesslitz is taken, regiment is to wait for other forces to pass, and rejoin column as rear guard.
1.6. At all times regiment is to coordinate with ORANGE.
1.7. As the battle progresses, security detachment is to secure forward positions for DAG batteries to move up.

2. ORANGE regiment
2.1. Send Combat Recon Patrol north-west of Hollfeld, reconnoitring area between Highway B505 and B22, as well as hills by Wiesentfels. If no significant resistance is encountered, CRP is to rejoin Highway B22.
2.2. Main body of regiment is to proceed along Highway B22 towards Schesslitz. Once Schesslitz is taken, regiment is to proceed towards Bamberg.
2.3. At all times regiment is to coordinate with ORANGE and PINK.

3. GREEN regiment
3.1. Send Combat Recon Patrol north-west towards Fuselsdorf, then proceed towards Dark Blue Area Schweisdorf-Wattendorf.
3.2. Main body of regiment is to support PINK regiment’s advance along Highway B505. CIC to select between two courses of action.
3.2.1. COA 1: proceed along north road parallel to B505, then rejoin B505 at crossroads south-west of Grafenhausling and assault Schesslitz.
3.2.2. COA 2: proceed along northern route through Arnstein towards Dark Blue Area Schweidorf-Wattendorf. Root out enemy presence and gain control over defensive terrain overlooking Schesslitz.
3.3. CIC to select between courses of action.
3.3.1. COA1: Disperse and secure area around Schesslitz. Find and eliminate enemy spotters to ensure security of logistical route and protect advancing DAG. Once area is secure, reform and act as mobile reserve.
3.3.2. COA2: Rejoin road column along B22/B505.
3.3.3. COA 3: Proceed west, securing hills overlooking Gundelsheim\Weichendorf.
3.4. At all times coordinate with PINK regiment

4. PINK regiment
4.1. Send Combat Recon Patrol along B505 or parallel road north of B505.
4.2. Main body of regiment is to proceed along B505 towards Schesslitz.
4.3. Gain control over hills south-west of Burglesau in preparation for assault on Schesslitz.
4.4. Assault Schesslitz. Once taken, proceed towards BAMBERG.
4.5. At all times coordinate with GREEN and ORANGE.

DAG

3 SPA (Callsign VOLK) is to remain off-map and provide immediate fire support and masking to YELLOW and ORANGE. VOLK is expected to expend all ammunition before line of contact moves beyond range – roughly Grafhausling\Hohenhausling axis.

GRAD MLRLS (Callsign LOS) is to remain off-map and hold fire until a critical concentration of enemy forces is identified and fixed.

1 SPA and 2 SPA (Callsign RYS and MEDVED) are to deploy near Hollfeld and support division advance. Once line of contact moves forward, batteries are expected to advance along either B22 or B505 in coordination with security element and anti-air batteries. One redeployment is expected before assault on Schesslitz. Second redeployment is expected before assault on Bamberg. Batteries are expected to conduct minor redeployments frequently in order to avoid hostile counter-battery fire.

Fire priority is as follows:
1. Counter-battery fire
2. Facilitating movement along B22 and B505 though both masking and suppression fire missions
3. Enemy ammo dumps, HQs and anti-air batteries
4. Major enemy concentrations, particularly Abrams
5. Reinforcement of successful breakthroughs.

Regiments are expected to rely on their own fires. Divisional fires are expected to reinforce success, not mitigate failure.

AIR SUPPORT
To be filled in by CIC or Air Controller.

EW
To be filled in by CIC or controller.

BadOptics posted:

From my own experiences in FCSS; I would second (third?) the suggestions for the forces to be able to mutually support instead of fighting 3 different battles due to terrain considerations. Personally, I try to echelon my forces in Warsaw Pact style and keep a battalion (or company if the scenario is smaller) ready in a location to "reinforce success".

I'll be interested to see how that game goes Zeppelin; I've been trying to play some PBEM games in FCSS with what time I have and it's totally different - more challenging but also more enjoyable.

I think you were the person who posted the IKS discord in this thread - I'd definitely be interested in trying out "multiplayer" FCSS if they run an event like this again.

Frosted Flake posted:

Orange Devil posted:

Orange Devil posted:

It looks a lot better. Such a juicy road running from Königsfeld to Poxdorf though.

You're making me real invested in finding out how poo poo actually goes down. Please do share.

Tankbuster posted:

given that the recent warscape 2 editor happened because CA helped the modders, I would say no they weren't afraid of modders eating their lunch. Its absolutely something people who don't make mods say. Loading in custom models was a slightly more difficult method that was also eventually solved by modders. Its just that the modders who made the GCCM campaign map addons are far less active during warhammer 3. At the same time, the pipeline for adding custom animations/actual new sounds/UI elements etc is far more refined so people like making their bleep bloop models and putting them into the game.

Warhammer 3 has a giant more classic warhammer fantasy map focused on the old world and it works great. You absolutely see the lack of polish and doodads because instead of a team of professionals making it, its mostly just one guy who also likes modding bethesda games.

1stGear posted:

Zeppelin Insanity, all this planning is bullshit. Just charge forward with sufficient elan and everything will work itself out. If it doesn't work out, then obviously the enlisted lacked sufficient elan and you as an officer can't be held responsible for that.

FirstnameLastname posted:

afaik a lot of the decline in mod support in games has been mostly pushed from the corporate level because robust mod supply makes it harder to make artificial markets with horse armor kinda dlc
kind of a minor distinction but imo makes sense if you look at how with most titles that've slipped backwards it's more of an absence of support or planned flexibility than intentional lockout

Zeppelin Insanity posted:

Will do! Note the game will probably last several months, since usually players have about 24 hours to submit orders, and umpires usually resolve a turn within 48 hours. So, when each turn represents 45-ish minutes in the scenario, that adds up quickly. Also I just realized the first turn starts on February 19th. I guess I got a bit too excited and carried away.

Mister Bates posted:

lmao the guys who made Vietnam '68 and Afghanistan 2011 have released the third game in the series, and it's a loving South African Border War game in which you play the South African apartheid state attempting to put down the pro-independence movement in their colonial frontier

Mister Bates posted:

Afghanistan 2011 was so incredibly tone-deaf that it was possible to mistake it for a deliberate anti-war statement, a dark satire in which you are forced to repeat all of the mistakes that led to the US losing the war in real life, doomed to fail because there is no option available to you but failure

but nope lol the developers were being completely sincere and they're just Nazis

Mister Bates posted:

Afghanistan 2011 was so incredibly tone-deaf that it was possible to mistake it for a deliberate anti-war statement, a dark satire in which you are forced to repeat all of the mistakes that led to the US losing the war in real life, doomed to fail because there is no option available to you but failure

but nope lol the developers were being completely sincere and they're just Nazis

Some rando on Steam posted:

As an OEF/OIF veteran I really want to like this game, truely I do. However, it isn't so much a wargame, tactical, operational or otherwise as it is a LOGCAP one. You'll spend more time conducting ReSupp missions to your FOB's and units in the field than actually engaging in COIN operations, which eventually becomes the sole focus of your playtime. I understand that this game mechanic is meant to be a sort of juggling act but it simply consumes far too much gameplay time.

It would've been nice to have this system somewhat automated - Create a convoy with the required assets, supplies and predefine the departure time at a given turn to resupply the FOB's, the convoys could then do their thing. The player could then inject themselves back into these missions should there be any damage or losses.

Perhaps the largest issue is that there is no way to conduct any sort of combat ops, large or otherwise to secure a village or town under Taliban or Militia control. Instead you're forced to do it via a rather abstract system of winning 'Hearts and Minds'. That's great and all for the locales that are neutral but not so much for those villages or towns that are firmly under enemy control (eg. Marjah/Op. Moshtarak). The Hearts and Minds aspect just doesn't work here and is simply a fundamentally flawed component as the time for building waterworks and delivering aid has long since past.

I hoping some of these issues will be addressed in the future, especially that of enemy strongholds.

BadOptics posted:

Edit: Also, the first command cycle of my Flashpoint Campaigns: Southern Storm PBEM game finished up - already have some screenshots and a draft post. Figured I'd effort post the scenario as I play through it as there seems to be some interest in that game.

Tekopo posted:

I'm doing a narrative LP on a hex-n-counter for the invasion of crete if people are interested in checking it out.