Retreat versus withdraw

[Torasaur]

There should be a major difference between when an army retreats and when it withdraws. At the moment, it seems like if you retreat and or withdraw from a bad situation, the army becomes uncontrollable for months. It's a little absurd, I had an army retreat through three states after telling it to withdraw. I know that there is some "variance" in that if you withdraw it can turn into a retreat / rout but that even brings up another point. There is a difference between withdraw, retreat and route. Furthermore, an army shouldn't flee through three states, before reconstituting. If the army got it's ass kicked that bad it should just disintegrate.

[Ratboy]

I agree, I did an 1861 campaign and one of my corps got engaged with their army of virginia, so I withdrew and the whole army retreated to New York. This needs to be fixed soon.

[Zipuli]

It should work so that withdrawal = unit continues skirmishing with the enemy, and can be given movement order. Withdrawal can turn into retreat, which will not have skirmishing, and unit is non-responsive...

Let's check if it is working as it should...

[Torasaur]

it's definitely not working as it should. My army of the Southwest has been retreating for literally months across 3 states. I can't give them any movement orders. Even after they got to their destination (Leavenworth) they are stationary but their status is still "retreating". Effectively I had an army wiped out because their permanent retreat status makes them irrelevant. They still cost me money to maintain of course but they don't accept any orders of any kind.

[JDpower]

Just found out you have to manually give it stop orders and then after the usual order delay your can resume telling it where to go rather than wait for it run 4 states away