RE: [NetEpic ML] Close Combat

From: <jyrki.saari_at_...>
Date: Wed, 7 Mar 2001 11:34:14 +0200

 
-----Original Message-----
From: ext Eivind Borgeteien [mailto:eivind.borgeteien_at_...]
Sent: 07. March 2001 11:13
To: netepic_at_yahoogroups.com
Subject: [NetEpic ML] Close Combat


The rules concerning vehicles with troops in close combat is as follows:
 
  

BM__Toc497575985Vehicles with Troops<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />


When the enemy charges a vehicle that is transporting troops, the
transported can fight in Close Combat providing that:

1. They have Charge orders (this should be explicit; in Net
Epic the vehicle and the troops can be given different orders),

2. The vehicle is unmoved (if it has completed its move, there
won't be any time for the troops to disembark).

 

My fellow gamers think that this rule allows the transported troops to get
out of their transports and move away from the combat at hand, as it doesn't
say anything about the transported troops being pinned by the attacking
unit. This must be wrong! Right?

JS: Right. The rule says they can move out TO FIGHT IN CC. Not that they can
run away.

 

Could we please have a sentence here saying that transported troops are
pinned if the transporter is being charged?

JS: That should be in order, if conclusions like that can be drawn.
Something like: "The troops may only move out to fight the enemy that
charged the transport in CC. They may not move away from the CC". Also, I
think the sentence "When the enemy charges a vehicle that is transporting
troops, the transported can fight in Close Combat..." should be changed to
"When the enemy charges a vehicle that is transporting troops, the
transported troops can disembark to fight in Close Combat...". Otherwise
some wiseguy probably claims that the troops fought from inside the vehicle
and can not be fired at in the AFPh.

Eivind



Jyrki Saari

-There is no such thing as free lunch because eating takes time and time is
money.
Received on Wed Mar 07 2001 - 09:34:14 UTC

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