Prev: Re: "Average" FT ship size? Next: Professionalism and Quality in FT terms (long)

Re: Simultaneous fire [was UK/US in balkans (as the UN)]

From: colin.plummer@t...
Date: Thu, 20 Jan 2000 10:54:11 +0000
Subject: Re: Simultaneous fire [was UK/US in balkans (as the UN)]

*unlurk*

Quoting Michael T Miserendino (Wed, Jan 19, 2000 at 03:04:00PM -0500)

[simultaneous fire]

> 1. Recording damage now becomes a pain.  You need to indicate that
damage 
> has been taken but will not take affect until the end of the combat
between 
> the two squadrons.  It seems this would also slow game play.	This is
a 
> potential spot for errors - e.g. A player might forget which damaged
occured 
> this turn from previous damage, and not fire a weapon system.

I don't agree, you merely need to assume a system of crosses for damage.
When the damage occurs, you make one stroke of the cross (somewhere next
to
the system is good) - at the end of the turn turn all single strokes
into
crosses.  If a system gets repaired, circle the cross.	You can now tell
at
a glance whether the system may be used (it has an uncircled cross next
to
it).

If you don't like that solution, since all fire is simultaneous - you
could
all write down what your firing will be, much like the procedure for
movement orders.

All it takes is a little thought in how you do things.

*lurk*

--
Colin Plummer

Prev: Re: "Average" FT ship size? Next: Professionalism and Quality in FT terms (long)