What game effects are there when a HQ unit is destoyed? (and related design issues)

[Don Maddox]

I'm wondering exactly what happens if one of the HQ units is destoyed. In what fashion does this effect the subordinate units? Is there a list of all the functions that the HQ unit performs?

By "HQ unit" I am referring to units marked with a flag (CP in the DA weapons database).

[CPangracs]

I'm wondering exactly what happens if one of the HQ units is destoyed. In what fashion does this effect the subordinate units? Is there a list of all the functions that the HQ unit performs?

By "HQ unit" I am referring to units marked with a flag (CP in the DA weapons database).If you look at the BOS systems overview included in the DA Guide on the Misc Files section, you will see that C2 Status, which is the ONLY function a headquarters has for units assigned to it, affects units in the following ways:

1. For every level of C2 status below "GREEN", a unit loses 10% lethality.

2. C2 status of "YELLOW" degrades movement rate of a unit by 25%. Anything below YELLOW degrades movement by 50%.

3. The C2 Status of a unit is affected by distance from its HQ IAW the below chart:

DISTANCE STATUS
30 km - - -GREEN
31-50 km - YELLOW
51-70 km - RED
>70 km - - BLACK

So, in conclusion, a unit MUST be assigned to a HQ. If a HQ unit is destroyed, all units that were under that HQ will have a C2 status of black and will move at 50% and fight at 70% lethality, and must be transfered to another HQ unit as soon as possible, or it will die quickly!

Hope this helps.

Curt

[Don Maddox]

Great information. Now allow me to ask a few more questions (and I am reading the documents. I'm just asking questions when I need additional clarifications and/or I suspect something isn't well documented).

Let's suppose we are creating a scenario with an infantry division as the friendly forces (let's call our hypothetical division the 28th). My first instinct was to create the OOB as the "original OOB" in the attachment.

From what you are telling me -- and if I understand this correctly -- this would probably lead to a serious loss of combat power in a Desert Storm-type setting where vast distances can be a serious logistics/command issue. To solve this problem and make DA run the way it should (and to give the commander the flexibility he needs) the OOB should look more like the "revised OOB" in the attachment.

Is this correct? What about the divisional cavalry squadron? Will they need to have a HQ (CP) assigned as well or are they okay on their own? Same question for the DISCOM and the AHB. Am I on the right track here, or am I making this more complicated then it needs to be?

[CPangracs]

Great information. Now allow me to ask a few more questions (and I am reading the documents. I'm just asking questions when I need additional clarifications and/or I suspect something isn't well documented).

Let's suppose we are creating a scenario with an infantry division as the friendly forces (let's call our hypothetical division the 28th). My first instinct was to create the OOB as the "original OOB" in the attachment.

From what you are telling me -- and if I understand this correctly -- this would probably lead to a serious loss of combat power in a Desert Storm-type setting where vast distances can be a serious logistics/command issue. To solve this problem and make DA run the way it should (and to give the commander the flexibility he needs) the OOB should look more like the "revised OOB" in the attachment.

Is this correct? What about the divisional cavalry squadron? Will they need to have a HQ (CP) assigned as well or are they okay on their own? Same question for the DISCOM and the AHB. Am I on the right track here, or am I making this more complicated then it needs to be?The revised OB is the correct one to use in this circumstance. Also, with a Div Cav Sqdn, you should have it assigned to the nearest larger combat element, such as a BCT, which would act as a HQ unit because it falls under, say, the TAC HQ, so the HQ's C2 effect is reproduced and passed-on to the Cav unit. We used this model for our recent exercise, and it worked flawlessly.

Unfortunately, IMO, a Div Cav and some other "independent" unit-types should NOT be hampered by this restriction, and have inherent systems/capabilities that should allow for a more diversified mission-type, and not be restricted by normal C2 values.

[Don Maddox]

The revised OB is the correct one to use in this circumstance. Also, with a Div Cav Sqdn, you should have it assigned to the nearest larger combat element, such as a BCT, which would have a HQ unit.
Which brings up another point: if the cav squadron is out front with 1st and 2nd brigades near behind, it can be assigned to the nearest brigade (let's say it's 1st Bde). If during the course of the battle 3rd brigade comes up and 1st brigade goes into reserve, we then task the cav to 3rd Bde, right?

As for the DISCOM, it doesn't need a CP of it's own correct? It simply needs to remain near the division HQ(Main)?

[CPangracs]

Which brings up another point: if the cav squadron is out front with 1st and 2nd brigades near behind, it can be assigned to the nearest brigade (let's say it's 1st Bde). If during the course of the battle 3rd brigade comes up and 1st brigade goes into reserve, we then task the cav to 3rd Bde, right?

As for the DISCOM, it doesn't need a CP of it's own correct? It simply needs to remain near the division HQ(Main)?Well, it depends on how you want to work it. If 1 and 3 are conducting a passage-of-lines and one is taking-over the mission of the other, then yes, you should reassign the Cav to the new unit.

As for DISCOM, it does NOT need a CP of its own, and the Main or Rear HQ will suffice, whichever is closest.

Also, check my edit of my previous post for more info.

[Don Maddox]

Thanks for the help.