Re: [NetEpic ML] Re: Pinning..

From: peter ramos <ramospeter_at_...>
Date: Tue, 19 Dec 2000 13:31:01 -0500

Hi!

Hmm..this brings the question of whether we should keep it this way. I think
the pinning restriction should be applied since otherwise I can visualize a
whole range of cheesy ploys to keep you from warp jumping.

Opinions?

Peter

>From: "Hellreich" <hellreich_at_...>
>Reply-To: netepic_at_egroups.com
>To: <netepic_at_egroups.com>
>Subject: Re: [NetEpic ML] Re: Pinning..
>Date: Tue, 19 Dec 2000 12:47:19 -0800
>
>OOOo time out Peter yes the Mech can have its Warp Jump messed up by the
>cheesy one lone stand. The fact is ANY extra mass around one tring to jump
>would through it off. But, this dos not stop the mech or Titan from just
>walking away from that type of model that is not in its pinning class. And
>this works fine if infantry or cheap tanks try to pin a Mech or Titan it
>can
>just walk away. But infantry would be pinned and have to fight. It is
>pretty
>clear in the rules how the Necron work. "" Necron also have built in warp
>jump generators that allow them to move in EXACTLY the same way as Mechs."
>----- Original Message -----
>From: <primarch_at_...>
>To: <netepic_at_egroups.com>
>Sent: Tuesday, December 19, 2000 7:58 AM
>Subject: [NetEpic ML] Re: Pinning..
>
>
> > Hi!
> >
> > My original response seems to have gotten lost somewhere. According
> > to the mech fluff warp jump engines dont work if too much mass is
> > closeby since the machine is attuned to the bearer of it. This means
> > anyone engaged in close combat cannot use the warp generator because
> > the generator doesn't have enough power, can't calculate fast enough
> > to compensate (or any similar logic) when the unit is grappled in
> > close combat.
> >
> > Note however "mass" is relative to size. The unit needs to be PINNED
> > for its warp generators not to work. Therefore a infantry stand
> > cannot engage a mech so it cannot use its warp generator because it
> > cannot pin it. This eliminate cheesy tactics of charging a lone stand
> > that can't pin mechs so they can't warp jump.
> >
> > These decriptions were never added to the infantry (Necron)
> > decriptions, but apply to all units with jump generators (even
> > titans).
> >
> > So infantry pinning assault necron would cancel their ability to warp
> > jump, but infantry could not do the same to mechs, you would need a
> > knight for that. In case of a titan only another titan could cancel
> > its ability to warp jump.
> >
> > These are things to be edited in the newer version fo the books.
> >
> > Daniel, please keep this message in your archive for when we do get
> > to the slann.
> >
> > Peter
> >
> > --- In netepic_at_egroups.com, Karlsen Rune <rune.karlsen_at_e...> wrote:
> > > 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
> >
> >
> >
> > To unsubscribe send e-mail to: netepic-unsubscribe_at_egroups.com
> >
> >
>
>_______________________________________________
>Why pay for something you could get for free?
>NetZero provides FREE Internet Access and Email
>http://www.netzero.net/download/index.html

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

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