RE: [SG] Close assault interpretation questions

er, I'm sorry but the rules state quite plainly that you have to be in
range
for the combat role.." this movement distance.. MUST be sufficient to
allow
at least some figures of the assaulting unit to come into contact....".
Page 41, third paragraph of INITIATING CLOSE ASSAULT......eg for regular
foot max 12", Fast PA max 24", terrain restrictions notwithstanding....

This is one of those rules discussions just CRYING out for incluson in a
FAQ?

Cheers,

Owen

> -----Original Message-----
> From: owner-gzg-l@lists.CSUA.Berkeley.EDU
> [mailto:owner-gzg-l@lists.CSUA.Berkeley.EDU]On Behalf Of Derk
Groeneveld
> Sent: Tuesday, 13 March 2001 6:03 PM
> To: 'gzg-l@csua.berkeley.edu'
> Subject: RE: [SG] Close assault interpretation questions
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On Tue, 13 Mar 2001, Robertson, Brendan wrote:
>
> > If you launch a close assault from more than 1 combat move away, any
> > casualties are deserved for trying to manipulate the defenders
morale
> > unrealistically.
>
> This is something we discussed last weekend, as well. It struck me
there
> is nothing within the rules, that we could find, to stop a player to
> declaring a close assault from half a table away, to break an already
> shaken defender.
>
> Now, the umpire should clobber this munchkin senseless, of course...
But I
> couldn't find anything that said the target HAS to be reachable?
>
> > To overrun, you really need to reach the position to start with
> (otherwise
> > it would be a failed assault however you look at it).
>
> Yes, but according to the rules as we read them, the overrun happens
> immediately after the test, i.e. before the attacker moved at all.
> Suddenly overrun became an underrun ;) Anyway, the suggestions I've
> yesterday clear up the problem, I think.
>
> Cheers,
>
>    Derk
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: Made with pgp4pine
>
> iD8DBQE6rdRJJXH58oo6ncURAhfKAKCS80iBPOTGPJHMOts0c/04HLVRhQCgmlOa
> 7rRnEZBYoQ53NWy7jskCbCc=
> =48Uz
> -----END PGP SIGNATURE-----
>
>