This is insufficient this only tells you the angle of the charge, however the distance moved before the wheel may alter which BG can intercept. The declaration needs to be of the path of the charge.shall wrote:Ok we'll FAQ it ...
But its pretty obvious that you need a path if there are potential interceptros or you don't know if they can or can't. It doesn't really matter as long as you move interceptors before any evades as Terry says.
So something like this I guess
Si"when do we need to delcare a direction for charge at that time?"
If troops are around who may intercept or evade - while the rules say its needed if evaders exist, we didn't make explciit that you will need a charge path to decide if interceptors can do anything (which happens in fact before evades). So if there are potential interceptors declare a pathm check its legal and decide if interceptors can move. Then move interceptors. Then move evades. Then move chargers.
I think that in practice you need to declare the path of the charge when the charge is declared, because it alters what other charges you can declare.
Example 1
A BG is blocked by another BG partially in front - if the front BG's path - provided nothing evades or intercepts - is such that gets out of the rear BG's way then the rear then it should be able to declare a charge.
Example 2
BGs A and B can each charge enemy BG E - which can't evade. B's charge can be intercepted by I. A and B can both wheel enough to prevent the other from contacting E.
IF I intercepts then the player can do A first and block B's charge which is then cancelled - leaving I having intercepted a charge that didn't happen [ which isn't too unreasonable - untill C hits it in the flank because it also hasn't declared a path yet and 1 base into the flank of I is as many bases as it was going to get straight ahead.]
If I doesn't intercept then the player can choose to charge A and B to both contact - and fight with overlaps, or do B's charge first to block A so its charge is cancelled.
