Landing Zone Overrun before Combat?

[rkr1958]

Here's the situation:

(1) German II Para corps dropped well behind the French lines on hex 54,30.

(2) French elect to use the notional.

(3) Before the drop is resolved, a breakthrough is achieved in a prior land combat and the landing zone is overrun.

(4) Shouldn't the II Para drop now be automatic as now Germany controls the drop hex?

[rkr1958]

game turn at the start of the land combat resolution phase.

MWiF version 3.1.0.5

[Centuur]

From the FAQ:

You get a B result in land combat and
could move into a hex where a combat is
to follow (only possible with a notional
being invaded / paradropped on), you:
(a) Move in for free making the paradrop /
invasion obsolete
OR (b) Have to overrun the notional with the
notional having whatever combat factors it
has due to the declared paradrop /
invasion
OR (c) Cannot move into the hex?
Answer:
(a), it could mean you are overstacked
though (after the landing) in which case
some units may die. Date 29/11/2007

So you've found a bug here. However, there's no gamesave included. Can you post it so that Steve can fix this?

[Courtenay]

ORIGINAL: Centuur

From the FAQ:

You get a B result in land combat and
could move into a hex where a combat is
to follow (only possible with a notional
being invaded / paradropped on), you:
(a) Move in for free making the paradrop /
invasion obsolete
OR (b) Have to overrun the notional with the
notional having whatever combat factors it
has due to the declared paradrop /
invasion
OR (c) Cannot move into the hex?
Answer:
(a), it could mean you are overstacked
though (after the landing) in which case
some units may die. Date 29/11/2007

So you've found a bug here. However, there's no gamesave included. Can you post it so that Steve can fix this?

It is also possible to advance into a hex where combat is to occur on an overrun. This is covered in RAC:

Clarification: An advance after combat into a second hex can result in you occupying a hex that you have already declared you are going to attack. This can happen by overrunning units in the second hex or if the second hex only contained a notional unit slated for a paradrop or invasion. If you occupy the second hex, the declared combat in the second hex is ignored; however, the paradropping and/ or invading units (if any) must also occupy the hex, which may result in overstacking and the destruction of some of your units.

[rkr1958]

ORIGINAL: rkr1958

game turn at the start of the land combat resolution phase.

MWiF version 3.1.0.5

ORIGINAL: Centuur

So you've found a bug here. However, there's no gamesave included. Can you post it so that Steve can fix this?

My bad, thought I'd uploaded the game turn in my second post. [:(]

Here's the turn at the start of the land combat resolution phase and before the overrun.

[Shannon V. OKeets]

This is the first time I have heard about this rule.[X(]

Well, actually, I think I inserted the clarification in RAC, but that was at least 15 years ago.[8|] The text was taken from Harry Rowland's numerous replies to questions from players (circa 2008, I think).

I will need to see if there is any code to implement it. I suspect there isn't any.[:(]

Hey, no one reported this for CWIF/MWIF over the last 24 years (1996 to 2020), so I guess it doesn't happen very often.[:D]

EDIT: Also, WiF was released in 1985, and Harry didn't write the clarification until 2008, so I guess there was a 23 year lag before anyone reported it to Harry.[:D][:D][:D]

[rkr1958]

ORIGINAL: Shannon V. OKeets

This is the first time I have heard about this rule.[X(]

Well, actually, I think I inserted the clarification in RAC, but that was at least 15 years ago.[8|] The text was taken from Harry Rowland's numerous replies to questions from players (circa 2008, I think).

I will need to see if there is any code to implement it. I suspect there isn't any.[:(]

Hey, no one reported this for CWIF/MWIF over the last 24 years (1996 to 2020), so I guess it doesn't happen very often.[:D]

EDIT: Also, WiF was released in 1985, and Harry didn't write the clarification until 2008, so I guess there was a 23 year lag before anyone reported it to Harry.[:D][:D][:D]

Glad to help. [:)]