Gray Fox said:
HAAC doesn't affect retreat of the stack. It affects the level of losses accepted before withdrawal of a unit engaged from combat. The Wiki has been hacked, but there used to be a table and on that table HAAC had a higher number, IIRC 0.38, for determining withdrawal.
I'm not sure this is exactly correct.
There are multiple retreat types: a chance to avoid a combat altogether before it even starts, the decision to withdraw voluntarily and in good order preceding any round of combat, (including the first round) and a forced retreat because of negative combat results (rout).
I thought orders (in this case HAAC) modified the willingness of a commander to voluntarily withdraw at the beginning of each round by changing the threshold for the random roll he makes to decide whether he can successfully withdraw when overmatched. (Hence the .38 number in the old Wiki.) This is a decaying number as rounds go by, with the net effect that he will be willing to fight a couple of rounds rather than immediately retreat when in an obvious overmatch, but still will eventually decide to GTFO by "winning" his progressively easier withdrawal roll as the threshold rises over time. Like Ace says, the calculation of whether he considers himself overmatched or not is based on PWR ratings, (see, PWR ratings do matter!) as evidenced by the calculation at the beginning of every round of the battle log.
HAAC reduces the chance that the general will choose to retreat voluntarily, but doesn't affect the" forced to retreat" situation directly. Forced to retreat is due to elements breaking in the field, i.e. the level of losses. If elements are breaking, the PWR rating is dropping, so even if he does not rout, he will be more likely at the beginning of the next round to voluntarily withdraw because the PWR ratings have changed.
So the game-play effect is that HAAC will make a general stick around for a bit and inflict some casualties, but will tend not to force him to stay on the field and fight to the last man when he would (theoretically) be better off retreating. STRAT rating affects his ability to withdraw in good order, so perversely (for the player) good generals are more likely to be able to withdraw from the type of battle ACE describes than poor ones. It is likely that in Ace's situation that if he had regular orders rather than HAAC, then his general would have retreated either before or after the first round.
No matter what is going on under the hood however, FOX is 100% correct in saying that if you really want to dig in and fight tooth and nail to hold a wilderness position you need a stockade or fort. They will minimize the amount of MC you lose, slow the enemy down, and give at least some chance of retreating into the structure rather than out of the region (although that is not necessarily a good thing

)
In practice I can only imagine a few places on the map where the situation Ace describes would occur: there just aren't that many places where the mountains matter. My guess is Ace is talking about somewhere on the rail line leading west from Harper's Ferry, somewhere in the Ozarks near Springfield, somewhere in the Smokies near Knoxville or in the "backdoor" of far western Virginia. I would be more than willing to spend a stockade on any of these positions if I thought it would secure them.
I agree with Ace that the engine definitely does not take into account terrain advantages that might make a position impregnable: when faced with an enemy twice the size, you will have to do everything you can just to prevent your general from withdrawing before combat even starts, since all he looks at is the relative PWR.
HAAC (Red orders) are super effective for defensive Corps at the point of attack that need to stay in the field so that there is still a battle on the second round that supporting Corps can MTSG to.