Page 1 of 1

bug or "feature"?

Posted: Fri Jun 29, 2007 7:38 pm
by Yamato hugger
I think this falls into the "grey area" between the 2 but here goes:

If a ground unit is set to move someplace and then "switches" between fragment numbers (or parent), its orders will change to whatever the unit that had its designation was before. I will try to illistrate:

1st example bde (parent) is in Bataan with a defend order.
1st example bde/1 is at Wuchow with orders to move to Kunming.
1st example bde/2 is at Kunming with a defend order.
1st example bde/3 is at Dacca with orders to move to Calcutta.

Clear as mud so far? Needless to say in this example we are talking about an evac from the PI by air to Wuchow, marching to Kunming, then air evacing to Dacca with a final assembly point of Calcutta. OK, so next turn:

1st example bde (parent) at Bataan has been reduced in strength to the point where the fragment in Wuchow is now the parent. So the unit in Wuchow that HAD a march order to Kunming now has the old parents order (defend). The fragment in Bataan is now the /1 unit with orders to move to Kunming.

Very annoying. Havent played with it to the point (yet) where 2 fragments combine and see what happens then, or if one of the other fragments (such as the /3 unit) becomes the parent I have to see what effect that has on the other fragment numbers). It is repeatable, it does it anytime the parent changes units for either side.

RE: bug or "feature"?

Posted: Fri Jun 29, 2007 7:42 pm
by dtravel
Bug.

RE: bug or "feature"?

Posted: Sat Jun 30, 2007 12:10 am
by Cpt Sherwood
bug

RE: bug or "feature"?

Posted: Sat Jun 30, 2007 1:07 am
by jwilkerson
ORIGINAL: Yamato hugger

I think this falls into the "grey area" between the 2 but here goes:

If a ground unit is set to move someplace and then "switches" between fragment numbers (or parent), its orders will change to whatever the unit that had its designation was before. I will try to illistrate:

1st example bde (parent) is in Bataan with a defend order.
1st example bde/1 is at Wuchow with orders to move to Kunming.
1st example bde/2 is at Kunming with a defend order.
1st example bde/3 is at Dacca with orders to move to Calcutta.

Clear as mud so far? Needless to say in this example we are talking about an evac from the PI by air to Wuchow, marching to Kunming, then air evacing to Dacca with a final assembly point of Calcutta. OK, so next turn:

1st example bde (parent) at Bataan has been reduced in strength to the point where the fragment in Wuchow is now the parent. So the unit in Wuchow that HAD a march order to Kunming now has the old parents order (defend). The fragment in Bataan is now the /1 unit with orders to move to Kunming.

Very annoying. Havent played with it to the point (yet) where 2 fragments combine and see what happens then, or if one of the other fragments (such as the /3 unit) becomes the parent I have to see what effect that has on the other fragment numbers). It is repeatable, it does it anytime the parent changes units for either side.

Looks like destination field is being swapped over when it shouldn't be - if you have "just before it happens" save pls send over.