Re: [NetEpic ML] Pinning..

From: peter ramos <ramospeter_at_...>
Date: Tue, 19 Dec 2000 08:21:21 -0500

Hi!

I beleive that under the description of warp jumps in the mech listing it
states that the jump engines do not work if any mass greater than the unit
with the carrying the jump device is too close. This description was not
carried over to the infantry with warp jump devices but the prinicipal was
the same. Therefore no slann unit (not even the titan) can use its warp jump
engines if engaged in close combat. Note the the unit needs to be PINNED for
it not to work, since it is an issue of mass. You cannot for example try to
put an infantry stand near a knight class model and expect it not to warp
jump, the mass in that case it too small.

The rule simple put: "pinned units cannot warp jump".

Peter


>From: Karlsen Rune <rune.karlsen_at_...>
>Reply-To: netepic_at_egroups.com
>To: "'netepic_at_egroups.com'" <netepic_at_egroups.com>
>Subject: [NetEpic ML] Pinning..
>Date: Tue, 19 Dec 2000 09:15:09 +0100
>
>Hi all!
>
>Nils and I recently played a game in which a stuation which caused some
>arguing arose. He pinned some
>of my Necron Assaults (which had yet to move) with 2 infantry stands and a
>rhino. Now, i realise they
>would be pinned according to the rules, but they do have warp capability.
>Why can't they simply escape
>by warping? This seems very logical to me, just push a button and off you
>go. Also, the movement of
>all units are considered to be simultaneous, so it's not like they're
>standing idly by, waiting to be pinned.
>If they had to walk towards the enemy, i concede that they would be pinned,
>but a unit with warp capability
>shouldn't be able to be pinned imho. To my mind, this simply isnt logical.
>If anybody could explain the logic
>behind this rule, id be grateful :)
>
>Rune

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Received on Tue Dec 19 2000 - 13:21:21 UTC

This archive was generated by hypermail 2.3.0 : Tue Oct 22 2019 - 10:59:13 UTC