Last time I said I was going to improve the Traveller Subsector Mapper I had written to show communication lines. Well, now it does. But I’m still not happy. My unhappiness just moved on.
=> Last time | Traveller Subsector Mapper
I’m now looking at some sort of algorithm that will “simplify” the network. Take a look at the sample subsector. I’d like this algorithm to delete the connection between Bemaat and Atcevein and the connection between Esgeed and Maxereis. Those I think should be obvious. Less obvious would be to delete the connection between Diare and Esgeed and between Atcevein and Esgeed.
I’m still struggling, however. What should the exact elimination rules be?
For every code amber and code red system, eliminate all but one communications route. The one and only communications route from such a system should go to the system with the best starport, the closest one, with the most people, and the richest, with no code amber or red.
This would make the following changes:
Or I could try something else.
Every system will keep the shortest communications routes it has.
Hm, I don’t think this is going to work.
#RPG #Traveller
(Please contact me if you want to remove your comment.)
⁂
I’m just going to say I so wished your Traveller mapping apps (and similar technology) had been available way back in the day when I first scored my Trav LLBs. You know - instead of plinking around with the TRS-80.
– Brian 2010-03-14 16:06 UTC
=> Brian
Thanks! Isn’t it ironic that I bought Traveller and started writing the mapping app because of the Mongoose Traveller review on 2d6 Feet in a Random Direction? 😄
=> I bought Traveller | 2d6 Feet in a Random Direction
– Alex Schroeder 2010-03-15 15:23 UTC
=> Alex Schroeder This content has been proxied by September (3851b).Proxy Information
text/gemini