Aramis is a Sub Sector Capitol that is a Hell World.
Since "Hell World" is a post-CT trade classification, I'm deliberately omitting it from my revamp of the Spinward Marches subsector to be closer to LBB S3.
According to the T5 survey parameters, a Hellworld requires:
- Size 3+
- Atmosphere 2, 4, 7, 9-C
- Hydrographics 0-2
By that standard, Aramis/Aramis definitely qualifies with a UWP of A6B0556-B as recorded in LBB S3, p28 ... if you're using all of the later T5 codes.
For a Size: 5 world, this is perfectly legal under LBB3.77 and LBB3.81, even before throwing in -4DM to Hydrographics because Atmosphere: A+. It's certainly an extreme case, but it is still within the bounds of straight up dice rolls possibility.
it isn't marked with Ho for an Inner Orbit Planet?
The Travellerwiki page for
Aramis (SM3310) is completely silent on any kind of solar orbit location for the planet, so I'm presuming that the mainworld is just a hostile environment in the habitable zone.
then discovering there were too many mistakes to actually be mistakes
I felt like I was losing my mind a little.
I figure that almost all of the transcription errors fall into the "off by 1" category that can easily result from things like missed keystrokes on a number pad.
The really fun one, of course, is the mess made of the Express Network through Lunion subsector, with the J5 error between Tenalphi and Strouden.
I'm personally convinced that what was supposed to happen here was to bring the Express Network from Caladbolg/Sword Worlds to Wardn/Lunion and then link to Tenalphi/Lunion and Adabicci/Lunion ... with no spinward/trailing link between Tenalphi and Strouden at all. This would have then meant that the Imperial connection through Biter/Sword Worlds was also a mistake ... and the route connection between Adabicci and Ianic are also obvious mistakes, so quite the Cluster Fudge going on there.
But the J5 Tenalphi <-> Strouden error is the most interesting, because ... in the old subsector hex location system used for LBB S3, you have:
- 0107 Wardn. (the period indicates an independent, non-Imperial world)
- 0206 Tenalphi
- 0707 Strouden
In order to incorrectly link Tenalphi to Strouden (to trailing), instead of to Wardn (to spinward), you just need to confuse a single digit for the hex location:
And depending on the font being used (which could have involved hand written notes for all I know) it can sometimes be very easy to confuse a 1 vs 7 depending on how it is written (and how tired/zombie brained) the person doing the data entry, typesetting and layout for publication is at multiple points during the production timeline. All it takes is a single transcription error confusing a 1 for a 7 (which is only an "off by 2" error on a number pad) and you've got the misprint we see in LBB S3 for the erroenous J5 link in the Lunion subsector.
Then there's the whole Biter/Sword Worlds vs Wardn/Lunion connection issue, where both worlds have type B starports, but only Wardn/Lunion has an IISS base in the system, which is just what you'd want for a link in the network chain between Lunion and Five Sisters susbsectors along the border ... as opposed to going through Biter/Sword Worlds which is a system controlled and held by a foreign (and not always friendly) polity, the Sword Worlds Confederation.
So it looks like there were (to my mind, anyway) multiple compounding little errors layering on top of each other that produced the mistakes in the Express Routes through Lunion subsector (at least 3, depending on how you want to count them) that resulted in such a "car crash" when published.
So yeah, mistakes upon mistakes until you feel like you're losing your mind a little ... right there with you.
![Zany face :zany_face: 🤪](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f92a.png)