Synchronised movements question

[Jamey]

Playing the tutorial. I move Grant, Sherman, and Mclerndand south to the Rebels at Corinth, using synchronized movement and offensive posture, per the tutorial.

Hit End Turn. They move south, have a battle, and win it. Now here's where it gets a little weird. Grant is in the region where Corinth is, besieging it. However, Sherman and Mclernand are both in the region below it, something like Pocahontes. It looks like they pursued the enemy after the battle or something. All three stacks still have synchronized movement selected.

Hmmm, not mentioned in tutorial, but I figure Sherman and Mclernand will move back up to Corinth next turn and join the seige. I keep on with tutorial.

Next turn, another battle for Corinth. The battle report shows that Mclernand joined in the battle but not Sherman. I think, well at least Mclernand should now be in the same region as Grant. But no. Sherman and Mclearnand are still in Pocahontes, while Grant is in Corinth.

Hmmm. Well tutorial instructions are over, but I keep playing. I order Grant to move to Memphis, make sure synchronized movement is selected on him, Sherman, and Mclernand and that offensive posture is set for all three. I hit End Turn.

Next turn, Grant moves to Memphis and starts besieging it all by himself! Sherman and Mclernand are still sitting in Pocahantes. I hit End Turn again, thinking they must be slow and will move to Memphis next turn.

Nope. Next turn they are still sitting in Pocahantes.

What am I doing wrong or misunderstanding?

[Son of Montfort]

I noticed this too. Before ending the turn, my projected movement says that the Army (which only has the general and a few units) will move to the region in 5-6 days while it will take the corps 12-13 days, all while in Sychronized movement mode. When the turn is resolved, the projections become reality. This leads to some uncomfortable battles... to say the least! Is this WAD or a bug?

SoM

[Primasprit]

Hello Jamey,

Sorry for the confusion, this may have happened:
As you attacked the enemy at Corinth you dropped your stack directly at the enemy and not to some "free" place next to him. If you drop one unit directly on another this can trigger two different actions: If the unit is one of yours they will merge (as described in the tutorial). If the unit you drop yours on, is an enemy, they will try to intercept him. Sorry, I simply forgot to mention that in the tutorial. So most probably you gave your corps an intercept order and they pursuit the enemy until the turn was over or they lost track of him. If they loose track of the enemy they will stop where they are, not moving any further. Also not back there they came from. This is why they didn't walked back to Corinth.
As the second battle for Corinth started the "Marching to the Sound of Guns"-rule triggered. The Army attacking Corinth called for reinforcements and there is a good chance that corps in adjacent regions will join the fight. After the battle they will go back to the regions they were before.
As you walked to Memphis the corps didn't followed the army because the sync-move command can only work if all units start in the same region.

[Primasprit]

I noticed this too. Before ending the turn, my projected movement says that the Army (which only has the general and a few units) will move to the region in 5-6 days while it will take the corps 12-13 days, all while in Sychronized movement mode. When the turn is resolved, the projections become reality. This leads to some uncomfortable battles... to say the least! Is this WAD or a bug?
SoM

In sync-move all units should arrive in the target region at the same day, moving at the speed of the slowest unit. However the corps have to be attached to the army they do the sync move with, and not to another.
If you switch the army to sync-move and drag it to another region they should automatically take their corps with them.

[Jamey]

Hello Jamey,

Sorry for the confusion, this may have happened:
As you attacked the enemy at Corinth you dropped your stack directly at the enemy and not to some "free" place next to him. If you drop one unit directly on another this can trigger two different actions: If the unit is one of yours they will merge (as described in the tutorial). If the unit you drop yours on, is an enemy, they will try to intercept him. Sorry, I simply forgot to mention that in the tutorial. So most probably you gave your corps an intercept order and they pursuit the enemy until the turn was over or they lost track of him. If they loose track of the enemy they will stop where they are, not moving any further. Also not back there they came from. This is why they didn't walked back to Corinth.
As the second battle for Corinth started the "Marching to the Sound of Guns"-rule triggered. The Army attacking Corinth called for reinforcements and there is a good chance that corps in adjacent regions will join the fight. After the battle they will go back to the regions they were before.
As you walked to Memphis the corps didn't followed the army because the sync-move command can only work if all units start in the same region.

Excellent explanation! This all makes perfect sense. Especially the part about all the units needing to be in the same region for synchronized movement to work is very helpful.

Thank you, Primasprit and thank you again for a great tutorial!