Re: [Epic] Net Epic: First Fire & Command Units

From: Tony Christney <acc_at_...>
Date: Thu, 20 Feb 1997 15:01:35 -0800

>From: Spatula <shupes_at_...>
>Date: Thu, 13 Feb 1997 10:44:21 -0500
>To: space-marine_at_...
>Subject: Re: [Epic] Net Epic: First Fire & Command Units
>Sender: owner-space-marine_at_...
>Precedence: bulk
>Reply-To: space-marine_at_...
>X-UIDL: f98c476f9b05b028896355c6acb731b8
>Status: U
>
>> From: "nethol" <nethol_at_...>
>>
>> As the rules go you cannot shoot at a command unit unless it is not the
>> closest unit to you.
>
> Closest unit of the same size class to you (infnatry/vehciles,
>super-heavy, titan). SHVs cannot screen infantry commanders.
>
>> This rule sometimes creates very illogical situations
>> where the weapon you fire is incapable of damaging the closer units. A
>> command unit walking besides a SHV or strolling between troops dug-in in
>> fortifications, in spite of being the most (perhaps only) eligible unit
>> within LOS, is safe from infantry fire. This is especially frustrating in
>> cases like 2 tech-marines and 3 shadow swords "protect" each other.
>>
>> How about modifying the rule to read as something like:
>> "A command unit cannot be shot at if there are closer targets to the
>> shooting unit that are damagable by the shooting weapon".
>
> No need.
>
> I would prose the addendum to the current rules that if
>all closer units of the proper size are in cover and the commander
>is not, you can shoot at the command unit in question. frex,
>your IG tac detachment is facing a long fang unit in a building
>and ragner blackmane is slightly further away, out in the open.
>The detachment should be able to shoot at Ragner (who they actually
>have a chance of hitting).
>
>Scott
>shupes_at_...
>
>
I agree with this, in fact that is the way we play. If someone is dumb
enough to put his command unit in the open while the regular troops are
in cover...let's just say it only will happen once.

Tony Christney
acc_at_...
Received on Thu Feb 20 1997 - 23:01:35 UTC

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