Article 7.4 confuses me, see text I put in bold : should this be deleted or is it missing some words, because as written I don't understand it. Thx for clarifying.
"If an entire file is destroyed any troops fighting their flank the victors can press forward up to 1 BW into contact with other enemy bases directly ahead"
Don't think the issue is the bit you've put in bold, it is "the victors" that is odd and could be removed.
And for those who are confused by the rules reference it is Page 85.
Ah, ok, situation is clear now for me, so I presume its needs also a comma then after 'destroyed'.
Sorry for this, don't want to be picky but I truly had no clue what was meant here but now I see the light :).
Thx Nik,
When a file is destroyed in the charge phase and bases press forward, as allowed under Pg85 7.4, is any new contact with enemy bases treated as:
1. a new charge... ie combat is fought in charge phase with charge phase claims
or
2. a continuation of fighting to be fought in combat phase... giving contacted bases chance to turn post charge phase using cards
Quote from: AandM on February 19, 2022, 06:07:25 PM
When a file is destroyed in the charge phase and bases press forward, as allowed under Pg85 7.4, is any new contact with enemy bases treated as:
1. a new charge... ie combat is fought in charge phase with charge phase claims
or
2. a continuation of fighting to be fought in combat phase... giving contacted bases chance to turn post charge phase using cards
An interesting one as up to now we always left a base in contact as contact may not be broken and press forward happens only during charge phase after first contact but before melee
There are two separate situations here which are getting confused.
In this situation (assuming the file is destroyed but the UG is not broken), then the bases press forward but it is not a charge and there is no further combat in the charge phase (7.4 p85).
If your opposing UG breaks in the combat phase, then you pursue and it is treated as a charge if you would contact new enemy (8.6 p86).
Richard