[DS2] Close Assault question and other questions

2 posts ยท Nov 14 2000 to Nov 15 2000

From: Brian Bell <bkb@b...>

Date: Tue, 14 Nov 2000 08:46:59 -0500

Subject: RE: [DS2] Close Assault question and other questions

Interesting!

I have not seen this option (different set of actions for different elements
as described on p. 18) used except where elements are unable to fire, so it
becomes part of the unit doing fire and move and part of the unit just moving.

I suppose that this could be read two different ways.
In re-reading the combat section, Vehicle combat is
refered to element by element. Infantry combat is always refers to a unit. So
you could read it: 1) Vehicle elements may choose different actions as on p.
18, but Infantry units must act as a whole (as much as possible. Many
specialist teams (elements) described on p. 13 may not conduct ranged combat).
2) Different elements of ANY unit may perform different actions as described
on p. 18 (including close assault).

The second option however, it does lead to some interesting situations:

If a single element close-assaults a unit, that element
attacking must make the same reaction test (RT) regardless to whether his is
out numbered or not (i.e. same check if one element is attacking 6 elements or
6 elements are attacking 1 element. In the same way the defender makes the
same confidence test (CT) regardless if it is one element attacking or 20.

Each element in the same unit making a seperate close assault on a unit
(increases chance the defending unit will retreat).

A unit will often end up out of unit integrety after a close assault.

Here are some additional questions:

1) Close Assault is described as a combat action, but it includes a move. The
rules state that it must be done BEFORE a move. Can a unit that has performed
a close assault move after the close assault (not including a followthrough
action)? We have always played that a Close Assault takes both the move and
combat action of a unit; but we could have been playing wrong.

2) If some of an armor unit is moving then firing and the other is firing then
moving, would this be 2, 3, or 4 phases for the unit. It could makes a
difference if elements are caught by opprotunity fire. Example: An armor unit
consists of 2 AFVs with fixed mounted weapons (call it Type A) and 3 AFVs with
full turrets (call it Type B). The player decideds to have the Type A units
fire then move (only way for Type A to fire) and the Type B units to move then
fire. Enemy unit X can call opprotunity fire on the unit as it moves. What is
the proper sequence for the first unit: i) Type A fires while Type B moves;
then Type B fires while Type A moves. (2 phases) If this is is used, op fire
can only be called on Type A or Type B. ii) Type A fires then moves; then it
fires; Type B moves; then fires (4 phases) Using this option, op fire can only
be called on either Type A or Type B. iii) Type A fires; then both Type A and
Type B move; then Type B fires. (3 phases) Using this option, op fire would be
called on both Type A and Type B.

3) Since most people move one element at a time when moving miniatures, is
opportunity fire called on an element as it moves or on the unit? I.e. Player
A has 5 AFVs in a unit and player B has 5 AFVs in a unit. Player A moves one
element and player B calls for op fire. Is only the first element in danger of
op fire? Does each element that then crosses become open to op fire? Is the
unit of player A brought in to unit integrety then op fire is applied? What if
player B waits unit the 2nd element is being moved? Is the first element
brought back into unit integrety?

-----
Brian Bell bkb@beol.net
http://www.ftsr.org/ds2/
-----

> -----Original Message-----

> But on page 34 close assaults are described as combat actions; "One

From: Noel Weer <noel.weer@v...>

Date: Tue, 14 Nov 2000 21:16:49 -0600

Subject: Re: [DS2] Close Assault question and other questions

> "Bell, Brian K" wrote:

It is, isn't it?

> I have not seen this option (different set of actions

The most common use of this I have seen is in instances where the leader
element calls for an artillery strike while the other elements execute direct
fire.

> I suppose that this could be read two different ways.

I generally support this interpretation. It makes a lot of sense as I read
back through things.

> The second option however, it does lead to some

Makes sense, as is you have that situation if 5 attack 4, etc...

> Each element in the same unit making a seperate close

True, to a certain extent. Wouldn't any elements within the unit choosing to
close assault have go simultaneously? At a minimum you could argue that there
wasn't enough "time" in a turn to charge in echelon.

> A unit will often end up out of unit integrety after a close assault.

Too true. particularly aggravated if only 1 or two elements charge.

> Here are some additional questions:

We have played the same way. I do not think it is wrong. Following a close
assault even a victorious unit is probably too disorganized to
perform any useful actions (except a follow-thru).

> 2) If some of an armor unit is moving then firing and the

This seems less complicated. The rule states "When opportunity fire is
declared, the opposing player must pause in moving his elements while the
player who wishes to fire at them does so and resolves all subsequent
effects."
At any time that a player declares opportunity fire in the process -
however that process is being carried out by the moving player -
everything stops. The moving player must be prepared for this, but it is upon
the firing player to time his declaration for the greatest effect, as the
opportunity presents itself.

> 3) Since most people move one element at a time when

The unit integrity question is pretty good. My gut says that integrity is
checked at the end of the activation and not during it.

As to the first part, once opportunity fire is declared all moving elements
freeze and only those elements in LOS of the firing unit are available to be
targeted. Again, it is up to the declaring player to time it to his benefit,
not the moving player.

> -----