In RL no good commander would change the orders after the troops have crossed the assault line. By that time the die is cast and you should just wait. If you do change the order then the attack will be replanned and yes you will end up back at the FUP if you had assigned one. My advice is to pause and issue the attack orders with all the setting you desire, then let it be.
Now a point I don't look thru, I adjusted some values(As far as I can see just ONLY Aggro, ROF, Ammo) for a bat. attack and as these new orders arrive with the attack already rolling the 3 companies attacking get the order to fall back to the FUP for a reorg task, I can't imagine that it should work that way, shouldn't these kind of adjustments be put into the rolling attack "on the fly"?
Some other situations which generally don¡¦t cause replans or incur orders delay are listed below. The list isn¡¦t complete, so there is still room for you to experiment and discover some of this for yourself, but in general anything not specifically mentioned below will probably incur orders delay.
Move or Defend Orders
„b Changing Speed, Route, Aggro, ROF, and Losses
„b Changing Frontage, Depth, and Facing
„b Changing Formation, except for In-Situ, which does incur orders delay
Attack or Probe Orders
„b Changing Speed, Route, ROF, and Losses
„b Changing Frontage, Depth, or Facing
„b Changing Formation (except for In-Situ) during the move to FUP, or sometimes (but not always) during the assault
You might need to do some more tests to see if there was not somethng else going on BigDuke, because as far as I cas see from the manual, you should not have needed a replan, unless it was the agro change?
< Message edited by dazkaz15 -- 3/15/2013 10:53:25 AM >