I know shoves/overlaps were rigorously treated in a previous query, but this question is different - promise!

Consider three files, ABC

A gets a shove result in melee combat.

B is fighting frontally and benefits from the shove.

C is fighting as an overlap for B - does it also benefit from the shove?

Case against: p. 205: "Shove gives a +1 to neighboring files...", so no, because C is not a neighbor to A.

Case for: p. 146, 5 & 5.1: "To work out the dice to add for a supporting file: Calculate its claims as if it were fighting the target base in the position of the friendly base it is supporting.", so yes, because you work it out as if C was a neighbor to A.

It would appear that the rule on p.146 takes precedence, but wanted to run it by folks.

The Shove effect benefits the neighbouring file.  The overlap is treated as if it was fighting the target base "in the position" of the file it is supporting - so yes it does benefit from the Shove (or Shatter) effect.  Seems clear to me.

Richard

" The overlap is treated as if it was fighting the target base "in the position" of the file it is supporting"

So, to clarify, if file B has a general fighting in the front rank would file C benefit from that too?

Nope. The general only counts for the file he is actually with, the "as if" bit is referring to where the neighbouring file is taken to be which isn't the same thing.

Thanks. Though I take it that there is nothing stopping a general fighting in the front rank of the overlapping file C? Which appears to have the added advantage that he can't be killed, unless the UG as a whole breaks, as the overlap doesn't take casualties.

Quote from: AlecJH on August 13, 2021, 11:38:46 AM
Thanks. Though I take it that there is nothing stopping a general fighting in the front rank of the overlapping file C? Which appears to have the added advantage that he can't be killed, unless the UG as a whole breaks, as the overlap doesn't take casualties.

Correct - and I've seen it done quite a few times