How come the defender did not withdraw?

Combat Command is Boku Strategy Games World War II operational game. strategy games played warfare on a hex playing field with turn-based game play utilizing company-sized units. Game design aspects include turn phases, combat resolution, unit design, scenarios and artificial intelligence.

Moderator: Obsolete

Post Reply
User avatar
Fred98
Posts: 4019
Joined: Fri Jan 05, 2001 10:00 am
Location: Wollondilly, Sydney

How come the defender did not withdraw?

Post by Fred98 »

I am playing the German side against a US AI opponent.

The Germans have just completed their Assault phase.

You can see from the screenshot that the US unit should have withdrawn. The unit began the scenario in a level 2 fort.

How come the unit did not withdraw?
-


Image


-
User avatar
PirateJock
Posts: 469
Joined: Thu Sep 14, 2006 8:59 pm
Location: North West, UK

RE: How come the defender did not withdraw?

Post by PirateJock »

Is it because the game's still in the Direct Fire phase? The Withdraw/Advance phase hasn't started yet.

Cheers
Combat Command Matrix Edition Company, The Forgotten Few
User avatar
Fred98
Posts: 4019
Joined: Fri Jan 05, 2001 10:00 am
Location: Wollondilly, Sydney

RE: How come the defender did not withdraw?

Post by Fred98 »

Page 38 Combat Sequence.

During the Assault Phase, Defender retreats then the Attacker advances.

But sometimes the defender does not retreat. I have seen this a few times.

-
Budas
Posts: 9
Joined: Thu Apr 28, 2011 11:57 am

RE: How come the defender did not withdraw?

Post by Budas »

I've noticed this too. There is further reference later in the manual on withdrawal. It states that if a unit cannot withdraw due to the presence of EZOCs or enemy units it takes a withdrawal check, assumes a defensive posture and remains in place.

I assume this applies in the case illustrated. The presence of substantial Axis forces has caused your unit to take a check and disruption is increased leaving it in a precarious position for the next turn.

I suppose the rationale behind it is that it is very difficult to extricate troops successfully from the front line when faced with a large body of the enemy.

This issue could benefit from further explanation I think.

Bud
User avatar
Obsolete
Posts: 1388
Joined: Tue Sep 04, 2007 8:52 pm

RE: How come the defender did not withdraw?

Post by Obsolete »

Often a unit fails to withdraw because it fails its withdraw checks.

Also remember, if a unit finds itself not in an E-ZoC after a battle, it doesn't have to withdraw anymore. So technically, you could have an enemy unit right next to your hex, but your own unit doesn't have to withdraw if you knocked him down to say... a level 4 disruption (units that badly disorganized have no ZoC). Anyhow, I'm very tired right now, but that's at least how I remember it right now.
Image
Image
King-Tigers don't let Tiger-I's get over-run.
User avatar
Fred98
Posts: 4019
Joined: Fri Jan 05, 2001 10:00 am
Location: Wollondilly, Sydney

RE: How come the defender did not withdraw?

Post by Fred98 »

ORIGINAL: Obsolete
........a level 4 disruption (units that badly disorganized have no ZoC).


This must be the answer! The attacker reached a disruption level of 3 or 4. Such a unit exerts no ZOC so the defender will not withdraw!

-
User avatar
Obsolete
Posts: 1388
Joined: Tue Sep 04, 2007 8:52 pm

RE: How come the defender did not withdraw?

Post by Obsolete »

I've played so many similar games that sometimes it's hard to tell one rule-set from another. So I could be wrong, but I THINK a unit at level 3-disruption also may exert no ZoC. Or was that just the cut-off for force d withdrawls, or both.  ARggg... I'll have to re-check on all that when I get back again.
Image
Image
King-Tigers don't let Tiger-I's get over-run.
Post Reply

Return to “Combat Command Series”