Starports
Thomas RUX
(18 Aug 2020 19:59 UTC)
|
Re: [TML] Starports
Alex Goodwin
(19 Aug 2020 15:11 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(19 Aug 2020 17:02 UTC)
|
Re: [TML] Starports
Kelly St. Clair
(19 Aug 2020 17:32 UTC)
|
Re: [TML] Starports
Alex Goodwin
(19 Aug 2020 17:55 UTC)
|
Re: [TML] Starports
Thomas RUX
(20 Aug 2020 22:46 UTC)
|
Re: [TML] Starports
Alex Goodwin
(21 Aug 2020 10:10 UTC)
|
Re: [TML] Starports
Thomas RUX
(21 Aug 2020 14:29 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(21 Aug 2020 16:25 UTC)
|
Re: [TML] Starports
Rupert Boleyn
(21 Aug 2020 18:44 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(22 Aug 2020 02:24 UTC)
|
Re: [TML] Starports
Rupert Boleyn
(22 Aug 2020 02:53 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(22 Aug 2020 06:36 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(22 Aug 2020 14:50 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(22 Aug 2020 14:18 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(22 Aug 2020 16:00 UTC)
|
Re: [TML] Starports
Phil Pugliese
(22 Aug 2020 21:01 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(23 Aug 2020 03:14 UTC)
|
Re: [TML] Starports
Phil Pugliese
(23 Aug 2020 16:27 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(23 Aug 2020 18:21 UTC)
|
Re: [TML] Starports
Phil Pugliese
(23 Aug 2020 23:20 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(25 Aug 2020 00:24 UTC)
|
Re: [TML] Starports
Phil Pugliese
(24 Aug 2020 00:14 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(24 Aug 2020 22:33 UTC)
|
Re: [TML] Starports
Rupert Boleyn
(25 Aug 2020 01:52 UTC)
|
Re: [TML] Starports
Phil Pugliese
(25 Aug 2020 03:10 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(25 Aug 2020 10:17 UTC)
|
Re: [TML] Starports
Phil Pugliese
(25 Aug 2020 02:53 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(25 Aug 2020 10:38 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(25 Aug 2020 18:41 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(25 Aug 2020 18:50 UTC)
|
Re: [TML] Starports
Phil Pugliese
(26 Aug 2020 11:22 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(26 Aug 2020 12:32 UTC)
|
Re: [TML] Starports
Phil Pugliese
(26 Aug 2020 17:48 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(26 Aug 2020 18:08 UTC)
|
Re: [TML] Starports
Phil Pugliese
(26 Aug 2020 20:09 UTC)
|
Re: [TML] Starports
Alex Goodwin
(22 Aug 2020 09:26 UTC)
|
Re: [TML] Starports Thomas RUX (22 Aug 2020 15:35 UTC)
|
Re: [TML] Starports
Alex Goodwin
(22 Aug 2020 16:12 UTC)
|
Re: [TML] Starports
Thomas RUX
(22 Aug 2020 21:32 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(23 Aug 2020 03:33 UTC)
|
Re: [TML] Starports
Phil Pugliese
(23 Aug 2020 16:35 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(23 Aug 2020 18:28 UTC)
|
Re: [TML] Starports
Alex Goodwin
(23 Aug 2020 05:20 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(23 Aug 2020 09:27 UTC)
|
Re: [TML] Starports
Alex Goodwin
(23 Aug 2020 09:56 UTC)
|
Re: [TML] Starports
Thomas RUX
(28 Aug 2020 16:08 UTC)
|
Re: [TML] Starports
Timothy Collinson
(28 Aug 2020 16:53 UTC)
|
Interstellar Wars Timelines (was Starports)
Alex Goodwin
(28 Aug 2020 17:05 UTC)
|
Re: [TML] Interstellar Wars Timelines (was Starports)
Thomas RUX
(29 Aug 2020 02:54 UTC)
|
Re: [TML] Interstellar Wars Timelines (was Starports)
Kenneth Barns
(29 Aug 2020 23:41 UTC)
|
Re: [TML] Starports
Thomas RUX
(26 Aug 2020 16:17 UTC)
|
Re: [TML] Starports
Alex Goodwin
(26 Aug 2020 18:05 UTC)
|
Re: [TML] Starports
Thomas RUX
(26 Aug 2020 18:57 UTC)
|
Re: [TML] Starports
hemdian
(19 Aug 2020 19:10 UTC)
|
Re: [TML] Starports
Rupert Boleyn
(19 Aug 2020 19:42 UTC)
|
Re: [TML] Starports
Phil Pugliese
(19 Aug 2020 20:16 UTC)
|
Re: [TML] Starports
Thomas RUX
(19 Aug 2020 20:51 UTC)
|
Re: [TML] Starports
Jeff Zeitlin
(19 Aug 2020 21:26 UTC)
|
Re: [TML] Starports
Thomas Jones-Low
(19 Aug 2020 21:44 UTC)
|
Re: [TML] Starports
kaladorn@xxxxxx
(19 Aug 2020 22:13 UTC)
|
Re: [TML] Starports
Phil Pugliese
(19 Aug 2020 22:22 UTC)
|
Re: [TML] Starports
Thomas RUX
(20 Aug 2020 02:31 UTC)
|
Re: [TML] Starports
Phil Pugliese
(20 Aug 2020 04:22 UTC)
|
Morning from Roy, WA Alex, > On 08/22/2020 2:25 AM Alex Goodwin <xxxxxx@multitel.com.au> wrote: > > > On 22/8/20 12:28 am, Thomas RUX wrote: > > <snip> > > Regardless of the distance that Badass-Moustache conducted the scan of a system the act of gathering, examining, and adding the information to the navigational data base is doing a survey. > > > > Unfortunately, I checked out MgT CRB 2e World and Universe Creation a while back which resulted in my not being able to follow the overview of how the scan was conducted. I did go back and start to review the chapter and I ran into a problem with gas giants. On PDF p. 225 is this portion of text: > > > > "Gas giants are relatively common. As indicated on the system contents table, roll 10+ for a gas giant not to be present in the system. If one is present, mark the system hex in accordance with the world format." > > > > I'm not able figure out what page "the system contents table" is on. > > > > MgT CRB 2e p. 225 has the same list of ports as CT LBB 3 does and I would use the port code of X at the interstellar range. Once Das Boote dropped into the system the scanners would still be collecting data and IIRC Badass-Moustache still reviewed the data. If the data did not indicate the presence of a landing beacon or the crew did not land on any planets the starport code would be X. If the merry band landed and marked the coordinates or left a beacon then the code would be E. > > > > Tom Rux > > ----- > > Tom, > > I think I see where we talked past each other. I was connoting "survey" > as "full up, all singing, all dancing, even most hazards to navigation" > system mapping", rather than "casing the joint, to any extent" that you > seemed to. I agree that we view the level of detail that the term "survey" covers differently. Das Boote's sensors are receiving every bit of information about the target system within in design specification. The ship's computer is using software to interpret the gathered information and saving it for immediate and future review. During the immediate review the information that is most important is there any place to refuel, repair, and do maintenance. This is, in my opinion, a survey even though a majority of the information gathered is ignored. > > I was using the survey rules from The Great Rift Book 4 - Deep Space > Exploration Handbook, pp 3-5. Someone else mentioned using MgT's The Great Rift Book 4 and I picked up a PDF copy of the Great Rift. Unfortunately, I have not gotten around to checking out the books yet. I have taken a look at the pages cited in The Great Rift Book 4 Deep Space Exploration Handbook. Page 3 breaks down phases of exploration. I may not fully agree with the phases, but I will adhere to them when following up. > As for not being able to find a "system contents table" in the MGT2 > core, you're not alone. What a relief to know that I have not simply overlooked the table. Thank you for the information. > > On reflection, I'd still argue for a ? starport code until definitive > data comes in either way. Frinstance, casing Sol from Prometheus c 2126 > in the PA-verse - going up to Survey Index 10 (or 11, that matter) would > let an interstellar-range snooper rumble the A-class port(s) around > Terra (ntm the traffic). By contrast, a downport-only setup (E, D, > lower-end C) could not be positively confirmed from extrasystem and > would remain ?. I agree that some place holder should be used to note that the target system has, if there is an indication of jump drive use, an unclassified type of port. I can get behind using a question mark "?". If there is no indication of jump drive use then by MgT Core Rule Book the designation code is X. In CT, MT, and TNE also have expanded/enhanced system generation systems that cover spaceports in addition to starports. Per the Traveller back story the Vilani were active at Bernard's Star. Scanning the Sol system would not have identified any starports since there where no jump drives being used. There where spaceports on the ground and in orbit. Under MgT rules, which does not appear to have spaceports, the code in my opinion would be "X". Thank you for the clarification and discussion. Tom Rux