Merge order quirkiness

[John Sedgwick]

I ordered Markov's division merge with Mai-Maievski's corps one day away by rail, but after redeploying Borovsky from Mai-Mai's corps to Azov, Markov's orders were changed to "Merge with Kornilov Division" (Borovsky), so he followed him home like a lost puppy. What gives? The merge command can be very useful, but it's so quirky I'm always a little scared to use it in the face of danger. Luckily no one was hurt this time, but it could've turned nasty (didn't control all of the railway he traversed), and now I've got to get him back there somehow. Harumph.

[lodilefty]

This happens in all the games.

I suspect that there is no easy fix, and "hard to do fixes" are off the radar at this time...

Essentially, NEVER split the target group after a merge order is given to someone heading that way.

....or, recreate the merge order after you split the target....

[John Sedgwick]

Thanks lodilefty, another lesson learned I guess.

I don't recall the exact circumstances (it was somewhere up north), but in my singleplayer games, I once saw a stack ordered to merge with a stationary stack one region away, make a completely unnecessary detour through an enemy stack two regions away and get destroyed before it was able to reach its destination. Is this another one of those "off the radar" quirks?

[lodilefty]

Thanks lodilefty, another lesson learned I guess.

I don't recall the exact circumstances (it was somewhere up north), but in my singleplayer games, I once saw a stack ordered to merge with a stationary stack one region away, make a completely unnecessary detour through an enemy stack two regions away and get destroyed before it was able to reach its destination. Is this another one of those "off the radar" quirks?

I'm digging into "pathfinding" for RoP questions, and since it's all same engine, we'll be able to better understand these types of things...