Comments on 2017-07-11 Traveller vs. Traveller

There should be a space lane between 0601 and 0701 by the 1977 rules (A-B J-1 is 1+ to have a space lane). Also 0504-0505 and 0508-0607, hmm and a bunch more...

– Frank Filz 2017-07-13 07:31 UTC


Indeed! A bug!

– Alex Schroeder 2017-07-13 09:25 UTC


New code produces:

1619343301-ct4

– Alex Schroeder 2017-07-13 09:35 UTC


Highlighting jump-1 routes:

1619343301-ct5

Not sure about the colour scheme. And the legend at the bottom needs fixing.

– Alex Schroeder 2017-07-13 10:59 UTC


Nice, I like the red to highlight the J-1. When I did my subsectors, I ended up not rolling for the J-3 and J-4 routes. I also didn’t bother with a J-2 route that was already connected by J-1 (for example 0604-0804 above, there’s already an implied J-2 route as 0604-0705-0804). Similarly you could remove the 0305-0604 J-3 route (unless there isn’t a J-2 between 0305-0505 and that blue line is actually JUST a J-4 route 0305-0705...).

– Frank Filz 2017-07-13 16:28 UTC


Hm... Isn’t that a bit like the minimum spanning tree optimisation? As Ian Borchardt said on G+:

One problem with your optimised paths is that you are assuming that space == time, which isn’t the case with Traveller jumps, because any jump takes two weeks, regardless of distance. [IIRC]

Which means it’s not cheaper (time wise) for a starship to call in at an intermediate port. So given a choice between A-B-A and A-A most people will still choose A-A by preference because it gets there in half the time. It has a greater efficiency.

I responded with the following:

As for trade route optimisation: one might say that the trade routes indicate the most popular trade routes and thus two jump-2 segments will be more popular than a single jump-4 segment because there will be more ships that can handle it, even if that makes the route take twice the time. Well, that was my argument when I realised that too many routes just made for an ugly map.

So basically the jump-2 route 0604-0804 says that ships can and will make this jump directly – unlike the jump 0604-0703, which is also a jump-2 but somehow the dice have decided that it’s not profitable enough to do. It’s up to the referee to explain the difference. At least, that’s Ian’s argument.

For myself, I’m still undecided. All I can say is that it looks busy and messy and I don’t like it too much.

As for distance, I guess from a player perspective, at the beginning of a typical campaign all we care about are jump-1 and jump-2 routes. Perhaps I should just use a third colour for jump-2 routes.

– Alex 2017-07-13 16:52 UTC


Support for sectors, click to zoom. Note how I used a third color for jump-2 routes.

Click to zoom!

– Alex 2017-07-13 18:03 UTC


D’oh. I just noticed that my generator never generated any gas giants. Fixed!

This also means that all the random seeds will now generate different maps. Nooooo!

– Alex 2017-07-13 18:33 UTC


As for picking a subsector capital, Ian Borchardt says:

Definitely an A class spaceport (and it will have an attached Imperial naval and scout base). It probably should be a Rich world (Atmosphere 6-8, Population 6-8), and I’d assign it a Government Type of 8. The TL should be amongst the highest in the subsector (and a minimum of 12).

And regarding trade routes, he says:

This is the approach I would take.

First generate the main routes.

(1) Connect all Starport A within Jump 2 of each other.
(2a) Connect all Starport B within Jump 2 of a Starport A.
(2b) Connect all Starport B within Jump 1 or each other.
(2c) Connect an unconnected Starport B to another Starport B within Jump 2.

If a connection in step 2 connects Starport A to the sector capital then upgrade it to a main route.

Next comes the feeder routes.

(3a) Connect Starport C to a single Starport A within 1 jump.
(3b) If not connected, connect Starport C to a single Starport B within Jump 1.
(3c) If not connected, connect Starport C to a single Starport A within Jump 2.
(3d) If not connected, connect Starport C to a single Starport A within Jump 2.
(4a) Connect Starport D to a single Starport A within 1 Jump. (optional)
(5) Class E starports are never connected by a trade route.

If in need of direction, assume the shortest path to the subsector capital.

This defines the regular services (for various definitions of regular). Everything else relies on tramp freighters.

[In your example map the small disconnected group of systems to coreward might have better trade connections to coreward than it does with the subsector it is technically a part of. Or it may be a different polity. And yes, I cheated with the rosette of class A and C starports to rimward, because of a fondness for benzene rings...]

– Alex Schroeder 2017-07-13 22:31 UTC


Please make sure you contribute only your own work, or work licensed under the GNU Free Documentation License. See Info for text formatting rules. You can edit this page if you need to fix typos. You can subscribe to updates by email without leaving a comment.

To save this page you must answer this question:

Please say HELLO.