Page 1 of 1

Bursting Through Broken Troops

Posted: Sat Sep 19, 2009 2:33 pm
by TERRYFROMSPOKANE
Friendly BG's A and B are heavy infantry. Enemy group P is cavalry.

Despite rear support from B, A has broken as a result of close combat with P in a melee phase. It can not avoid B so bursts through, dropping B one cohesion level. Pursuer P has enough VMD to smack into B, this charge to be resolved in the next impact phase. In the JAP, A routs a normal move.

In the next impact phase, B breaks. It rolls up for VMD and now must burst through A (which is already broken and routing). It appears that since A couldn't move, even if contacted by an enemy charge, it does not rout again when burst through. P rolls up for VMD and pursues into A. Since P is "in contact with a routing enemy", it inflicts one base loss on A. Further action must wait until the JAP. At that time, B routes a full move and A routs a VMD, and someone loses a base if P continues to pursue and manages to end in contact.

Have I got all this right, or have I missed a rule or two?

BTW, the rule on page 108 about pursuers inflicting a base loss is in conflict with the FULL TURN SEQUENCE. The FTS states "Remove bases if pursuers remain in contact at the end of the rout move." In the case above, one could argue P began in contact with and pursuing B and ended in contact with A and, therefore, did not "remain in contact". Changing "remain" to "are" would solve this problem, I think.

Terry G.

Re: Bursting Through Broken Troops

Posted: Sat Sep 19, 2009 4:46 pm
by marioslaz
TERRYFROMSPOKANE wrote:BTW, the rule on page 108 about pursuers inflicting a base loss is in conflict with the FULL TURN SEQUENCE. The FTS states "Remove bases if pursuers remain in contact at the end of the rout move." In the case above, one could argue P began in contact with and pursuing B and ended in contact with A and, therefore, did not "remain in contact". Changing "remain" to "are" would solve this problem, I think.

Terry G.
I think you make a base loss only in JAP. I suppose the reason is first rout move is subsequent to a fight, so you had already a chance to inflict a loss and a new base loss in this phase would be too much a punishment for routers. Of course many odd situations can occur, but base loss for fight against routers is only in JAP which represent a BG that remains in contact with routers for a complete move.

Posted: Sat Sep 19, 2009 6:13 pm
by TERRYFROMSPOKANE
Well, the rule on page 108 says : "Pursuers who are in contact with a routing enemy battle group at the end of ANY pursuit move: Inflict a base loss on the routing battle group...." The CAPS are mine, but pursuit moves occur during Impact, Melee and Joint Action. The rule indicates to me a base could be lost during any of these Phases.

Terry G.

Posted: Sat Sep 19, 2009 6:21 pm
by deadtorius
Well, the rule on page 108 says : "Pursuers who are in contact with a routing enemy battle group at the end of ANY pursuit move: Inflict a base loss on the routing battle group...." The CAPS are mine, but pursuit moves occur during Impact, Melee and Joint Action. The rule indicates to me a base could be lost during any of these Phases.
Thats right Terry, its a lot more deadly than most of us realize to end up in contact with pursuers and broken units will atuobreak a whole lot quicker than we think. Blathergut and I had been playing that part of the game wrong for a long time so our broken units were survivng longer than they should have been.

Posted: Sat Sep 19, 2009 7:00 pm
by marioslaz
TERRYFROMSPOKANE wrote:Well, the rule on page 108 says : "Pursuers who are in contact with a routing enemy battle group at the end of ANY pursuit move: Inflict a base loss on the routing battle group...." The CAPS are mine, but pursuit moves occur during Impact, Melee and Joint Action. The rule indicates to me a base could be lost during any of these Phases.

Terry G.
You are right. I likely got confused with a similar case, but of course with also some differences, of a previous thread. I think it was about a charger which contact router, or something like this.