QuantumEleven
Lightsider
I tend to play on huge maps (ie lots of units), which means that the stack movement commands are a godsend... However, I've noticed a rather odd bug recently: (C3C 1.15)
Description:
If I have units with different number of movement points and I give them a stack move command (either "stack move" or "stack move identical units only", it's the same with both) to a location which is further away than the movement points remaining for one of the units in the stack, then the whole stack will only move as far as that unit can, and then stop - while leaving no movement points remaining for the other units.
Steps to reproduce:
I've attached a save to illustrate. I've got two cavalry units, one with 2 movement points remaining, and one with 1, sitting on top of each other. If I now tell the two to move one squares away using stack movement (over flat land - no movement penalties), then it works as expected: Both units move, and the cavalry which had 1 MP remaining has now exhausted its MPs and stops, while the other is still active with 1MP remaining, asking for orders.
However, if I start from the same position as before and give a stack movement command to two squares away, then both cavalries will only move one square, and stop, with both shown as having 0 MP remaining. What happened to the spare MP that one of the two had...? Ordinarily, I would have expected the result to be the same as above: Both cavalries move one square, and then the cavalry that had 2MPs at the start has 1 left and can be moved one more square.
Now, I said "possible bug" in the title because I'm not 100% convinced that this isn't a feature - designed to keep stacks together even if they have different movement points remaining. Can anyone confirm or deny this?
Save here.
Description:
If I have units with different number of movement points and I give them a stack move command (either "stack move" or "stack move identical units only", it's the same with both) to a location which is further away than the movement points remaining for one of the units in the stack, then the whole stack will only move as far as that unit can, and then stop - while leaving no movement points remaining for the other units.
Steps to reproduce:
I've attached a save to illustrate. I've got two cavalry units, one with 2 movement points remaining, and one with 1, sitting on top of each other. If I now tell the two to move one squares away using stack movement (over flat land - no movement penalties), then it works as expected: Both units move, and the cavalry which had 1 MP remaining has now exhausted its MPs and stops, while the other is still active with 1MP remaining, asking for orders.
However, if I start from the same position as before and give a stack movement command to two squares away, then both cavalries will only move one square, and stop, with both shown as having 0 MP remaining. What happened to the spare MP that one of the two had...? Ordinarily, I would have expected the result to be the same as above: Both cavalries move one square, and then the cavalry that had 2MPs at the start has 1 left and can be moved one more square.
Now, I said "possible bug" in the title because I'm not 100% convinced that this isn't a feature - designed to keep stacks together even if they have different movement points remaining. Can anyone confirm or deny this?
Save here.
