Sunday, November 21, 2021

Aslan Bases in Dark Nebula

Following the inconclusive end of the Solomani Rim War… Solomani attention has since turned to other frontier areas, including the Aslan territories. Fortunately for the Aslan, the encounters have primarily been between the Solomani and either the Yerlyaruiwo or the Khaukheairl, both clans strong enough to hold their own with the Solomani (CT Aslan 3).

A heavily militarized section of the Aslan/Solomani frontier in Dark Nebula.

With this passage in mind, I reviewed the Dark Nebula sector data for evidence of Yerlyaruiwo or Khaukheairl military forces on the Confederation border. I wasn’t shocked to find scant support: Tlaukhu worlds aren’t exactly rare, but with ten different power blocs, finding a cluster of worlds associated with any one bloc—even the two most powerful blocs—is fairly unusual.

But as I started to dig in, I realized that the total number of Aslan bases seemed fairly low, particularly when compared to the Solomani Confederation. Even knowing that the Aslan have notorious difficulty coordinating inter-clan efforts, and knowing that most clan navies are constructed to fight other clans rather than interstellar states, for such a militaristic race to not mount some kind of defense in the face of Human aggression seemed rather odd.

But the number of Aslan bases in Dark Nebula didn’t just seem low in light of hostilities with the Solomani. The number of bases seemed low compared to a normal Aslan sector.

Generating Aslan Bases

The CT Aslan module (1984) describes two different types of naval bases found in the Hierate: Tlaukhu bases, built and occupied by members of the Twenty-Nine, and clan bases, used by all other types of clans. These bases are determined during world generation much like Imperial navy or scout bases. But in addition to considering starport type, Aslan bases also consider government type.

Dark Nebula bases were first detailed in the CT module Atlas of the Imperium (1984). That partial sector data was then used as the basis for the sector data in the MT supplement Solomani and Aslan (1991). And that data was the basis for the current data on Traveller Map.

I had long assumed that the Aslan bases in Atlas of the Imperium had been determined using CT Aslan world gen. In order to check that assumption, we can compare the actual number of bases in Dark Nebula against the expected number of bases that would be produced from Aslan world gen. But first, we need to break those worlds out by starport and, instead of using Government type, I’ll substitute the T5 allegiance codes, which provide similar information.

There are 234 Aslan Hierate worlds in Dark Nebula:

Hierate Worlds In Dark Nebula
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	11	14	12	2	6	0
On-World Clan (AsWc)	6	5	8	2	6	0
Multi-World Clan (AsMw)	6	20	12	5	14	0
Tlaukhu Clan (AsTX)	6	8	11	3	7	0
Vassal Clan (AsVc)	2	7	11	8	6	0
Tlaukhu Vassal (AsTv)	3	6	11	5	11	0
Total	34	60	65	25	50	0

From here we can calculate the total number of bases we would expect to have for each combination of starport and allegiance code.

Tlaukhu Bases

The Tlaukhu clans maintain larger, more powerful, and more advanced navies compared to other clans. Their bases can be found on worlds directly controlled by Tlaukhu members, their vassals, and split-control worlds. The following table details the percentage chance for having a Tlaukhu base at different Hierate systems:

Frequency Of *Tlaukhu* Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	58.33%	41.66%	27.77%	16.66%	–	–
On-World Clan (AsWc)	–	–	–	–	–	–
Multi-World Clan (AsMw)	–	–	–	–	–	–
Tlaukhu Clan (AsTX)	83.33%	72.22%	58.33%	41.66%	–	41.66%
Vassal Clan (AsVc)	–	–	–	–	–	–
Tlaukhu Vassal (AsTv)	41.66%	27.77%	16.66%	8.33%	–	–

Note that this table details the potential presence of one or more bases in a single system. In a split control world divided up by six different Tlaukhu clans, each clan could have its own in-system base. Similarly, a world directly controlled by a Tlaukhu clan or its vassal might, at least theoretically, host multiple Tlaukhu bases if an allied clan from the same power bloc were present in-system.

Multiplying the number of worlds of each category by the corresponding frequency, we can determine the expected number of systems with Tlaukhu bases in Dark Nebula:

Expected *Tlaukhu* Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	6	6	3	0	0	0
On-World Clan (AsWc)	0	0	0	0	0	0
Multi-World Clan (AsMw)	0	0	0	0	0	0
Tlaukhu Clan (AsTX)	5	6	6	1	0	0
Vassal Clan (AsVc)	0	0	0	0	0	0
Tlaukhu Vassal (AsTv)	1	2	2	0	0	0
Total	12	14	11	1	0	0

Using CT Aslan world generation, we would expect 38 systems with Tlaukhu bases, which is surprisingly close to the 39 systems with naval bases we would expect to produce using the default world gen system from The Traveller Book.

But let’s take a look at the actual numbers from Dark Nebula:

Actual *Tlaukhu* Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	3	0	0	0	0	0
On-World Clan (AsWc)	0	0	0	0	0	0
Multi-World Clan (AsMw)	0	1	0	0	0	0
Tlaukhu Clan (AsTX)	1	2	0	0	0	0
Vassal Clan (AsVc)	0	0	0	0	0	0
Tlaukhu Vassal (AsTv)	0	0	0	0	0	0
Total	4	3	0	0	0	0

Less than 20% of the expected number of systems in Dark Nebula have Tlaukhu bases. No wonder the Solomani have been able to snatch up so many border worlds!

Clan Bases

Clan bases are naval bases built by any clan other than a member of the Tlaukhu. Generally, clan navies are smaller and less advanced than Tlaukhu forces. The following table lists the chances for one or more clan bases to be present in different Hierate systems:

Frequency Of Clan Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	72.22%	58.33%	41.66%	27.77%	–	–
On-World Clan (AsWc)	72.22%	58.33%	41.66%	27.77%	–	27.77%
Multi-World Clan (AsMw)	83.33%	72.22%	58.33%	41.66%	–	41.66%
Tlaukhu Clan (AsTX)	–	–	–	–	–	–
Vassal Clan (AsVc)	72.22%	58.33%	41.66%	27.77%	–	–
Tlaukhu Vassal (AsTv)	58.33%	41.66%	27.77%	16.66%	–	–

Multiplying these frequencies by the corresponding number of worlds lets us calculate the expected number of systems with clan bases:

Expected Clan Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	8	8	5	1	0	0
On-World Clan (AsWc)	4	3	3	1	0	0
Multi-World Clan (AsMw)	5	14	7	2	0	0
Tlaukhu Clan (AsTX)	0	0	0	0	0	0
Vassal Clan (AsVc)	1	4	5	2	0	0
Tlaukhu Vassal (AsTv)	2	2	3	1	0	0
Total	20	31	23	7	0	0

Using CT Aslan world generation, we would expect to have 81 systems with one or more clan bases in Dark Nebula. By way of comparison, using The Traveller Book world gen we would expect to generate 62 systems with scout bases.

But yet again, we find that the actual number of systems in Dark Nebula with clan bases is far less than expected:

Actual Clan Bases
Allegiance	Starport Type
Allegiance	A	B	C	D	E	X
Split Control (AsSc)	2	1	0	0	0	0
On-World Clan (AsWc)	2	0	0	0	0	0
Multi-World Clan (AsMw)	0	1	0	0	0	0
Tlaukhu Clan (AsTX)	0	0	0	0	0	0
Vassal Clan (AsVc)	1	0	0	0	0	0
Tlaukhu Vassal (AsTv)	0	1	1	0	0	0
Total	5	3	1	0	0	0

This is only a little more than 11% of what we would expect from CT Aslan world generation.

Note that Atlas of the Imperium lists two additional worlds in Dark Nebula as having clan bases: Troi' (DARK 1923 E787A78-9) and Fiyhiyha' (DARK 0938 B43248A-B). Neither system has a base in the current Traveller Map data. I think this was an intentional decision for Troi', as worlds with Class E starports normally cannot have bases. I suspect that Fiyhiyha' was simply a mistake, so I recommend reinstating the base there.

Summary

Here’s a summary of our analysis of bases in Dark Nebula:

Summary Of Hierate Bases In Dark Nebula
Allegiance		Starport Type						Total
Allegiance		A	B	C	D	E	X	Total
Tlaukhu	Expected	12	14	11	1	0	0	38
	Actual	4	3	0	0	0	0	7
Clan	Expected	20	31	23	7	0	0	81
	Actual	5	3	1	0	0	0	9

I honestly don’t have a great recommendation for what to do here in part because I don’t understand what happened. And I was surprised not to find any past discussions on the Traveller Mailing List or on the Citizens of the Imperium board.

We see similar patterns in other Aslan sectors from Atlas of the Imperium. There the percentage of systems with either Tlaukhu or clan bases are Hlakhoi 7%, Ealiyasiyw 9%, Staihaia'yo 10%, and Iwahfuah 12%. Keep in mind that the Atlas of the Imperium provided the basis for all subsequent versions of sector data, official and unofficial. And the reviewers of the T5 Second Survey project generally considered the Atlas the gold standard source.

Which begs the question, how did Atlas of the Imperium determine the presence of Aslan bases? The Atlas was published the same year as the Aslan alien module, so the developers might or might not have had access to the Aslan world gen sequence. But even if they did, that system uses Government type to determine the presence of bases. And the Atlas did not generate Government data.

A low number of Aslan bases in Dark Nebula might have been a simple mistake—a faulty random formula, for example. But although MT Solomani and Aslan uses the same world gen sequence as CT, the authors of that supplement did not take the opportunity to correct the number of Aslan bases in their Dark Nebula data.

But I’m not convinced the low number was an intentional decision, either: It doesn’t make a lot of sense given steady Solomani encroachment on Aslan space.

A couple ideas might partially rationalize the current data. As discussed above, each Aslan clan maintains its own naval bases. Overlord and vassal clans can have separate bases, partners in a power bloc might have separate bases, and certainly rivals on a split control world would have separate bases. So many of the “missing” bases might actually be right in front of us, stacked up in single systems. Kusyu alone, for example, might have dozens of different Tlaukhu bases.

Further, many clan bases might be present but simply not be shown on Traveller Map. Maps of Imperial space, for example, do not show every single planetary or colonial naval base, even though they must exist. As CT Spinward Marches notes, “any world with a tech level of 7 or 8 and a population of 6+ will probably have a base for the local (planetary) naval forces (such forces will be capable of interplanetary, though not interstellar, flight). Any world with a tech level of 9+ and a population of 6+ will probably have a base for local naval forces (which are capable of interstellar flight, where necessary)” (40).

Although I think the low number of Tlaukhu bases might be a problem. I’m reluctant to recommend adding a bunch of new bases to the map willy-nilly. Has anyone else ever considered these questions before?

Copyright Information

The Traveller game in all forms is owned by Far Future Enterprises. Copyright © 1977 – 2021 Far Future Enterprises. Traveller is a registered trademark of Far Future Enterprises. Far Future permits web sites and fanzines for this game, provided it contains this notice, that Far Future is notified, and subject to a withdrawal of permission on 90 days notice. The contents of this site are for personal, non-commercial use only. Any use of Far Future Enterprises’s copyrighted material or trademarks anywhere on this web site and its files should not be viewed as a challenge to those copyrights or trademarks. In addition, any program/articles/file on this site cannot be republished or distributed without the consent of the author who contributed it.

Materials produced by Digest Group Publications (DGP) are copyright © Roger Sanger. Any use of Digest Group Publications’ copyrighted material or trademarks anywhere on this Web site and its files should not be viewed as a challenge to those copyrights. Usage is intended to follow the guidelines announced by Roger Sanger on the Traveller Mailing List for preserving the overall Traveller milieu.

Tuesday, November 16, 2021

Revised Dark Nebula High Population Data

The Steisua Cluster is an important astrographic feature in Hrorehe and Kou subsectors containing five different high population worlds.

As I reviewed the current Dark Nebula data on Traveller Map I realized that the population of Kusyu had been increased from 4 billion in Classic Traveller to 70 billion. I initially assumed this reflected a change made in MegaTraveller or Mongoose Traveller but after checking those sources, no dice.

In fact, the population of Kusyu has proven much more consistent than the location of Kusyu over various editions:

CT Aslan (1984): 4.6 billion
MT Referee’s Companion (1988): 4.6 billion
Travellers’ Digest 17 (1989): 4.631 billion*
MT Solomani and Aslan (1991): 4.631 billion*
GURPS Traveller: Alien Races 2 (1999): 4.6 billion
Mongoose Traveller Aslan (2009): 4.6 billion
Mongoose Traveller Pirates of Drinax(2017): 4.6 billion

* Note that the subsector data contradicts the text, listing Kusyu with Pop 9 and Pop multiplier 7.

Agent of the Imperium lists Kusyu as Pop 9, while Traveller⁵ Book 3 lists Kusyu as both Pop 9 (p 287) and Pop A (p 242).

Now curious, I looked at other high population worlds in the sector. “High population” is a trade classification assigned to worlds with population codes of either 9 (billions) or A (tens of billions). The location and names of all high population worlds in Dark Nebula are identified in the Classic Traveller supplement Atlas of the Imperium (1984). The MegaTraveller supplement Solomani and Aslan then provided full sector data for all Dark Nebula worlds and is generally consistent with the Atlas.

Further review of the Traveller Map data showed that the Aslan worlds of Troi’ (DARK 1923), Eakhoi (DARK 2123), Oiirl (DARK 2430), Hai Ei (DARK 0836), and Steisua (DARK 1135) also had their population levels increased from 9 to A.

Who Cares?

Changing the population levels of just six worlds from 9 to A is actually a much bigger deal than it seems on first blush, profoundly impacting the overall population of the entire sector. And in Traveller, population is inextricably tied to economic clout. If we only focus on the high population worlds in the original Solomani and Aslan data, Dark Nebula sector contains 50 billion Ormine, 162 billion humans, 138 billion non-aligned Aslan, and 256 billion Hierate Aslan. Following the adjustment of just six worlds to Pop A, the overall population of Hierate Aslan in the sector soars to 547 billion Aslan—over double.

I suspect that the changes were made by a well-intentioned T5SS reviewer looking at the overall population of Dark Nebula compared to surrounding sectors: the Solomani Rim, for example, has a total population of 1,660 billion; Magyar, 552 billion; and Dark Nebula, before adjustment, 650 billion. Given that Dark Nebula contains the homeworld of one of the six major races, 650 billion might seem a little low.

But I actually think that goosing the sector population to 936 billion was probably the wrong way to go here. Statistically, the original population of Dark Nebula falls well within expectations. Using 2D - 2 to determine population levels, with 487 total worlds, Dark Nebula would have on average of 14 pop A worlds. The original dataset had 13 pop A worlds, so fairly close.

We should also remember that the sector data for the Solomani Rim was intentionally massaged to reflect the setting description: a highly developed, industrial powerhouse. The Rim’s population and economic numbers have always been outliers by design.

A Case for Reversion

With this in mind, I’m not sure that transforming Dark Nebula into an economic powerhouse best reflects the established setting. In some ways, allowing the sector to lag economically and technologically seems more appropriate, given my understanding of the setting history. Consider: something has always been odd—and I think, intentionally so—about the layout of Dark Nebula sector. As many others have previously noted, the Aslan differ from all other major races in that their homeworld lies on the edge of Hierate space rather than in the center of their polity. When Aslan took to the stars they discovered that Humans had already settled the territories immediately trailing and coreward of Kusyu, forcing the Aslan to initially expand spinward and rimward.

During the Long Night, the Aslan amassed enough power and technology to challenge those neighboring Human systems. As described, the Border Wars were a slow-moving, incredibly complex series of low-level conflicts along the coreward and trailing border of the Hierate. Eventually, several treaties between various clans and Human powers established buffer zones around these border areas, culminating in the Peace of Ftahalr.

A quarter of Dark Nebula still falls into the Buffer Zone while another quarter, running along the trailing border was probably part of buffer zones recently absorbed by the Solomani Confederation. We know that Aslan allow captured worlds to regress technologically and that the various treaties were designed to limit outside interference within the buffers. Given this history, it’s not all that surprising that the border regions would have a notable lack of class A or B starports as well as significant technological lag—many worlds remain stuck at industrial tech levels even in 1105.

I’d also argue that keeping the Aslan Hierate worlds in Dark Nebula at somewhat lower population levels is not inconsistent with the known setting details. The Aslan are notable for their incessant hunger for acquisition and expansion of territory, and we know that the most powerful clans quickly laid claim to the best worlds around Kusyu, forcing the lesser clans to look farther and farther afield for new lands.

We also know that Aslan males have very different conceptions of value than Aslan females, whose thinking is much more in line with Humans. Aslan males place tremendous weight on cultural and historical value, unlike the much more pragmatic and unsentimental females, who calculate value in conventional economic terms. While a female Aslan might view a large stretch of arid, infertile land as a waste of clan resources, a male might treasure this same tract if it had been the site of an ancient battle, particularly one involving an ancestor. So it’s not hard for me to imagine that many clans would view the ancestral worlds of Dark Nebula as essentially one great historic district, to be preserved for cultural significance—with serious industrial production relegated to worlds deeper in the Hierate.

Further, I have to wonder about the economic viability of Hierate worlds with a Population level of A, or at least those with pre-stellar tech levels. As GURPS Traveller: Alien Races 2 explains, “If possible, Aslan cities sprawl sideways rather than towering upward, because each male wants his own patch of land, and will not settle for a patch of floor 30 stories up if there is any alternative” (23). Cramming Aslan populations into tightly-packed cities or even high tech arcologies is probably only a measure of last resort.

Further, split-clan control probably leads to ecological disaster for many high-population, habitable worlds: a classic example of the tragedy of the commons. In the absence of high tech solutions, individual clans likely struggle to coordinate responses to planet-wide ecological challenges caused by extreme population pressure.

And the unique dietary requirements of Aslan potentially impose serious limitations on the development of high-population Aslan worlds. Aslan are almost exclusively carnivorous and prefer fresh meat over synthetic substitutes. Meat production is inherently inefficient, and technology can only provide so much relief given Aslan insistence on “analog” dining. So a few pop A worlds could readily siphon off energy resources from across an entire subsector.

I am certain the Hierate contains plenty of high population, industrial hellholes where low status Aslan and unassimilated aliens toil in monstrous factories run by clan-controlled corporations. But given what we know about the Aslan I wonder if they might not expand to secondary worlds within a system before they started packing populations onto the mainworld? If I needed to establish a Hierate with more economic clout than currently shown in sector data, I would turn to the secondary worlds before I started converting too many worlds from Pop 9 to Pop A.

Recommendations

Putting all of this together, I think it makes sense to revert many of these changes in Dark Nebula, beginning with Kusyu. I really can’t see any compelling justification for increasing the population of the Aslan homeworld to 70 billion, and it contradicts almost every prior source.

Here are my full recommendations for reverting population levels:

Kusyu (1226) - Change UWP to A876976-E to revert population level back to 9 and PGB to 403, consistent with prior sources. Change Economic extension to (F8H+4) and Cultural extension to [9E4D].
Troi’ (1923) - Change UWP to E787978-8 to revert population level back to 9. Add Pr to remarks, change Importance to { -1 }, Economic extension to (C8A+1), and Cultural extension to [A859].
Eakhoi (2123) - Change UWP to C786976-A to revert population level back to 9. Add Pr to remarks, change Economic extension to (H8D+1) and Cultural extension to [9B4A].
Hai Ei (0836) - Change UWP to E665979-8 to revert population level back to 9. Add Pr to remarks, change Importance to { -1 }, Economic extension to (G8A+1) and Cultural extension to [B86A].

As a compromise, I would recommend retaining the populations of Oiirl (DARK 2430) and Steisua (DARK 1135) as A. This alone increases the overall population of Hierate Aslan in Dark Nebula to 355 billion.

Copyright Information

Tuesday, November 9, 2021

The Mystery of the Missing Dark Nebula Worlds

Sector data for Dark Nebula has been something of a muddle right from jump. As discussed before, the lovely map for the Dark Nebula board game was never utilized by the RPG. The CT Aslan alien module gives at least three different locations for Kusyu, with every subsequent edition seemingly making a different choice. Hans Rancke-Madsen wrote a good history of Kusyu’s various locations, and for what it’s worth I completely agree with Hans’s argument that hex 1226—the location currently shown on Traveller Map—makes the most sense.

The CT supplement Atlas of the Imperium (1984) provides rudimentary details of the sector, including starport type and location of all systems, as well as the names of high population worlds. DGP provided detailed data for Kilrai’ subsector in Travellers’ Digest 17 (1989) and then the entire sector in Solomani and Aslan (1991). This DGP data has been the base for all sector data to follow but, as discussed earlier, the initial data files available on the web for Dark Nebula were so replete with scanning errors that many worlds continue to pop up with erroneous names.

At first glance, the CT adventure compilation Alien Realms (1986) doesn’t appear to have any material set in Dark Nebula. One adventure is specifically set in Waroatahe sector, but the partial subsector data in Alien Realms doesn't line up with the later S&A dotmap of the Aslan Hierate. This was inadvertent: as Don McKinney explains in his Consolidated CT Errata, "The worlds (and map) in this adventure do NOT appear in the DGP dot map of this sector . . . because everyone forgot about it." A subsequent T5 Second Survey review overrode the DGP dotmap and added the Alien Realms worlds to Waroatahe.

A closer look at the J. Andrew Keith adventure “Interdiction Zone” from Alien Realms suggests that maybe the Waroatahe references weren't the only thing forgotten. The location of Kualakhtaea, the interdicted world at the heart of the adventure, is not given, but the background information names many worlds located in "Kyaeakha" subsector. None of these worlds or the subsector currently appear on Traveller Map.

However, some of the Aslan clans mentioned in "Interdiction Zone" are also mentioned in the Amber Zone adventure “Raid on Stataorlai,” from Journal of the Travelers' Aid Society #20 (1984), which is credited to Keith Douglass, one of the many pseudonyms used by … J. Andrew Keith.

“Raid on Stataorlai” is set in Kyaenkha subsector, which is canonically subsector E of Dark Nebula. Note that Kyaenkha is close enough to Kyaeakha to be a typo. Putting everything together, I suspect that J. Andrew Keith intended for these two adventures to be set in the same subsector, namely Kyaenkha subsector of Dark Nebula—and the reference to Kyaekha in Alien Realms was an error.

In any case DGP clearly didn't refer to Alien Realms when developing their dotmap of the Hierate. (I think the DGP material is generally great, but the dotmaps are notoriously unreliable, sometimes not even including stars mentioned in the same book they appear in.)

So ten J. Andrew Keith worlds from “Raid on Stataorlai,” and "Interdiction Zone” are not currently reflected in the Dark Nebula sector data. Could we find suitable homes in Kyaenkha subsector for them? Ideally we could find worlds in the existing data that fit the descriptions in everything but name, but even if we can only find approximate matches, I think it would make sense to override the DGP data to fit J. Andrew Keith’s adventures.

A couple of ground rules: first, any tweak cannot contradict information in Atlas of the Imperium, generally considered the gold standard for matters of canonicity. And second, we can’t override any worlds that have received a canonical treatment. These ground rules place only two worlds in Kyaenkha off-limits for this exercise. Hteoe (DARK 0117), is briefly described in TD 17 (and currently misspelled Hleoe in Traveller Map). And the high population world of Au'aiyyee is named in Atlas of the Imperium. So let’s see what we can do with the remainder:

Ftaikhao. As described in “Interdiction Zone,” this world is located in Kyaeakha subsector and outright owned by the Hweaolriya clan. Since we know that Hweaolriya is a multiworld clan, we’re looking for a world that has the allegiance code AsMw. Kuaeankha subsector has several candidates: Kheawyarl (DARK 0116 B79A36A-A), Aulyetyu (DARK 0214 E648446-6), Leftearl (DARK 0615 B200587-D), and Hwiysa (DARK 0619 E546387-7). As explained below, Leftearl may be the site of “Raid on Stataorlai,” so let’s remove that from contention. Kheawyarl fits the bill, so I propose renaming Kheawyarl “Ftaikhao” and changing the government type to 8.

Hakekhea. As described in “Interdiction Zone,” this “bleak” world is located in Kyaeakha subsector and outright owned by the Aeahekihiykhiy clan, the only world they own in the subsector. Further, “valuable mineral deposits [were] recently discovered” in the system. As with Ftaikhao, we’re looking for a world with the allegiance code AsMw, although it might be a secondary world. Hwiysa (DARK 0619 E546387-7), with a thin, tainted oxygen-nitrogen atmosphere isn’t quite bleak, at least by Traveller standards, but it’s close enough. I recommend renaming Hwiysa “Hakekhea.”

Ktiyrhaniy. As described in “Interdiction Zone,” this is another Kyaeakha subsector world outright owned by the Hweaolriya clan. Aulyetyu (DARK 0214 E648446-6) is the only unallocated world with the AsMw allegiance code, so I propose renaming Aulyetyu “Ktiyrhaniy.”

Kualakhtaea. As described in “Interdiction Zone,” this interdicted world has a UWP of X987673-1. There’s really nothing even close to a match in the subsector data, so we’re probably talking a secondary world controlled by the Aeahekihiykhiy. The mainworld could have any allegiance code, but either an on-world clan (AsWc) or a vassal clan (AsVc) with a small presence make the most sense. (A Tlaukhu or large multiworld clan in the system might horn in on Kualakhtaea, source of great wealth to the Aeahekihiykhiy.) The description of the world suggests a star favorable to support life, so the primary probably wouldn’t be a red giant, any supergiant, or have a white dwarf companion. Ayeiyfua (DARK 0311 E100643-8) is a nice, sleepy system controlled by an on-world clan and anchored by a G0 V M6 V. If Ayeiyfua is a gas giant moon in the outer system, Kualakhtaea could be a secondary world orbiting the G0 V star in the habitable zone.

Htealyahwa. As described in “Interdiction Zone,” this is a rich Kyaeakha subsector world controlled by the Ftauhakit clan in fief to the Hweaolriya. This suggests the allegiance code AsVc. Eweuas (DARK 0112 A585745-C) is a decent fit, so I recommend renaming Eweuas “Htealyahwa.” Note that two worlds with government type 6 are controlled by Eweuas: Tyakhyo (DARK 0115 D100369-A) and Etlaorla (DARK 0315 CDC5166-A). I recommend changing the Government code of Tyakhyo to 8 and of Etlaorla to 4 and removing ownership details from both.

Huuira'alr. As described in “Interdiction Zone,” this is a Kyaeakha subsector world partially owned by the Hweaolriya clan. This is, by definition, a split control world with the allegiance code AsSc. Only three split-control worlds are listed in the current subsector data: Hteoe (DARK 0117), Eatyurei (DARK 0120), and Au'aiyyee (DARK 0220). Both Hteoe and Au'aiyyee are off-limits, and I’m reserving Eatyurei for other purposes. So we would need to tweak something to make this fit. I recommend changing Ealalrye (DARK 0317 B410434-C), allegiance AsVc to Huuira'alr (DARK 0317 B410474-C), allegiance AsSc.

Kahkeheas. “Interdiction Zone” describes a Kyaeakha subsector world that is partially or wholly owned by the Tralyeaeawi clan. This would suggest any of the allegiances AsT3, AsTv, or AsSc. As there are no Tralyeaeawi bloc or available split-clan worlds, we need to find a suitable Tlaukhu vassal world. Sowei (DARK 0520 777547-B) seems like a decent fit, so I recommend renaming Sowei “Kahkeheas.”

Stataorlai. This planetoid belt is described in “Raid on Stataorlai” as having the UWP of C0007J8-8 and “located in 0605 of the Kyaenkha subsector of the Dark Nebula sector, controlled by the Eakhtawa clan.” This location corresponds to Leftearl (Dark Nebula 0615 B200587-D). There are no asteroid belt mainworlds in the subsector, much less one with a class C starport, so Stataorlai must obviously be a secondary world. As described, the Stataorlai system has three gas giants and a military base. Leftearl is controlled by a multiworld clan, had 2 gas giants, and no bases. There’s no indication in the adventure as to how many worlds are controlled by Eakhtawa, so the existing Leftearl allegiance could work if we assume this clan controls other worlds. We could increase the number of gas giants easily enough. There is no clan base shown in AotI, but let’s add one. Putting this all together, I suggest increasing the number of Leftearl gas giants to 3, assume the mainworld is a moon of the innermost gas giant and that the Stataorlai belt is a secondary world on the edge of the outer system. As the mainworld has a Population code of 5, less than Stataorlai’s Population of 7, let’s swap those around so that Leftearl has a revised UWP of B200787-D and the Stataorlai belt a UWP of G000568-8. This has several cascading effects: Leftearl’s remarks change to Na Pi Va Sa, Importance increases to 2, the economic extension changes to B65+1, and the cultural extension to 595D.

Syeaa'isiy. “Interdiction Zone” describes a Kyaeakha subsector world that is partially owned by the Hweaolriya clan. As we have no available split control (AsSc) allegiance worlds, I recommend tweaking Htiyhoai (DARK 0612 B636797-B), allegiance AsTv to Syeaa'isiy (DARK 0612 B636777-B), allegiance AsSc.

Waeoisya/Waeorsya. As described in “Raid on Stataorlai,” “Waeoisya” is a split control world located in Kyaeankha subsector and partially owned by the Hweaolriya clan. As described in “Interdiction Zone,” “Waeorsya” is a split control world located in Kyaeakha subsector and partially owned by Hweaolriya clan. So it’s pretty clear these worlds are one and the same. Only three split-control worlds are listed in the current subsector data and with Hteoe (DARK 0117), and Au'aiyyee (DARK 0220) off-limits, Eatyurei (DARK 0120) is the only candidate. In “Raid on Stataorlai,” Waeoisya is described as being a potential site of conflict between the Hweaolriya and Aeahekihiykhiy clans. Eatyurei is a low-population, split-control world controlled by owners out of Au'aiyyee, and in AotI was listed as having starport X. Sounds like a contested world to me. Given all this, I propose renaming Eatyurei “Waeorsya” and changing the Government code to 7, removing the ownership details.

Copyright Information

The illustration at the top of the blog is by William H. Keith and is from Alien Realms (1986).

Sunday, November 7, 2021

Traveller RPG Starship Miniatures

As I’ve mentioned before, although I enjoy painting miniatures and using them at the game table, I’m a dreadfully slow painter and really have only a few brief windows each year to devote to these projects.

As such, I already have a pretty large backlog of models on my workbench. Combined with the fact that I own a decent selection of painted fantasy figures, I’ve resisted the temptation to acquire any more.

I’m afraid that resistance was shattered this week with the launch of this Kickstarter:

I don’t currently have any starship miniatures and these are based on the work of the great Ian Stead, whose Patreon I already support.

But what really sold me? They’re adding an armed packet to the ship list:

At that point my Wisdom save was as good as failed. I’ve been curious about 3-D printing for a while and the costs to entry have steadily fallen over the last few years. So I guess it’s time to take the plunge…

Tuesday, November 2, 2021

Revised Dark Nebula Planetary Data

An artist’s rendition of the garden world of Satwor (DARK 2610 A867632-A) in the Akuusir Cluster. Source: Solomani Ministry of Information holopamphlet, “The Border Worlds of the Confederation” (5661).

In addition to tweaking stellar data, I also wanted to add Traveller⁵ trade classifications for climate and satellites, and potentially seed a few larger world sizes into my house sector data for Dark Nebula. I also found a few irregularities in the data currently available on Traveller Map, most likely the result of earlier passes from the T5 Second Survey (T5SS). Finally, I had a couple of random changes I wanted to add.

Mainworld Placement

By determining the mainworld’s orbit, we also establish the mainworld’s climate and whether the mainworld is tide-locked to the primary or not. Traveller⁵ assumes that mainworlds are generally found in or around the habitable zone orbit (HZ) of their primary. The specific orbit is determined randomly with a Flux roll. Accordingly, most worlds will orbit in the HZ and have a moderate climate range. A low Flux puts a mainworld in orbit HZ-1, with a Hot (Ho) or Tropic (Tr) trade classification; a high Flux puts a mainworld in orbit HZ+1, with a Cold (Co) or Tundra (Tu) classification.

The most common modifier is for class M main sequence stars: M0 V, M1 V, M2 V, or M3 V. The HZ for such stars is orbit 0 (about 0.2 AU), so worlds orbiting these stars cannot occupy one orbit in: the modifier pushes their orbits to the HZ (orbit 0), HZ+1 (orbit 1), or HZ+2 (orbit 2). A world orbiting in HZ+2 might qualify for the Frozen (Fr) code, often associated with worlds in the outer system.

After generating orbital placements for Dark Nebula, I then made a series of passes to massage the resulting data. I swapped the climate codes of several worlds with breathable atmospheres (4–9, E) with worlds with unbreathable atmospheres (0–3, A–C) to move more of the former into an HZ orbit and more of the latter out of an HZ orbit.

Planet or Satellite

Traveller⁵ determines whether a mainworld is a planet or the satellite of a gas giant or large terrestrial planet with another Flux roll. An important rule of thumb that I followed was to prevent worlds that orbit too close to the primary (orbits 0 or 1) from being satellites: this removed several satellites from the dataset, since M and K class main sequence stars are so common. I also moved several satellite codes from larger worlds (7+) to smaller worlds (4-).

Tide-Locking and Resonant Orbits

One inevitable consequence of applying Traveller⁵ world generation rules to sector data is that, because class K and M main sequence stars are so common, you end up with a LOT of mainworlds in orbits 0 or 1. By default, worlds in these orbits are considered tide-locked with the trade classification Twilight Zone (Tz).

As I noted in my post on Dark Nebula stellar data, there is an interesting debate going on right now about the habitability of such worlds, with strong arguments being made for and against. Worlds with either no, trace, or exotic atmospheres make sense as tide-locked worlds. Similarly, worlds with either a great deal of water (8+) or very little water (3-) also made sense as tide-locked.

Although Traveller⁵ does not provide for this possibility, worlds in close orbit to the primary may fall into a resonant orbit with the primary, like Mercury in the Sol system. I took a hard look at Twilight Zone worlds with breathable atmospheres and moderate hydrographic percentages. And for a select number of these worlds, I overrode the Twilight Zone code and assumed they have resonant orbits:

Aleikhes (DARK 0710 A755657-D)
Arahao (DARK 1008 C544733-5)
Meskok (DARK 2308 C654768-5)
Niysk (DARK 2405 E867424-2)
Springflow (DARK 2510 B777465-8)
Satwor (DARK 2610 A867632-A)
Temgassung (DARK 3205 C777422-5)
Eweuas (DARK 0112 A585745-C)
Merpikhnomi (DARK 1116 E544653-5)
Turnovo (DARK 3020 D766762-4)
Aiaiso (DARK 0727 C678747-8)
Eohe (DARK 0536 B776686-A)
Hroilr (DARK 1536 A556788-C)
Eiar (DARK 2539 C884788-8)
Miken (DARK 3033 B678564-9)

Large Terrestrial Planets

Traveller⁵ allows for mainworlds of larger than size A, though these are fairly rare. Recent discoveries in exoplanetology seem to support this idea, so I increased the size of the following size A Dark Nebula mainworlds accordingly:

World Size Changes
Hex	Name	UWP	Remarks
0909	Syasaral	DCA5499-8	Fl Ni Px
2605	Dengmi	CB88486-4	Ni Pa
0315	Etlaorla	CDC5166-A	Fl Lo Sa
2838	Olruiwos	BBA5786-A	Fl Tz

Forbidden Worlds

As discussed previously, many Dark Nebula worlds with starport X in Atlas of the Imperium had their starport codes changed to E or higher with Red travel zones during one round of T5SS review. For many of these worlds, the starport codes were reverted back to X during a subsequent round of review. But several starports lost both the X designation and the Red Zone, and I believe this was an error.

Simply adding back class X starports to these worlds presents a challenge. A class X starport imposes a hefty (-4) penalty on Tech Level. This can result in a maximum TL that is below the minimum necessary, which is determined by Atmosphere. Take, for example, Rormepeni (DARK 0915 E8B4443-8). An Atmo code of B indicates corrosive: “A concentrated gas mix or unusual temperature creates a corrosive environment, which requires the use of a protective suit or vacc suit” (MT Referee’s Manual 20–21). Such a hostile environment requires a minimum TL of 8. But if we gave Rormepeni a class X starport, the maximum TL we could generate would be 6 (1D) -4 (starport) +1 (Atmo) +1 (Pop) = 4, not enough to make it with a corrosive atmosphere.

For such worlds, we can leave the Class E starport but add a Red Zone travel code and the Forbidden (Fo) trade classification: Eahaeah (DARK 0206 E523498-7), Ahuawiyoi (DARK 0607 E8C4544-9), Ealyurei (DARK 0120 E100266-7), Rormepeni (DARK 0915 E8B4443-8), Ktealau (DARK 0130 E998123-7), Hlehekah (DARK 1127 E100545-A), Eakhyehiyye (DARK 0740 E544643-6), and Aiheisaus (DARK 1637 E100443-7). Only the world of Yetiuaya (DARK 2340 E768448-7) can also have its starport X reinstated.

Most of these red-zoned worlds are likely self-interdicted.

Hydro Codes

Several worlds in Dark Nebula have Hydrographics codes out of range from the Atmosphere codes: Ul (DARK 0603 A682698-A), Pannusgario (DARK 1003 A5829DB-A), Eariure (DARK 1901 C73A332-A), Lachbes (DARK 2501 D73A146-6), Asati (DARK 1912 D729400-9), Nabokov (DARK 3118 DAF5532-3), Shrlmia (DARK 3119 B7C2644-9), Ftihahe' (DARK 1023 D5A0798-8), Ekhiy (DARK 2023 B629386-B), O'awiy (DARK 2525 E84A897-8), Hkitei (DARK 0634 B73A367-E), Ahiyh (DARK 0838 E62A7A9-9), Hiwoieikh (DARK 1832 D893435-6), and Hynrl-Lavo (DARK 3036 A539543-E).

The T5SS was generally pretty rigorous in enforcing these limits and it looks like most of these are simple omissions. Most can be fixed by adjusting the Hydro code and occassionaly adding or removing a trade classification. Hkitei and Ahiyh, however, could not be adjusted without also changing the TL, which then cascades through the Importance, Economic, and Cultural extensions. For both worlds we can adjust the Atmo to 5.

Other Changes

The world 541-668 (DARK 2601 X541668-5) was explicitly described in Solomani and Aslan as being known only by its hex location (“2601”) but was issued a Scout Service type name. I had brought this up to Don McKinney during one pass of the T5SS but was overruled. Given that the original “name” has canonical backing I reverted the name for my own take.

Finally, Earle (Dark Nebula 0307) is described in Solomani and Aslan as an “Aslan world with high percentage of human population” (p 69). This would also correspond with the history of the world as noted on page 99. Based on this, I would recommend adding the remark “Huma4,” which would represent some 12 billion humans.

Change Log

Here are the resulting changes from adding Traveller⁵ classifications to the legacy Dark Nebula data:

Uiwe (0106) - add remark Tz.
Oukheayekh (0107) - add remark Co.
Oifairouw (0109) - add remark Tu.
Yeasea (0201) - add remark Tz.
Eahaeah (0206) - add remarks Tz Fo; Add R code to Travel Zone field to reflect Atlas of the Imperium.
Aohoikiy (0207) - add remark Lk.
Earle (0307) - add remarks Ho, Huma4 to reflect Solomani & Aslan.
Eakhtya'i (0402) - add remarks Sa Fr.
Sowhkeiy (0407) - add remarks Tz Ho.
Haiaokoa (0408) - add remark Tz.
Ularin (0501) - add remark Co.
Limenas (0502) - add remark Fr.
Usun (0503) - add remarks Sa Co.
Oekhaihikh (0507) - add remark Tz.
Amar (0601) - add remark Tz.
Ul (0603) - change UWP to A683698-A to put Hydro code within range.
Ahuawiyoi (0607) - add remarks Tz Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Tahetlo (0609) - add remark Ho.
Oiwohas (0707) - add remarks Lk Co.
Nalale (0801) - add remark Tz.
Elulor (0805) - add remark Tz.
Fteite (0807) - add remark Sa.
Hye (0809) - add remark Tz.
Chesall (0903) - add remark Sa.
Aoaki (0907) - add remark Lk.
Syasaral (0909) - change UWP to DCA5499-8; add remarks Tz Ho.
Pannusgario (1003) - change UWP to A5839DB-A to place Hydro code within range.
Walryaei (1004) - add remarks Tz Co.
Yoaieal (1104) - add remark Tz.
Hrowele (1107) - add remarks Tz Tr.
Osuilyuh (1110) - add remark Tz.
Trienamm (1203) - add remark Tz.
Uaweisa (1205) - add remark Co.
Hfieao (1207) - add remark Co.
Ftahalr (1208) - add remark Tz.
Canshar (1304) - add remark Tz.
Teioyukh (1310) - add remarks Tz Ho.
Reawaiy (1402) - add remarks Tz Co.
Oheou (1501) - add remark Tz.
Nihoipo (1504) - add remark Tz.
Hyeirih (1506) - add remark Sa.
Irekhal (1508) - add remark Ho.
Iweheh (1603) - add remarks Sa Co.
Jardeng (1604) - add remarks Tz Ho.
Eiyriou (1608) - add remark Tz.
Brensat (1609) - add remark Tz.
Aowoiktes (1705) - add remark Tz.
Yeyofui' (1708) - add remark Tz.
Doning (1804) - add remark Tz.
Bathanfel (1805) - add remark Ho.
Earlure (1901) - change UWP to C738332-A to put Hydro code within range; remove Wa remark; add remarks Tz Ho.
Murphy (1902) - add remarks Sa Co.
Aeia (1907) - add remark Lk.
Bontennes (2001) - add remark Tz.
Rodsban (2002) - add remark Tz.
Sordno (2010) - add remark Tz.
Febung (2108) - add remark Tz.
Tauoilais (2109) - add remarks Tz Co.
Kemsung (2202) - add remark Tz.
Dloh (2208) - add remarks Sa Ho.
Datja (2302) - add remark Tu.
Wisu (2402) - add remark Tz.
Wanlir (2403) - add remark Tz.
Mamalt (2404) - add remark Tz Co.
Mosarelel (2407) - add remark Tz Co.
Carn Gafall (2408) - add remark Tz.
Lachbes (2501) - change UWP to D738146-6 to put Hydro code within range; remove Wa remark; add remark Tz.
Karziv (2603) - add remarks Tz Ho.
Dengmi (2605) - change UWP to CB88486-4.
Fonfado (2606) - add remark Fr.
Morlisbon (2609) - add remark Tz.
Rana (2710) - add remark Ho.
Romart (2810) - add remark Tz.
Mosgat (2901) - add remark Tz.
Renfrew (2904) - add remark Tz.
Angle (3005) - add remark Tz.
Patawidmam (3009) - add remark Ho.
Wormen (3106) - add remark Lk.
Linate (3204) - add remarks Lk Ho.
Ouleawos (0114) - add remarks Tz Co.
Tyakhyo (0115) - add remark Tz.
Ealyurei (0120) - add remarks Lk Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Aulyetyu (0214) - add remark Tz.
Au'aiyyee (0220) - add remarks Sa Co.
Ayeiyfua (0311) - add remarks Lk Ho.
Kikeasa (0314) - add remark Tz.
Etlaorla (0315) - change UWP to CDC5166-A.
Oyuyes (0316) - add remark Tz.
Ealalrye (0317) - add remark Tz.
Htaheatelr (0411) - add remarks Tz Co.
Ftyuealoi (0416) - add remark Co.
Hkyewao (0519) - add remark Lk.
Htiyhoai (0612) - add remark Tz.
Hirliyse (0613) - add remark Lk.
Ktarua (0614) - add remarks Tz Co.
Leftearl (0615) - add remark Sa.
Uioirli (0811) - add remarks Tz Co.
Nishror (0812) - add remarks Tz Tu.
Chorikhnare (0815) - add remark Tz.
Htaweal (0817) - add remarks Tz Ho.
Siniob (0819) - add remark Tz.
Kipelaresh (0914) - add remark Tz.
Rormepeni (0915) - add remarks Tz Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
I'etle (0916) - add remarks Sa Co.
Ewuia (0918) - add remark Ho.
Hopeshre (1014) - add remark Tz.
Ihkasya (1020) - add remark Fr.
Alaooh (1111) - add remark Tz.
Osa (1112) - add remark Tz.
Eaisakh (1120) - add remark Ho.
Thometha (1213) - add remarks Sa Co.
Meshmo (1215) - add remarks Tz Ho.
Iopfen (1217) - add remark Tz.
Oyarn (1420) - add remark Ho.
Ekhtekih (1518) - add remark Tz.
Eauie (1519) - add remark Tz.
Aseahya (1611) - add remarks Tz Co.
Sherarehi (1615) - add remarks Sa Ho.
Hlao (1719) - add remark Tz.
Ye (1813) - add remark Tz.
Asati (1912) - change UWP to D727400-9 to put Hydro code within range; add remarks Tz Ho.
Kakhisil (1915) - add remark Fr.
Horrace (1916) - add remark Tz.
Khoakta (1918) - add remarks Lk Co.
Taeahehe (2011) - add remark Tz.
Morain (2012) - add remark Fr.
Hleahao (2018) - add remarks Lk Co.
Oiaous (2020) - add remark Tz.
Ikhaeal (2111) - add remark Tz.
Sharp (2117) - add remark Tz.
Pritchard (2214) - add remark Tz.
Yakolev (2215) - add remark Co.
Crain (2216) - add remark Tz.
Ehoioi (2218) - add remark Tz.
Strin (2316) - add remark Lk.
Nigdye (2413) - add remark Tz.
Ilriyhya (2415) - add remark Ho.
Stop Gap (2416) - add remark Sa.
Lima (2511) - add remarks Fr Sa.
Tortsad (2516) - add remarks Sa Co.
Wolsone (2613) - add remark Tz.
Hichape (2713) - add remark Tz.
Ninnihrang (2812) - add remark Tz.
Merejace (2815) - add remark Tz.
Waq (2819) - add remark Co.
Shobind (2911) - add remark Tz.
Yakoru (3114) - add remark Tz.
Morsang (3116) - add remark Tz.
Nabokov (3118) - change UWP to DAF6532-3 to put Hydro code within range.
Shrimia (3119) - change UWP to B7C3644-9 to put Hydro code within range; remove He remark; add remark Tz.
Pangringgan (3120) - add remarks Co Tz.
Aiolio (3214) - add remark Tz.
Wangmetjem (3217) - add remarks Tz Ho.
Iruma (3219) - add remark Tz.
Kteatau (0130) - add remark Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Yehta (0226) - add remark Lk.
Seilrye (0227) - add remark Tz.
Iyyoiy (0321) - add remark Fr.
Ktaol (0327) - add remark Tz.
Ruiloih (0328) - add remark Sa Co.
Wuhtiaweh (0329) - add remarks Tz Co.
Ye'aeaoafokh (0330) - add remark Lk.
Atayekhe (0421) - add remark Tz.
Yokiyheir (0423) - add remark Tz.
Teaiyre (0427) - add remark Tz.
Eftaeikui (0428) - add remark Lk.
Hoireh (0523) - add remark Sa.
Heiaieai' (0524) - add remarks Sa Ho.
Ao'iyaulra (0627) - add remark Tz.
Khteau (0628) - add remark Co.
Ihkeh (0629) - add remarks Tz Co.
Stofakhail (0630) - add remark Lk.
Stui (0721) - add remark Tz.
Yasai (0722) - add remark Tz.
Erloufteaw (0725) - add remark Ho.
Ziha (0824) - add remark Tz
Auyal (0825) - add remark Tz.
Khtyu (0827) - add remarks Lk Co.
Foiheliy (0922) - add remark Tz.
Ftihahe' (1023) - change UWP to D5A1798-8 to put Hydro code within range; add remarks Fl Lk Co.
Leihkyeau (1025) - add remarks Lk Co.
Ilkhah (1027) - add remark Tz.
Oarua (1121) - add remark Tz.
Ahehuikh (1124) - add remark Tz.
Htehekah (1127) - add remarks Sa Co Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Hlitilar (1224) - add remark Lk.
Naco (1321) - add remark Tz.
Iyokh (1430) - add remarks Tz Co.
Foiseihyaluh (1522) - add remark Tz.
Mihraga (1621) - add remark Ho.
Hyesiyr (1622) - add remark Lk.
Heahelie (1629) - add remark Tz.
Easouyao (1721) - add remarks Sa Co.
Syailei (1724) - add remark Tz.
Tenarna (1825) - add remarks Tz Ho.
Yelrailr (1829) - add remarks Tz Co.
Iyaiah (1925) - add remark Lk.
Tiylewoiw (1930) - add remark Tz.
Ewirarl (2021) - add remark Sa.
Ekhiy (2023) - achange UWP to B627386-B to put Hydro code within range; add remark Tz.
Fyawahri (2026) - add remarks Lk Co.
Kihahouwu (2028) - add remarks Tz Ho.
Sewalair (2121) - add remark Lk.
Iyhahorl (2125) - add remark Tz.
Aohitao (2126) - add remark Tz.
Khtyasitrao (2322) - add remark Tz.
Styaroir (2325) - add remarks Tz Co.
Oskvo (2422) - add remarks Tz Ho.
Iweakhte (2426) - add remark Tz.
Eiouktoh (2427) - add remark Tz.
Oiirl (2430) - add remarks Tz Co.
Besmam (2523) - add remark Tz.
Sovkhersk (2524) - add remark Ho.
O'awiy (2525) - change UWP to E849857-8 to put Hydro code within range and maintain TL; remove Wa remark.
Earltras (2527) - add remark Fr.
Dranweis (2624) - add remark Sa.
Gallbre (2629) - add remarks Tz Co.
Aokhtiyfti (2728) - add remarks Sa Co.
Kanna (2824) - add remark Ho.
Petal (3024) - add remark Tz.
Bridgehead (3121) - add remark Tz.
Shin (3123) - add remark Tz.
Terenn (3128) - add remark Tz.
Garnenshold (3129) - add remark Tz.
Abmi (3223) - add remark Tz.
Cupuepue (3226) - add remarks Tz Co.
Iykye (0136) - add remark Co.
Hkiho (0140) - add remark Lk.
Khiyu (0239) - add remark Lk.
Aotui'asiyr (0334) - add remarks Tz Co.
Wiykhearl (0335) - add remarks Sa Ho.
Eaoer (0336) - add remark Tz.
Iytaow (0432) - add remark Tz.
Eoyaea (0435) - add remarks Sa Co.
Traihoa (0437) - add remark Tz.
Ihkealresiy (0440) - add remarks Sa Ho.
Hkitei (0634) - change atmo to 5; add remark Tz.
Waohar (0738) - add remark Tz.
Eakhyehiyye (0740) - add remark Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Feakh (0835) - add remarks Tz Co.
Ahiyh (0838) - change atmo to 5; remove remark Pi; add remarks Wa Ho.
Ewei (0839) - add remarks Tz Co.
Soukhi' (0934) - add remark Sa.
Uryarlil (0937) - add remarks Lk Ho.
Seiyasar (0939) - add remark Tz.
Kheiei (1034) - add remark Sa.
Taleiw (1037) - add remarks Tz Co.
Isikhas (1232) - add remark Sa.
Eiefei'os (1235) - add remarks Sa Co.
Eikhilua (1236) - add remark Tz.
Teayokhtae (1238) - add remark Tz.
Htakaoea (1331) - add remark Tz.
Heaeakh (1335) - add remark Tz.
Suikhiyeisela (1337) - add remark Sa.
Yoreah (1431) - add remark Sa.
Oihaiyo (1434) - add remark Tz.
Ikhoalreih (1439) - add remark Lk.
Aiheisaus (1637) - add remarks Co Fo; add R code to Travel Zone field to reflect Atlas of the Imperium.
Eihkeha (1638) - add remark Tz.
Tlaea'yeryel (1640) - add remark Tz.
Ihtye (1731) - add remark Fr.
Asefihea (1740) - add remark Tz.
Hiwoieikh (1832) - change UWP to D894435-6 to put Hydro code within range; add remarks Pa Tz.
Atoiloilol (1939) - add remark Tz.
Oakheiye (2031) - add remarks Tz Co.
Eahkihkao (2033) - add remarks Tz Ho.
Htao'ewyalr (2038) - add remark Tz.
Eiaohe (2039) - add remark Sa.
Ehairiwa (2131) - add remark Tz.
Hkyosali (2132) - add remark Ho.
Ewausiaktiy (2136) - add remarks Tz Co.
Hkayuea (2140) - add remark Tz.
Erelefo (2335) - add remark Tr.
Yetiuaya (2340) - Change UWP to X768448-3 to match Atlas of the Imperium; add remarks Fo Tz; change Cultural Extension to [4153]; add R code to Travel Zone field.
Uiwealirlao (2435) - add remarks Tz Ho.
Oeafowyahlulr (2537) - add remark Tz.
Khaolao (2635) - add remark Tz.
Hyefteite (2639) - add remark Tz.
Jingleswelt (2732) - add remark Tz.
Ohkiylyo (2734) - add remarks Tz Co.
Theleme (2836) - add remarks Lk Ho.
Brimate (2837) - add remark Lk.
Olruiwos (2838) - change UWP to BBA5786-A; add remark Tz.
Teaoiyekh (2839) - add remark Tz.
Ilalt (2937) - add remark Tz.
Gimemuh (2938) - add remarks Tz Co.
Caparro (3032) - add remarks Tz Co.
Hynri-lavo (3036) - change UWP to A538543-E to put Hydro code within range; add remark Tz.
Treege (3132) - add remark Tz.
Junganyika (3236) - add remark Lk.
Newquay (3240) - add remark Tz.

Copyright Information

Tuesday, October 26, 2021

Revised Dark Nebula Stellar Data

The M2 III red giant primary of the Steiaseah (DARK 1927) system. The ancient Terrans designated the star Beta Pegasi, while the Aslan know it as Ua’aloiatye, the Bright Star.

The current stellar data for Dark Nebula sector, as found on the Traveller Map, reflects fairly early world generation methods. Atlas of the Imperium (1984) included a dot map of the sector with system locations and rudimentary data such as starport class and the names of high-population worlds. Stellar data for Kilrai’ subsector was first provided in the Travellers’ Digest 17 (1989) and for the entire sector in Solomani & Aslan: The Rimward Races (1991). Like the old Spinward Marches data set, this data has a relatively high number of subgiant, giant, and even supergiant stars as well as many white dwarfs.

For my house version of Dark Nebula, I wanted to follow a similar path as the T5 Second Survey Marches review by curtailing the number of stars outside of the main sequence and trying to match up habitable worlds with reasonable primaries.

All sources agree that Kusyu’s primary is Tyeyo, a G4 V star with a close white dwarf companion, Saietaie. (Of course, no one could agree just where Kusyu was located until the T5SS!) Although having a habitable world and white dwarf seems implausible, this has so much canonical weight I think it’s best considered inviolable.

The only other canonical text reference to stellar data I could locate was to Yehta/Siei (Dark Nebula 0226), a planetoid torn between two stars and a gas giant.

Although it is nowhere described in canon, many have noted the presence of an extremely bright supergiant (F8 Ia) in Dark Nebula. Originally located in the Eakhoi (2123) system, which has a high population garden world, the stellar data was shifted to the asteroid system Troutiyka (2230) during an earlier pass of the T5SS. As noted in that thread, even with this change a supergiant in this location of Charted Space (65–70 parsecs from Terra) would be the brightest star in the Earth’s sky, roughly as bright as Jupiter.

There are a handful of bright real world stars that would be located in approximately the same area as Dark Nebula:

Real World Stars Near Dark Nebula
Bayer Designation	Common Name	RA	Dec	Galactic Long (lb°)	Galactic Lat (b°)	Spectral Type	Vis Mag	Abs Mag	Dist (LY)
Gamma Draconis	Eltanin	17 57	51.5	79.1	29.1	K5 III	2.24	-1.04	148
Beta Pegasi	Scheat	23 04	28.1	95.8	-29.1	M2 III	2.44v	-1.49v	200
Alpha Pegasi	Markab	23 05	15.2	88.4	-40.4	B9 IV	2.49	-0.67	140
Eta Pegasi	Matar	22 43	30.2	92.5	-25	G2 II-III F0 V	2.93	-1.16	215
Theta Aquilae		20 11	-0.8	41.6	-18.1	B9.5 III	3.24	-1.48	285
Delta Aquarii	Skat	22 55	-15.8	49.6	-60.7	A3 III	3.27	-0.18	160
Zeta Pegasi	Homam	22 41	10.8	78.9	-40.7	B8.5 V	3.41	-0.62	210
Beta Bootis	Nekkar	15 02	40.4	67.6	60	G8 III	3.49	-0.64	220

Standard disclaimer: it is folly to try to establish a consistent relationship between real world stars and jump maps of Charted Space. And our real world understanding and classification of stellar data is constantly changing. But if we’re a little more than 50 parsecs from Terra, I think it’s useful to give unusually bright stars in the sector data extra scrutiny (why don’t we see this F8 Ia star from Earth?), and if possible associate them with a real world analog. Maybe the A7 IV primary of Stralsund (Solomani Rim 0618) is really Alpha Cephei, and maybe it isn’t, but the connection is there if a referee wants it.

As I worked through the data I took a hard look at the outlier stars—the subgiants, giants, white dwarfs, and so on. In general, I reduced these to main sequence stars, though I tweaked a few to line up with some of the real world candidates. I found a nice home for Beta Pegasi in Steiaseah (1927), a system without gas giants or belts and an airless planetoid for a mainworld. And it just happens to be in the same area as Daanarni, the “Bright Star” of the Dark Nebula board game.

I dithered over what to do with that F8 Ia, especially with Beta Pegasi already placed in the sector. I went back and looked at past discussions and really didn’t see anyone arguing that Dark Nebula needed a supergiant, and with no canonical grounding I decided to scale that star back.

I also took a hard look at the M class stars: there are at lot of these, and that’s consistent with real world data. But red dwarfs are so cool that worlds in the habitable zone are almost always tidally locked unless they wind up in a resonant orbit. There is an interesting debate going on right now about the habitability of tide-locked worlds, so I generally left the red dwarf stars alone. But in a handful of cases—generally agricultural and/or garden worlds—I changed the primary to something a bit warmer.

Here are my proposed changes to the Dark Nebula stellar data:

Aohoikiy (0207) - Change stellar data from M3 III D to M3 V to reduce giant star to main sequence.
Tahetlo (0609) - Change stellar data from M6 III K9 V to K9 V to remove giant star.
Nalale (0801) - Change stellar data from M3 III to M3 V to reduce giant star to main sequence.
Helene (1005) - Change stellar data from K4 III to K4 V to reduce giant star to main sequence.
Hfieao (1207) - Change stellar data from A1 IV F7 V to F7 V to remove bright subgiant star.
Teioyukh (1310) - Change stellar data from K1 III to K1 V to reduce giant star to main sequence.
Reawaiy (1402) - Change stellar data from M3 III to M3 V to reduce giant star to main sequence.
Eiyriou (1608) - Change stellar data from M0 III D to M0 V D to reduce giant star to main sequence.
Bathanfel (1805) - Change stellar data from M1 V M6 V to G6 V to reflect habitability.
Cuoon (2105) - Change stellar data from M0 V to K0 V to reflect native Chirper population.
Rindnoir (2201) - Change stellar data from M2 V M4 V to G2 V to reflect planetary habitability.
Elahkilr (2203) - Change stellar data from M2 V M3 V to K8 V to reflect planetary habitability.
Caprona (2607) - Change stellar data from K7 II M6 V to K7 V M6 V to reduce giant star to main sequence.
Bedegrayn (2608) - Change stellar data from A3 IV to M3 V to reduce bright subgiant star to main sequence.
Frasden (2801) - Change stellar data from K0 II to K0 V to reduce giant star to main sequence.
Romart (2810) - Change stellar data from K5 II to M0 V to reduce giant star to main sequence.
Strova (2903) - Change stellar data from M9 III D to K5 V to reduce giant star to main sequence.
Hfayulealr (0319) - Change stellar data from M2 V M2 V M3 V to F5 V to reflect likely Terran colony.
Tahwyafe (0717) - Change stellar data from M6 II to B8 V (Zeta Pegasi).
Rosal (0720) - Change stellar data from M2 V to F7 V to reflect native Droyne population.
Hipera (0814) - Change stellar data from M1 V to F7 V to reflect likely Terran colony.
Htaweal (0817) - Change stellar data from K5 IV to K5 V to reduce unlikely subgiant star to main sequence.
Kipelaresh (0914) - Change stellar data from K7 II to M0 V M4 V to reduce giant star to main sequence.
Meshmo (1215) - Change stellar data from K4 IV to K4 V to reduce unlikely subgiant star to main sequence.
Akhlare (1313) - Change stellar data from M2 V to K2 V to reflect native Ormine population.
Yakolev (2215) - Change stellar data from M2 V to F1 V B9 III (Delta Cygni).
Ilriyhya (2415) - Change stellar data from M0 III D to G9 V M9 V to reduce giant star to main sequence.
Stop Gap (2416) - Change stellar data from M2 II to F2 V G3 V to reduce giant star to main sequence.
Neween (2619) - Change stellar data from M2 II D to G4 V M1 V to reduce giant star to main sequence and remove white dwarf.
Waq (2819) - Change stellar data from M1 II to G8 III (Zeta Cygni).
Nabebe (3015) - Change stellar data from M2 V M5 V to F5 V to reflect planetary habitability
Nabokov (3118) - Change stellar data from M1 V M8 V to K1 V M8 V to reflect planetary habitability.
Ro Hyeres (3218) - Change stellar data from M6 III D M5 V to G8 V to reduce giant star to main sequence.
Syerakhir (0222) - Change stellar data from M2 V M9 V to K2 V M9 V to reflect likely Terran colony site.
Uiaio (0224) - Change stellar data from K6 IV M6 V to K6 V M6 V to reduce unlikely subgiant star to main sequence.
Iyyoiy (0321) - Change stellar data from M9 II M9 V to M2 V to reduce giant star to main sequence.
Teaiyre (0427) - Change stellar data from G8 III to M1 V M8 V to reduce giant star to main sequence.
Hlyerl (0429) - Change stellar data from M3 III to K5 V to reduce giant star to main sequence.
Kteaesyah (0527) - Change stellar data from K8 II M8 V to G7 V to reduce giant star to main sequence.
Khteau (0628) - Change stellar data from G3 IV to G2 II F0 V (Eta Pegasi).
Ahaiehea (0726) - Change stellar data from M2 V to G2 V to reflect planetary habitability.
Ziha (0824) - Change stellar data from M0 III D to M0 V to reduce giant star to main sequence.
Iylhreyu (0829) - Change stellar data from M1 V to K1 V to reflect planetary habitability.
Ewirle (1028) - Change stellar data from M1 V to G2 V to reflect planetary habitability.
Weisaow (1327) - Change stellar data from M3 V to K2 V M3 V to reflect planetary habitability and match board game; stars correspond to Blatta and Xida.
Iyohkeih (1427) - Change stellar data from K4 III to K4 V to reduce giant star to main sequence; primary named Rosa based on board game.
Aiearye (1428) - Change stellar data from K0 II D to K2 V to reduce giant star to main sequence; primary named Panas based on board game.
Syailei (1724) - Change stellar data from M4 III to M0 V M7 V to reduce giant star to main sequence and reflect binary system in board game; stars named Dim and Astek.
Eieiau (1830) - Change stellar data from K6 IV to K6 V to reduce unlikely subgiant star to main sequence.
Troi' (1923) - Change stellar data from M3 V M2 V to G9 V M9 V to reflect planetary habitability; based on board game G9 V primary named Ria and the M9 V near companion Alis.
Steiaseah (1927) - Change stellar data from M1 V to M2 III (Beta Pegasi); based on board game asteroid belt also known as Daanarni.
Kihahouwu (2028) - Change stellar data from K4 IV M7 V to K4 V to reduce unlikely subgiant star and match board game; primary named Salia per board game.
Eakhoi (2123) - Change stellar data from M1 V to K1 V to reflect planetary habitability.
Iouhtah (2128) - Change stellar data from M1 V M3 V to K1 V to reflect planetary habitability; based on board game primary named Kov.
Troutiyka (2230) - Change stellar data from F8 Ia to F8 V G4 V to reduce supergiant star to main sequence and correspond to stars N3 and N4 from board game.
Styaroir (2325) - Change stellar data from M7 III D to M1 V M9 V to reduce giant star to main sequence; based on board game stars named Umuro and Omoro.
Eiouktoh (2427) - Change stellar data from M0 V to M0 V G3 V to reflect board game; stars named Rishi and Kamat.
Arakhal (2729) - Change stellar data from M2 V to G2 V M2 V to reflect board game; stars named Maadin and Omyl.
Tanjert-Nebo (2821) - Change stellar data from K3 III M6 V to K3 V to reduce giant star to main sequence.
Gilead (2921) - Change stellar data from M3 V to K5 V to reflect planetary habitability.
Iywaiwofu (0337) - Change stellar data from K9 IV to K9 V to reduce unlikely subgiant star to main sequence.
Hyeirih (0537) - Change stellar data from K9 IV to K9 V to reduce unlikely subgiant star to main sequence.
Sualriyw (0636) - Change stellar data from M3 V M8 V to K5 V to reflect planetary habitability.
Khohoa (0733) - Change stellar data from M3 III D to M3 V to reduce giant star to main sequence.
Waohar (0738) - Change stellar data from M0 III to M0 V to reduce giant star to main sequence.
Fuihafai (0834) - Change stellar data from M5 II to G8 V K5 V to reduce giant star to main sequence.
Hai Ei (0836) - Change stellar data from K3 IV M6 V to K3 V M6 V to reduce unlikely subgiant star to main sequence.
Steisua (1135) - Change stellar data from K8 III to G1 V M1 V to reduce giant star to main sequence.
Yoreah (1431) - Change stellar data from M5 III D to M3 V to reduce giant star to main sequence.
Taiea (1535) - Change stellar data from K8 III M5 V to G8 V to reduce giant star to main sequence.
Ualaohei (1934) - Change stellar data from M2 V M5 V to K9 V to reflect planetary habitability; based on board game star named Osa.
Tloueaeiei (2037) - Change stellar data from G6 III D to K8 V to reduce giant star to main sequence.
Eiaohe (2039) - Change stellar data from K0 III D to F5 V to reduce giant star to main sequence.
Hkyosali (2132) - Change stellar data from M2 V M4 V M9 V to G6 V; based on board game primary corresponds to star N1.
Erelefo (2335) - Change stellar data from M1 V M0 V to F1 V to reflect planetary habitability, based on board game star corresponds to Duduki.
Irihroalea (2432) - Change stellar data from K7 III to K7 V to reduce giant star to main sequence; based on board game primary named Irbev.
Euhisai (2434) - Change stellar data from M2 V M1 V to K4 V to reflect planetary habitability; based on board game primary named Changa.
Steahryoha (2540) - Change stellar data from M2 III to G3 V to reduce giant star to main sequence.