RE: [Epic] Transport units
<On putting transport detachments on seperate orders from the
detachment they carry>
>Putting one detachment on march orders and the 2nd detachment on
>overwatch is a great idea, but bear in mind that a unit (except orcs)
>has to pay 5cm in movement to load and an additional 5cm movement to
>disembark. The transporting detachement also must pay the cost.
>The 5cm deduction from their movement does not allow the unit to move
>5cm to the transporting detachment.
This is true. It works best for orks (which is why I first concieved
of it); other units would have to begin loaded on the transport in
order to take advantage of it (i.e. they could do it on the first
turn).
My original conception was not putting the transports on march orders
actually. I was thinking of loading the artillery on battlefortresses
which would advance up in support of a more rapidly advancing force
of mechanized infantry.
>If you wanted the 2nd detachment
>to start the game loaded in the 1st detachment, you would either have
>to deduct 5cm movement from both detachments initially for their 1st
>turn movement, or start them in reserves. If in reserves, they would
>not be able to move onto the table until your reserve movement
>results allowed 2 detachments to move in, not just one.
Not true actually. On page 15 of the battles book, under Reserves
it says:
"A detachment which is transporting another detachment (such as
a transport flyers or a war engine for example) is treated as a
single detachment for purposes of rolling for reserves."
When the transport detachment enters the game, the detachment it
carries comes automatically. It never rolls seperately and is
not counted as a seperate detachment. So, for example, if you
have a detachment of battlewagons transporting a detachment of
nobz off table, and no other reserves, the battlewagons will
automatically come in next turn (since they are the only reserve
unit), bring the nobz with them.
David
Received on Tue Jul 22 1997 - 00:32:05 UTC
This archive was generated by hypermail 2.3.0
: Tue Oct 22 2019 - 13:09:39 UTC