• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

Classic Traveller Sensor Rules

OK, we seem to be going back and forth on the computer hit thing. I had been convinced that it wasn't necessary, caused too much extra work and wasn't really worth it. Your rules dude. If you want to use the computer hit/drop rule, that is great, glad I could help. I will probably go back to using it too. I really like the sensor damage rule, that really adds to the roll-playing aspect of space combat, which is always a good thing.
 
OK, we seem to be going back and forth on the computer hit thing. I had been convinced that it wasn't necessary, caused too much extra work and wasn't really worth it. Your rules dude. If you want to use the computer hit/drop rule, that is great, glad I could help. I will probably go back to using it too. I really like the sensor damage rule, that really adds to the roll-playing aspect of space combat, which is always a good thing.
 
Originally posted by MaineCoon:
*clamors for a consolidated Word doc or PDF*
Click to expand...
It's a-coming. This will probably be my next project....might take a little while, though. That last one on chargen took me 16 hours to write!

I'll post when the sensor rules are ready in a pdf (and then I've got to do the UGM).
 
Originally posted by MaineCoon:
*clamors for a consolidated Word doc or PDF*
Click to expand...
It's a-coming. This will probably be my next project....might take a little while, though. That last one on chargen took me 16 hours to write!

I'll post when the sensor rules are ready in a pdf (and then I've got to do the UGM).
 
Originally posted by WJP:

The sensor suite includes multiple sensors in both Passive and Active arrays.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Suite Range
Class I One-half Light Second (150,000 km or 15 Range Bands)
Class II One Light Second (300,000 km or 30 Range Bands)
Class III One and One-half Light Seconds (450,000 km or 45 Range Bands)
Class IV Two Light Seconds (600,000 km or 60 Range Bands)</pre>
Click to expand...
DESIGNER'S NOTE: I have not considered yet how much these sensors suites will cost. Your input on this is welcome.

[/quote]Recently, I've been pondering sensors as well, and have seen a couple of posts from a couple of people which seem to be going somewhere interesting. And I'd like to try to contribute.

I'd suggest that CT's computer volume is really the sensor suite volume, and that half of its cost is the sensors' cost.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Class MCr Volume
1 2 1
2 9 2
3 18 3
4 30 4
5 45 5
6 55 7
7 80 9
8 110 11
9 140 13</pre>[/QUOTE]To scan: roll range* or better.

Scanning DMs (these are a lot like yours):
+ Model number

-4 if using PEMS
-1 if attempting a lock

+1 Military craft

-2 Target less than 10 tons
-1 Target less than 100 tons
+1 Target 1000+ tons
+2 Target 10,000+ tons

...etc...


* With your system, perhaps each range would be range bands/10?

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Range Target Number
<10 bands 0
10-19 bands 1
20-29 bands 2
30-39 bands 3
40-49 bands 4
50-59 bands 5
60-69 bands 6
70-79 bands 7
80-89 bands 8
90-99 bands 9
etc</pre>[/QUOTE]My range scale is a bit too jumpy for your purposes:

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">5 500 m
6 5 km
7 50 km
8 500 km
9 5000 km
10 50 kkm 0.2 L-S
11 250 kkm 0.8 L-S
12 500 kkm 1.5 L-S
13 2.5 mkm 8.0 L-S
14 5.0 mkm
15 50.0 mkm
16 1 AU
17 Inner system
18 System
19 Companion-system
20 Interstellar
...and so on...</pre>[/QUOTE]Of course, AEMS stops around range 17 or 18...
 
Originally posted by WJP:

The sensor suite includes multiple sensors in both Passive and Active arrays.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Suite Range
Class I One-half Light Second (150,000 km or 15 Range Bands)
Class II One Light Second (300,000 km or 30 Range Bands)
Class III One and One-half Light Seconds (450,000 km or 45 Range Bands)
Class IV Two Light Seconds (600,000 km or 60 Range Bands)</pre>
Click to expand...
DESIGNER'S NOTE: I have not considered yet how much these sensors suites will cost. Your input on this is welcome.

[/quote]Recently, I've been pondering sensors as well, and have seen a couple of posts from a couple of people which seem to be going somewhere interesting. And I'd like to try to contribute.

I'd suggest that CT's computer volume is really the sensor suite volume, and that half of its cost is the sensors' cost.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Class MCr Volume
1 2 1
2 9 2
3 18 3
4 30 4
5 45 5
6 55 7
7 80 9
8 110 11
9 140 13</pre>[/QUOTE]To scan: roll range* or better.

Scanning DMs (these are a lot like yours):
+ Model number

-4 if using PEMS
-1 if attempting a lock

+1 Military craft

-2 Target less than 10 tons
-1 Target less than 100 tons
+1 Target 1000+ tons
+2 Target 10,000+ tons

...etc...


* With your system, perhaps each range would be range bands/10?

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Range Target Number
<10 bands 0
10-19 bands 1
20-29 bands 2
30-39 bands 3
40-49 bands 4
50-59 bands 5
60-69 bands 6
70-79 bands 7
80-89 bands 8
90-99 bands 9
etc</pre>[/QUOTE]My range scale is a bit too jumpy for your purposes:

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">5 500 m
6 5 km
7 50 km
8 500 km
9 5000 km
10 50 kkm 0.2 L-S
11 250 kkm 0.8 L-S
12 500 kkm 1.5 L-S
13 2.5 mkm 8.0 L-S
14 5.0 mkm
15 50.0 mkm
16 1 AU
17 Inner system
18 System
19 Companion-system
20 Interstellar
...and so on...</pre>[/QUOTE]Of course, AEMS stops around range 17 or 18...
 
Originally posted by robject:
I'd suggest that CT's computer volume is really the sensor suite volume, and that half of its cost is the sensors' cost.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Class MCr Volume
1 2 1
2 9 2
3 18 3
4 30 4
5 45 5
6 55 7
7 80 9
8 110 11
9 140 13</pre>
Click to expand...
[/quote]I think that's brilliant. I like. I think that should be part of these rules.


To scan: roll range* or better.
Click to expand...
I want to get away from the "count hexes every time" condition in my original rules. I like the wide "range bands" you see in personal Traveller combat--not as much time spent figuring range that way.

If I ever finish these rules, I'll have to adjust.

I abandoned, or put this project on hold, as my campaign went dirtside for a long period of time. Heck, we're still dirtside (but I think we'll be back in space in a few months--it's hard to tell only playing once a month).

I've defaulted to DGP's CT Sensor Rules until I get the spark to put some more time into these.

I like your contribution, though.

Keep posting. If you've got more to add.

I like what you've done with the place.
 
Originally posted by robject:
I'd suggest that CT's computer volume is really the sensor suite volume, and that half of its cost is the sensors' cost.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">Class MCr Volume
1 2 1
2 9 2
3 18 3
4 30 4
5 45 5
6 55 7
7 80 9
8 110 11
9 140 13</pre>
Click to expand...
[/quote]I think that's brilliant. I like. I think that should be part of these rules.


To scan: roll range* or better.
Click to expand...
I want to get away from the "count hexes every time" condition in my original rules. I like the wide "range bands" you see in personal Traveller combat--not as much time spent figuring range that way.

If I ever finish these rules, I'll have to adjust.

I abandoned, or put this project on hold, as my campaign went dirtside for a long period of time. Heck, we're still dirtside (but I think we'll be back in space in a few months--it's hard to tell only playing once a month).

I've defaulted to DGP's CT Sensor Rules until I get the spark to put some more time into these.

I like your contribution, though.

Keep posting. If you've got more to add.

I like what you've done with the place.
 
I understand completely. I thought your range determination was brilliant, actually (using computer rating as the short-range marker is genius).

Perhaps "range" then can still work in broad swaths?

Short : 4+
Medium : 8+
Long : 12+
Extreme : 16+
 
I understand completely. I thought your range determination was brilliant, actually (using computer rating as the short-range marker is genius).

Perhaps "range" then can still work in broad swaths?

Short : 4+
Medium : 8+
Long : 12+
Extreme : 16+
 
Originally posted by robject:
I understand completely. I thought your range determination was brilliant, actually (using computer rating as the short-range marker is genius).
Click to expand...
Thanks, brother. Between us, I think we're writing a pretty good rule here.

Perhaps "range" then can still work in broad swaths?

Short : 4+
Medium : 8+
Long : 12+
Extreme : 16+
Click to expand...
I had mixed up with Sensor Thread this was. I wrote another one (just before this one) where range must be counted out each time.

Actually, as you say above, I kinda like the range "bands" for the ship being determined by the ship's systems.

I'll repost that part of the rules here:

Short range for the ship's sensor package is determined by the model number of the ship's computer. Model 1 or 1bis indicates that the sensor's short range is the single hex surrounding the ship. A Model 4 computer would indicate 1-4 hexes out from the ship as the sensor's short range area. Write the sensor's short range under the 4+ in the ship's sensor listing.

Medium range for the ship's sensor arrays is determined by the ship's powerplant letter code. More powerful powerplants tend to push better sensor units, and this is represented by wider ranges in the crucial Medium range category.

Consider the ship's powerplant letter code in hexidecimal notation (where A=10, D=13, W=30, etc.) and indicate this as the Medium range limit on the ship's sensor listing under 6+.

Long range for the ship's sensor package has already been determined when the sensor suite was selected. Indicate this range under the 8+ in the ship's sensor listing.

Very Long range is any range past the Long range upper limit.

Here are example sensor listings for some of the ships described in Book 2:

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">100T Type S Scout
PP-A
Suite: Class IV C-1bis

2+ 4+ 6+ 8+
0 1 2-10 11-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">200T Type A Free Trader
PP-A
Suite: Class I C-1

2+ 4+ 6+ 8+
0 1 2-10 11-15</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type R Sub Merch
PP-C
Suite: Class I C-1

2+ 4+ 6+ 8+
0 1 2-12 13-15</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">200T Type Y Yacht
PP-A
Suite: Class II C-1

2+ 4+ 6+ 8+
0 1 2-10 11-30</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">800T Type C Merc Cruiser
PP-M
Suite: Class IV C-5

2+ 4+ 6+ 8+
0 1-5 6-21 22-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type T Patrol Cruiser
PP-H
Suite: Class IV C-3

2+ 4+ 6+ 8+
0 1-3 4-17 18-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type L Lab Ship
PP-F
Suite: Class III C-2

2+ 4+ 6+ 8+
0 1-2 3-15 16-45</pre>[/QUOTE]Do you not agree that that's a decent way to go?

Or, are you thinking we need one-size-fits-all range bands, just like personal combat?
 
Originally posted by robject:
I understand completely. I thought your range determination was brilliant, actually (using computer rating as the short-range marker is genius).
Click to expand...
Thanks, brother. Between us, I think we're writing a pretty good rule here.

Perhaps "range" then can still work in broad swaths?

Short : 4+
Medium : 8+
Long : 12+
Extreme : 16+
Click to expand...
I had mixed up with Sensor Thread this was. I wrote another one (just before this one) where range must be counted out each time.

Actually, as you say above, I kinda like the range "bands" for the ship being determined by the ship's systems.

I'll repost that part of the rules here:

Short range for the ship's sensor package is determined by the model number of the ship's computer. Model 1 or 1bis indicates that the sensor's short range is the single hex surrounding the ship. A Model 4 computer would indicate 1-4 hexes out from the ship as the sensor's short range area. Write the sensor's short range under the 4+ in the ship's sensor listing.

Medium range for the ship's sensor arrays is determined by the ship's powerplant letter code. More powerful powerplants tend to push better sensor units, and this is represented by wider ranges in the crucial Medium range category.

Consider the ship's powerplant letter code in hexidecimal notation (where A=10, D=13, W=30, etc.) and indicate this as the Medium range limit on the ship's sensor listing under 6+.

Long range for the ship's sensor package has already been determined when the sensor suite was selected. Indicate this range under the 8+ in the ship's sensor listing.

Very Long range is any range past the Long range upper limit.

Here are example sensor listings for some of the ships described in Book 2:

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">100T Type S Scout
PP-A
Suite: Class IV C-1bis

2+ 4+ 6+ 8+
0 1 2-10 11-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">200T Type A Free Trader
PP-A
Suite: Class I C-1

2+ 4+ 6+ 8+
0 1 2-10 11-15</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type R Sub Merch
PP-C
Suite: Class I C-1

2+ 4+ 6+ 8+
0 1 2-12 13-15</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">200T Type Y Yacht
PP-A
Suite: Class II C-1

2+ 4+ 6+ 8+
0 1 2-10 11-30</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">800T Type C Merc Cruiser
PP-M
Suite: Class IV C-5

2+ 4+ 6+ 8+
0 1-5 6-21 22-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type T Patrol Cruiser
PP-H
Suite: Class IV C-3

2+ 4+ 6+ 8+
0 1-3 4-17 18-60</pre>[/QUOTE]</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">400T Type L Lab Ship
PP-F
Suite: Class III C-2

2+ 4+ 6+ 8+
0 1-2 3-15 16-45</pre>[/QUOTE]Do you not agree that that's a decent way to go?

Or, are you thinking we need one-size-fits-all range bands, just like personal combat?
 
Originally posted by Supplement Four:
Medium range for the ship's sensor arrays is determined by the ship's powerplant letter code. More powerful powerplants tend to push better sensor units, and this is represented by wider ranges in the crucial Medium range category.

Consider the ship's powerplant letter code in hexidecimal notation (where A=10, D=13, W=30, etc.) and indicate this as the Medium range limit on the ship's sensor listing under 6+.
Click to expand...
Something comes to mind here...how to reconcile this with ships that have High Guard statistics?

Is there a way to convert High Guard ships to Book 2 PP codes?
 
Originally posted by Supplement Four:
Medium range for the ship's sensor arrays is determined by the ship's powerplant letter code. More powerful powerplants tend to push better sensor units, and this is represented by wider ranges in the crucial Medium range category.

Consider the ship's powerplant letter code in hexidecimal notation (where A=10, D=13, W=30, etc.) and indicate this as the Medium range limit on the ship's sensor listing under 6+.
Click to expand...
Something comes to mind here...how to reconcile this with ships that have High Guard statistics?

Is there a way to convert High Guard ships to Book 2 PP codes?
 
By the bye, several people on COTI and other places have suggested that the CT computer was better suited as a ship's sensor suite; so really I'm just borrowing from other folks as I can.

PP Codes are strange things. There's a correspondence to Energy Points, but how do EPs relate to your signal levels?

OK, well, let's see then. A Scout ship may be expected to usually have one laser, and under unusual circumstances may have 3. That plus the M-drive A suggests the Power Plant-A is a 2 EP drive, more or less.

Likewise, a Far Trader may have up to 6 lasers, but is more likely to have (say) 3 or 4. That plus the J-drive B suggests the Power Plant-B is something like a 4 EP drive, again, more or less.

To scale up a bit, the 1000-ton Oberlindes J3 Cargo Carrier has a J-drive and Power Plant-Q, plus 30 beam lasers. In High Guard, the power plant would be expected to generate 30 EPs... which fits the laser loadout nicely.

This means a rough approximation of EPs can be found by finding the breakpoints in the Drive Potential Table.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">A 2
B 4
C 6
D 8
E 10
F 12
G 14
H 16
J 18
K 20
L 22
M 24
N 26
P 28
Q 30
R 32
S 34
T 36
U 38
V 40
W 50
X 60
Y 80
Z 120</pre>[/QUOTE]So, if we can approximate EPs from the DPT, then we ought to be able to go the other way 'round.

The formula from EPs to your Signal Code may be something like this?

Signal = (EP/2) + 9

I'd simplify it to

Signal = (EP/2) + 10
 
By the bye, several people on COTI and other places have suggested that the CT computer was better suited as a ship's sensor suite; so really I'm just borrowing from other folks as I can.

PP Codes are strange things. There's a correspondence to Energy Points, but how do EPs relate to your signal levels?

OK, well, let's see then. A Scout ship may be expected to usually have one laser, and under unusual circumstances may have 3. That plus the M-drive A suggests the Power Plant-A is a 2 EP drive, more or less.

Likewise, a Far Trader may have up to 6 lasers, but is more likely to have (say) 3 or 4. That plus the J-drive B suggests the Power Plant-B is something like a 4 EP drive, again, more or less.

To scale up a bit, the 1000-ton Oberlindes J3 Cargo Carrier has a J-drive and Power Plant-Q, plus 30 beam lasers. In High Guard, the power plant would be expected to generate 30 EPs... which fits the laser loadout nicely.

This means a rough approximation of EPs can be found by finding the breakpoints in the Drive Potential Table.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">A 2
B 4
C 6
D 8
E 10
F 12
G 14
H 16
J 18
K 20
L 22
M 24
N 26
P 28
Q 30
R 32
S 34
T 36
U 38
V 40
W 50
X 60
Y 80
Z 120</pre>[/QUOTE]So, if we can approximate EPs from the DPT, then we ought to be able to go the other way 'round.

The formula from EPs to your Signal Code may be something like this?

Signal = (EP/2) + 9

I'd simplify it to

Signal = (EP/2) + 10
 
You must log in or register to reply here.

Similar threads

W
T4 merchant design challenge
Replies
9
Views
879
warwizard
W
robject
REST API for Starship Component creation
2
Replies
24
Views
2K
robject
robject
Baroun Tardis
T5 House Rule: Robots, Droids and Bots
Replies
3
Views
379
kilemall
kilemall
Jetrock
MGT Only: 150-ton Wind-class SX Scout/Courier
Replies
6
Views
817
Jetrock
Jetrock
Spinward Flow
CT Only: Spinward Yacht
2 3
Replies
56
Views
2K
Spinward Flow
Spinward Flow
Back
Top