shatter factors from rear rank

[Roger]

see before and after pictures
Unit of 4 Charging lancers charge unit of 6 Knights front rank Armoured rider, charging lancer, DC, Back rank Protected DC.
They start the charge from in front so count as fighting to the front,1 file hits rear protected Rank and 1 file hits front Charging lancer.
Chargers bag so we do Rear rank combat first.
No Dc factors because they are in 1 rank, chargers threw skull and wound defenders threw "S"
Question? do they give the shatter to the front rank because:-
                1. they are both fighting to the front
                2. they are "adjacent"

[attachment deleted by admin]

[lionheartrjc]

As far as I see it, they meet the requirements for a "neighbouring file" so yes, they can count a Shatter.  (Edge contact - note it doesn't say side edge, facing the same way and parallel).

Richard

[LawrenceG]

Not clear from the rules that a neighbouring base in the same file qualifies as a neighbouring "file". (Probably intended, though)

What about a base in the same file that is not adjacent to the base that scored the S?

In general, is a file neighbouring itself?

[steads]

Not clear from the rules that a neighbouring base in the same file qualifies as a neighbouring "file". (Probably intended, though)

What about a base in the same file that is not adjacent to the base that scored the S?

In general, is a file neighbouring itself?

It is the neighbouring base of the chargers NOT the target

[LawrenceG]

Not clear from the rules that a neighbouring base in the same file qualifies as a neighbouring "file". (Probably intended, though)

What about a base in the same file that is not adjacent to the base that scored the S?

In general, is a file neighbouring itself?

It is the neighbouring base of the chargers NOT the target

In the OP it was the target TuG that rolled the S.

[lionheartrjc]

As I read it,

The attackers threw a Skull and Wound so would get a Shatter.  (I am unclear why they are two results - I am assuming the initial roll was the skull whilst the wound is from the adjacent file and isn't actually relevant to the question).
The defender threw an S.  (So also get a Shatter).

The question asked about the defenders.   By definition,  the conditions of the neighbouring file are met so both sides would count a shatter.

Richard

[LawrenceG]

As I read it,

The attackers threw a Skull and Wound so would get a Shatter.  (I am unclear why they are two results - I am assuming the initial roll was the skull whilst the wound is from the adjacent file and isn't actually relevant to the question).
The defender threw an S.  (So also get a Shatter).

The question asked about the defenders.   By definition,  the conditions of the neighbouring file are met so both sides would count a shatter.

Richard

The definition of neighbouring file in the glossary (pdf version) is:

Neighbouring files are those in edge contact with, facing the same way, and parallel to the
file creating a shatter or shove.

On the face of it, the second defending base is in the same file as the first one, i.e. it is in the file creating the shatter, not a file that is in edge contact with the file creating the shatter.

It think RJC's "umpire decision" that the shatter does count is in the spirit of the rules, but I'm not so sure it can be derived directly from the rules as written.