Prev: RE: Phalon and Sa'Vasku encounters on starmaps? Next: FT: EW

Re: Sensor Rules

From: Sean Bayan Schoonmaker <schoon@a...>
Date: Sat, 8 Apr 2000 06:57:37 -0700
Subject: Re: Sensor Rules

>Results:
>
>1 HIT : Bogey detected. +2 range bands to fire on.
>2 HIT : Soft Lock. +1 range bands to fire on
>3 HIT : Hard lock. Fire as normal
>4 HIT+ : Hard Lock and movement compensated. Fire as -1 range bands
>(minimum 1)

I think that the possible results are a bit extreme. A destroyer with
standard sensors might not get even bogey info until the enemy is quite
close. Likewise, adjusting an entire rangeband is potentially a bit
much.
There are, after all essentially only three bands to begin with. I think
that "half bands" might work better and allow for more varied results.

>Datalinks
>
>Sensor pools can be combined and allocated at the discretion of the
Flagship.
>1/2 of the sensor pool is sacrifised to the Flag sensor pool (allowing
point
>defence and independant fire for the ships part of the Flag sensor
pool). It
>then allows the flag to detect enemy vessles from the closest ship that
is
>part
>of the pool. It also allows all ships as part of the Flag sensor pool
to
>use the
>detection level of the detected ships (Ie, if the flag detects a
cruiser
>with a
>Hard lock, all ships in the pool treat the cruiser as a hard lock).

Hmmm, Starfire. I've also looked a mimicking this system. There needs to
be
a limitation on the distance between datalinked ships, otherwise the
system
becomes too powerful.

As a Traveller simulation, those sensor rules are fine, but I'd hesitate
to
adopt them as a general set for FT; a little too involved.

Schoon

Prev: RE: Phalon and Sa'Vasku encounters on starmaps? Next: FT: EW