The Army commander doesn't always pass stats on to his Corps commanders
ArmChairGeneral wrote:BTW: Check out the Confederate battle flag roundel on ASJ's map-icon. Thanks fred zeppelin! (Link to mod.)
moni kerr wrote:There is a downside to this configuration. During combat an enemy force will not target the Army if there is an active Corps in the region.
A wily opponent would attack the Army stack and let the Corps mtsg in support. Once that Corps enters the region and joins in the combat, it's units will get all of the attention of the attacker and will not gain the benefit of the fortifications. The results can be quite devastating.
moni kerr wrote:There is a downside to this configuration. During combat an enemy force will not target the Army if there is an active Corps in the region.
A wily opponent would attack the Army stack and let the Corps mtsg in support. Once that Corps enters the region and joins in the combat, it's units will get all of the attention of the attacker and will not gain the benefit of the fortifications. The results can be quite devastating.
veji1 wrote:If it is the case, this is a big big problem, because it means that it is an engine featured that can be exploited. I would have thought though, that the army stack having been engaged first was more or less locked by the routine into fighting until its units started being depleted. I would be suprised if the engine just shifted the focus of the battle like that ?
veji1 wrote:If it is the case, this is a big big problem, because it means that it is an engine featured that can be exploited. I would have thought though, that the army stack having been engaged first was more or less locked by the routine into fighting until its units started being depleted. I would be suprised if the engine just shifted the focus of the battle like that ?
ArmChairGeneral wrote:Not so fast!
I have observational data on this (posting shortly) and there is more going on than first appears. The main problem is that if the Army stack is not targeted by an opposing stack it can only come in to "support" a friendly stack that was already attacked, which causes it to leave its trenches! Opposing stacks tend to target MTSGers, because the Army stack takes lots of hits on the first round (because it is the only stack and is automatically targeted) and wants to sit out until the other divisions have taken hits as well. When it returns, it supports its friends by leaving the trenches and charging across the battlefield to the rescue.
If there is also a Corps in the region this can still happen to the Army stack but less often for some reason. The Corps always stays in its trenches the whole battle, however because it is not MTSG (already in region). In cases where the Army is larger it usually gets targeted and does not have to leave its trenches.
The main thrust of the evidence so far is that relying on MTSG Divisions to support a smallish Army stack (2Divs) means that you will often not benefit from entrenchment for the Army either.
If you are defending with an Army stack it is important to have as many Divisions in it as possible so that it can hold its own until MTSGs arrive on the later rounds. I had good results with 3 Div under ASJ against a 4 Div 3000 PWR stack under Grant, but less so when the third division was with the Corps instead and had to MTSG.
The analysis includes screenshots and is several pages long. I will post it to the AAR section, and will include a save so that the setups can be replicated and further experimented with by others.
moni kerr wrote:There is a downside to this configuration. During combat an enemy force will not target the Army if there is an active Corps in the region.
A wily opponent would attack the Army stack and let the Corps mtsg in support. Once that Corps enters the region and joins in the combat, it's units will get all of the attention of the attacker and will not gain the benefit of the fortifications. The results can be quite devastating.
Users browsing this forum: No registered users and 7 guests