{Im}, T5SS, and Capitals in the Solomani Rim

[Garnfellow]

The last big round of the T5 Second Survey sector data appeared to use T5’s Importance stat to determine subsector capitals, resulting in a few changes from previously published data. I took a look at how this shook out in the Solomani Rim, where a whopping 7 of the 15 subsector capitals were affected.

There are at least four different canonical sources for Rim data prior to the Rebellion: Supplement 10: The Solomani Rim (1982), Alien Module 6: Solomani (1986), GURPS Traveller Rim of Fire (2000), and Mongoose Traveller: Solomani Rim (2012). All four sources are pretty much in agreement as to the identity of the subsector capitals. There is a slight discrepancy in Alien Module 6 – the “Solomani Rim Data” table has Lagash as the capital of Sol Subsector (consistent with Supplement 10), while “World Index” table has Terra.

Here’s a breakdown of all the subsector capitals in the Rim:

Subsector	Previous Capital	T5SS Capital
Ultima (Subsector A)	Thamber (0704 A554898-C)	Iddamakur (0110 A7799AB-A)
Suleiman (Subsector B)	Suleiman (1504 AA6598B-E)	Ascalon (1207 A562AAF-E)
Concord (Subsector C)	Eleusis (2109 A789831-D)	Ephemir (2308 A675999-E)
Harlequin (Subsector D)	Arkiirkii (2905 A66A8AD-E)	Arkiirkii (2905 A66A8AD-E)
Alderamin (Subsector E)	Shululsish (0214 A584A52-F)	Shululsish (0214 A584A52-F)
Esperance (Subsector F)	[None]	[None]
Vega (Subsector G)	Muan Gwi (1717 A556A86-E)	Muan Gwi (1717 A556A86-E)
Banasdan (Subsector H)	Banasdan (2920 A653A54-F)	Murphy (2517 A5449BE-E)
Albadawi (Subsector I)	Gaea (0722 A986986-E)	Eneldun (0326 A31498A-E)
Dingir (Subsector J)	Dingir (1222 AA89A98-F)	Dingir (1222 AA89A98-F)
Sol (Subsector K)	Lagash (2121 A667A8B-F)	Agidda (1824 A974979-C)
Arcturus (Subsector L)	Jael (2821 A55789A-C)	Tewfik (2528 A524945-D)
Jardin (Subsector M)	Jardin (0233 A5679BC-D)	Jardin (0233 A5679BC-D)
Capella (Subsector N)	Twylo (1034 A551AA6-E)	Twylo (1034 A551AA6-E)
Gemini (Subsector O)	Hamilcar (1738 A56A9AA-E)	Hamilcar (1738 A56A9AA-E)
Kukulkan (Subsector P)	Laputa (2740 A7559D9-C)	Laputa (2740 A7559D9-C)

My take on this is that, for the Rim at least, the revisions are undoubtedly well-intentioned but wrong-headed. The changes don’t make a significant improvement on the status quo and in fact create new problems by invalidating plenty of perfectly good canon. For example, there are some nice discussions in Rim of Fire and the Mongoose Solomani Rim on why Thamber, Banasdan, and Lagash are subsector capitals ahead of other choices. Further, many of the new capitals – Ephimir, Eneldun, Agidda, and Twefik -- are not connected to existing X-boat routes.

 

[Garnfellow]

I think the Importance extension {Ix} to world data is one of the more useful innovations in T5; it helps establish the relative political and economic clout of different worlds. But on turning to the T5 text for clarification on assigning subsector capitals, we get at least three different and contradictory directions:

• Homeworlds (p. 80). Capitals are classed as Political codes, with the note that “Cp, Cs, Cx require Starport A.”
• The Importance Extension (p. 427). “Capitals. The most Important world in a subsector is the Subsector Capital; the most important world in a Sector is the Sector Capital. When more than one world is of the highest Importance, the one with the most Trade Classifications is considered most Important.”
• Worldgen TCS (p. 434). “Cp, Cs, Cx require Starport A. Politicals [which include Cp, Cs, and Cx] assigned by Referee (not generated).” This text is repeated on p. 496.
• World Gen Ix Ex Cx (p. 435). “The Importance Extension (Ix) ranks worlds within a region. It governs the locations of capitals and trade routes. . . . Important worlds are more likely to be Capitals of subsectors and sectors.”

So pages 434 and 496 indicate assignment of capitals is flat referee fiat, as long as we have a class A starport. Page 427 suggests assignment is determined by the Importance calculation, period. And page 435 suggests it is usually driven by Importance but subject to referee judgment, which seems like the only rational approach. I suggest amending the T5 text to at least be consistent between sections, maybe something like: "Capitals of subsectors and sectors are assigned by the referee. They always have Class A starports and are usually the most Important world in their respective region."

While the Importance extension is useful, it is an extremely coarse metric and in actuality many fine inputs would feed into what makes a subsector capital a capital: historical, cultural, and logistical inputs not captured by {Ix}. Importance changes over time but an entrenched bureaucracy can be difficult to uproot. And in the U.S., for example, many state capitals were specifically NOT established in the most important cities, making capitals notoriously difficult for schoolchildren to remember. Sacramento is no San Francisco, much less L.A.

Turning back to the changed Rim capitals, none of these seem an obvious improvement and a couple are real head scratchers. For example: Murphy over Banasdan? Murphy has the Industrial trade classification, sure, because of its crappier atmosphere, and arguably a better location. But it also has less than a fifth of the population and a lower tech level than Bansadan. Making a change here is even less desirable because we have a canonical history of how Banasdan was made subsector capital over its rival, Nisinasha, following the Rim War.

How about Agidda over Lagash? Agidda has less population, a significantly lower tech level (C vs. F), and lacks a naval base. Lagash is a garden world (no modifier to Importance), while Agidda “benefits” from its tainted atmosphere, which gives it an Industrial trade classification and an extra +1 modifier to its Importance. The change also invalidates canonical narratives explaining why Lagash was selected over Terra or other worlds.

I am all for rewriting canon when the change provides significant upside: for example, a change that cleans up an illogicality or irreconcilable contradiction, or adds some new interesting story possibility. But these changes to the Rim seem to be far more of a headache than they are worth.

Given all of this, my strong recommendation would be to roll back these changes to subsector capitals. Using Importance as a tool to identify potential capitals is great, but in the end I think it’s too coarse a metric to be the final arbiter, particularly with sectors like the Rim that have significant established canon.

 

[robject]

I think it's quite reasonable to use prior canon to identify capital worlds, leaving Importance as a referee's tool and economic input.

 

[Garnfellow]

The more I think about this, it seems like the tail is wagging the dog here. Importance shouldn't drive capital assignments, but capital assignments should inform importance. Albany isn't a capital because it is Important; it's Important because it's a capital. There are numerous canon examples of worlds vying to become subsector capitals for the prestige and economic benefits. Being a subsector capital ought to be worth a +1 boost to Importance; canny sector dukes would use this to reward loyalists and to check the power of rival nobles.

 

[inexorabletash]

And TL should drive Starport, not vice-versa.

The world generation rules are not intended to be a simulation. Capitals are important. Therefore, important worlds are more likely to be capitals. There is correlation and causality... even if the generation causality direction doesn't match realistic causality.

 

[Ulsyus]

While the Importance extension is useful, it is an extremely coarse metric and in actuality many fine inputs would feed into what makes a subsector capital a capital: historical, cultural, and logistical inputs not captured by {Ix}. Importance changes over time but an entrenched bureaucracy can be difficult to uproot.

I agree with you. Another point is that Traveller is meant to be a set of rules that can be used in any setting, not just the 3I. If you consider that, then the Importance rules are pretty useful when generating values to derive capitals in YTU, but should probably be taken with a grain of salt when reading the OTU.

 

[robject]

The more I think about this, it seems like the tail is wagging the dog here. Importance shouldn't drive capital assignments, but capital assignments should inform importance.

I used to think this. In fact, I had a mechanic that did this. It also awarded points to worlds on the x-boat route. But it turns out to be a self-fulfilling prophecy, and the value quickly loses its meaning.