As described in CT Alien Module 1, Aslan (CTAM1), “The largest landholds are in the hands of the Tlaukhu, and consist of many worlds and parts of worlds. Since holding such an extensive territory is beyond the ability of one Aslan, an extensive network of vassals (usually sons, brothers, or male relatives by marriage) administer it in the clan head’s name” (4).
Each Tlaukhu clan has several vassal clans that owe them fealty. These vassal clans are significant enough that the worlds they control are assigned their own allegiance code, AsTv. A Tlaukhu Vassal controlled world is described as “controlled (but not owned) by a vassal clan in fief to one of the 29.”
Vassals can be born, made, or won in battle. As noted above, many of a clan’s second sons may elect to become vassals (fiy) rather than ihatei, and go on to manage established landholds on behalf of their lord. A clan may also create a new vassal to reward a loyal follower who performed a great service to the clan. An ihatei colony that settles new lands is initially a vassal to the sponsoring clan. Finally, vassals can be won by subjugating another clan and forcing them to bend the knee. Defeating another clan might also entitle the victor to claim some or even all of their vassals.
Although being a vassal clan is probably less prestigious than being an independent clan, swearing fealty to a more powerful clan provides several benefits. As GURPS Traveller: Alien Races 2 (GT:AR2) explains, “Duties between vassal clans and their lords run strong in both directions—to attack one is to attack the other—so it is common for battles to involve several clans on each side, and possibly mercenary units as well” (32).
As GT:AR2 further relates, “The overlord guarantees his vassals secure (and usually hereditary) tenure of their lands, and rewards them with further territory he may acquire by conquest or other means. Since an overlord’s vassals bear the brunt of the expense of fighting, and demand additional lands in return for their service, Aslan warfare emphasizes offensive action to seize new land” (13).
This strongly implies that, in addition to administering their overlord’s lands, a vassal might also win and hold lands of their own. Reinforcing this insight is our knowledge that Tlaukhu vassals can in turn command vassals of their own, based on the example from CTAM1 of “clan Wahtoi, which is a vassal of clan Aroaye’i, itself a vassal of clan Hlyueawi” (7). While the process of subinfeudation could theoretically continue down and down to minor clans, given that most clans in the Hierate are said to be independent I’m inclined to limit this to two levels of fealty.
Tlaukhu vassal clans presumably vary greatly in terms of size and assets. While some might only manage portions of a world, others might manage an entire world and yet others might manage multiple worlds across the Hierate on behalf of their Tlaukhu overlord. If each Tlaukhu clan has between 30 to 40 worlds that are managed by vassal clans, let’s assume that each Tlaukhu clan has 1D direct vassal clans that manage 1D worlds, and each of those vassal clans have 1D-1 vassal clans of their own that manage another 1D-1 worlds each. All of these Vassal Clan controlled worlds would have the allegiance code AsTv and would be considered to be part of the Tlaukhu clan’s holding.
This also suggests there are about 100 direct vassal clans of Tlaukhu clans in the Hierate, and another 250 indirect vassal clans of Tlaukhu clans. Taken together, this suggests that roughly 10% of Hierate clans are either Tlaukhu members, or else direct or inderect vassals of member clans, which seems like a reasonable guess.
Worlds controlled by a Tlaukhu vassal can have both a Tlaukhu base, built and maintained by the Tlaukhu clan, as well as a clan base, built and maintained by the vassal clan itself. In fact, raising military forces on behalf of the overlord is an important obligation of a vassal clan.
Tlaukhu Military Forces
As discussed above, all Tlaukhu clans combined might directly control 1,000 to 1,100 worlds across the Hierate, and their vassal clans might control another 1,000 to 1,100 worlds on their behalf. That suggests individual Tlaukhu clans might directly control 30 to 40 worlds, and their vassal clans a comparable number.
Further, Tlaukhu clans may have holdings on worlds with Split Control allegiance (Code AsSc), which number another 1,200 to 1,400 worlds. Not every Tlaukhu clan will occupy every Split Control world, and some Split Control worlds may not have any Tlaukhu clans, but let’s assume each Tlaukhu member possesses, on average, major holdings on 200 split control worlds.
If we could put these holdings into a single region, this might be the equivalent of controlling 2–4 subsectors. Chris Thrash calculated that in the Imperium, the average subsector fields six colonial squadrons: three CruRons, two BatRons, and one AssaultRon, plus three Imperial Navy squadrons. Let’s assume that, although the Aslan are far less organized than the Imperium, they are far more militarized, so they produce squadrons at comparable rates. And let’s assume that the average Tlaukhu clan controls the equivalent of four subsectors. This would suggest that a Tlaukhu clan and its vassals could field the tonnage equivalent of 9 CruRons, 6 BatRons, and 3 AssaultRons, or some 18 million dtons. Respectable, but not overwhelming.
One inherent limitation for the Aslan is that their Space Forces are distributed inefficiently throughout the Hierate. Presumably the Tlaukhu would attempt to coordinate defenses along the borders of neighboring interstellar states like the Imperium or the Confederation, but in general it appears naval assets are not positioned for optimum strategic value. This might explain why the Confederation has been able to successfully encroach on Aslan space.
The composition of Tlaukhu squadrons would likely be very different than anything the Imperium would field. While the Hierate borders both the Solomani Confederation and the Imperium, the greatest threat to a clan would be other clans, so navies will be built to fight other clan forces. We don’t have many canonical examples of Aslan capital ships, and GT:AR2 claims that the “male preference for dewclaw-to-dewclaw fighting, and the hideous expense of capital ships, means that compared to a Human fleet, a typical clan navy has fewer, smaller ships. It is rare to encounter a cruiser or larger warship” (34). In this light, battle rider and fighter carrier squadrons would likely be very popular and appropriate for clan-on-clan conflicts.
CTAM1 notes that “Tlaukhu Space Forces are more proficient, better equipped, and more technologically advanced [than other clan forces]” (6). The highest TL in the Hierate circa 1105 is 14, but perhaps only elite Tlaukhu squadrons would be built at that tech level. Most Tlaukhu and Tlaukhu vassal squadrons would likely be built to TL12 or 13 standards, while other clans might be limited to building TL10 or TL11 vessels
As TL12 marks the common introduction of meson weapons and defenses, this technological inflection point gives Tlaukhu clans and their vassals a tremendous advantage over other clans. I would guess that the hyper-competitive Aslan jealously guard their technology and that Tlaukhu clans are very circumspect about selling military ships or equipment to lesser clans. (This might provide a huge opportunity for unscrupulous Human traders.)
Tlaukhu Vassal Worlds
The Tlaukhu Vassal Clan allegiance code (AsTv) gives no indication which bloc, much less which Tlaukhu clan, the vassal owes fealty to. If the specific Tlaukhu member needs to be determined, the following D66 table can be used:
Die | Bloc | Tlaukhu Overlord | Die | Bloc | Tlaukhu Overlord |
---|---|---|---|---|---|
11 | AsT0 | Yerlyaruiwo (1) | 41 | AsT4 | Eakhtiyho (5) |
12 | AsT0 | Yerlyaruiwo (1) | 42 | AsT4 | Eteawyolei’ (11) |
13 | AsT0 | Hrawoao (13) | 43 | AsT4 | Fteweyeakh (23) |
14 | AsT0 | Eisohiyw (14) | 44 | AsT5 | Hlyueawi (6) |
15 | AsT0 | Ferekhearl (19) | 45 | AsT5 | Hlyueawi (6) |
16 | AsT1 | Khaukheairl (2) | 46 | AsT5 | Isoitiyro (15) |
21 | AsT1 | Khaukheairl (2) | 51 | AsT6 | Uiktawa (7) |
22 | AsT1 | Estoieie’ (16) | 52 | AsT6 | Iykyasea (17) |
23 | AsT1 | Toaseilwi (22) | 53 | AsT6 | Faowaou (27) |
24 | AsT2 | Syoisuis (3) | 54 | AsT7 | Ikhtealyo (8) |
25 | AsT2 | Syoisuis (3) | 55 | AsT7 | Tlerfearlyo (20) |
26 | AsT2 | Syoisuis (3) | 56 | AsT7 | Yehtahikh (24) |
31 | AsT2 | Syoisuis (3) | 61 | AsT8 | Seieakh (9) |
32 | AsT2 | Syoisuis (3) | 62 | AsT8 | Akatoiloh (18) |
33 | AsT3 | Tralyeaeawi (4) | 63 | AsT8 | We’okunir (29) |
34 | AsT3 | Yulraleh (12) | 64 | AsT9 | Aokhalte (10) |
35 | AsT3 | Aiheilar (25) | 65 | AsT9 | Sahao’ (21) |
36 | AsT3 | Riyhalaei (28) | 66 | AsT9 | Ouokhoi (26) |
To determine whether the vassal clan is a direct vassal of the Tlaukhu clan or a vassal of a vassal clan, consult the following D66 table:
1D | Vassal Status |
---|---|
1-2 | Direct Vassal |
3-6 | Vassal of a Vassal |
Copyright Information
The illustration at the start of this blog entry is by Michael Vilardi from Travellers’ Digest 21 (1990).
The Traveller game in all forms is owned by Far Future Enterprises. Copyright © 1977 – 2022 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.
No comments:
Post a Comment