T5SS: Travellermap.com Update

[DonM]

There's been an update of the data on travellermap.com. The Aslan sectors remain in draft mode, expect more changes, but the Imperial worlds should now be solid (as solid as can be until a book is published that covers a sector, of course).

Glaring problems are mostly likely mine, not travellermap.com.

 

[whulorigan]

"Booklet Maker" function not working

The "Booklet Maker" function on Traveller Map is apparently no longer functioning (or at least it is not on my end).

 

[tjoneslo]

The "Booklet Maker" function on Traveller Map is apparently no longer functioning (or at least it is not on my end).

Which sector(s) were you trying? I've done a few (Spinward marches, Core, Dagudashaag) and they all seem to work fine.

 

[inexorabletash]

The "Booklet Maker" function on Traveller Map is apparently no longer functioning (or at least it is not on my end).

Reminder: when reporting a problem, please include the steps you're following, what you're expecting to see, and what you're actually seeing. In most applications there are many paths into a particular piece of functionality and the problem may be specific to the steps you're following.

I just fixed an issue affecting these steps:
* Go to http://travellermap.com/poster
* Select "Aktifao" from the drop down
* Click "Compose Booklet"
Expected: booklet produced
Actual: Giant error with unformatted HTML, including "Object is null"

Hopefully that's the glitch you were seeing. As noted in the blog post http://travellermap.blogspot.com/2014/05/t5ss-data-update-aprilmay-2014.html there was a LOT of code churn necessary to support the new allegiance codes so I'm not surprised bugs crept in. Please let me know if you spot any others!

 

[inexorabletash]

The Aslan sectors remain in draft mode, expect more changes...

And hence I've marked them as "Unreviewed" on the site, so hopefully it's somewhat clear to users that there is churn expected. (Adding a "Review in Progress" state is probably overkill, but I can do so if needed.)

 

[whulorigan]

I just fixed an issue affecting these steps:
* Go to http://travellermap.com/poster
* Select "Aktifao" from the drop down
* Click "Compose Booklet"
Expected: booklet produced
Actual: Giant error with unformatted HTML, including "Object is null"

Hopefully that's the glitch you were seeing. As noted in the blog post http://travellermap.blogspot.com/2014/05/t5ss-data-update-aprilmay-2014.html there was a LOT of code churn necessary to support the new allegiance codes so I'm not surprised bugs crept in. Please let me know if you spot any others!

It seems to be working fine now.

 

[whulorigan]

Subsector Capitals & Dukes

There's been an update of the data on travellermap.com.

However, Aramis is NOT the only subsector in the Marches to not have a capital in the T5SS... Jewell and Vilis subsectors lost their subsector capitals as well. Both are administered from Regina.

I am rather curious as to why Lanth does have a Subsector Capital. It is a low population backwater, whose "capital" (Lanth) is one of 4 worlds with Importance Ix = +2 (the highest level in the subsector). Lanth would not otherwise even rate a Lesser Duke (C6/Soc=f), which requires minimum Importance Ix = +4 (as all other Subsector Capitals in the Spinward Marches have). In fact, no worlds in the subsector rate either a Lesser Duke or even a Count. Extolay, Treece, and Equus are the most significant worlds (meriting Viscounts), and Lanth itself otherwise merits nothing greater than a Knight.

Seems to me that Lanth would be an ideal candidate for a subsector to be administered from elsewhere.

GT:Nobles does not give it a duke. My take is that Lanth is divided between the duchies of Regina, Rhylanor, and Lunion.

It still has a subsector capital, though.

Perhaps the solution would be that subsectors with Ix<4 have a "Subsector Capital" as a regional administrative center, but do not qualify for a Subsector Duke until the Importance is raised to Ix=4? Such subsectors may fall under the jurisdiction of a neighboring Duke, or have a lesser noble (Marquis - Count) appointed as regional administrator/overseer in the interrim?

Well, according to the new T5SS Data, we have some updates* on this discussion from the [FONT=arial,helvetica]T5SS Semi-Official Thread :
* - (NOTE: I am not implying that these are problems, but simply noting the changes since we had talked about them previously)

- Aramis Subsector once again has a [/FONT][FONT=arial,helvetica][FONT=arial,helvetica]Subsector Capital at[/FONT] Aramis/Aramis [/FONT][FONT=arial,helvetica][FONT=arial,helvetica](like it used to be in CT)[/FONT], but does NOT have a Subsector Duke (C6/Soc=F) associated with it;

- The capital of Vilis Subsector has been designated as Frenzie/Vilis (like it used to be in CT), but Frenzie does NOT get a Subsector Duke (though Vilis/Vilis still has a world-duke [[/FONT][FONT=arial,helvetica][FONT=arial,helvetica]C6/Soc=f][/FONT]);

- Lanth Subsector still has a Capital at Lanth/Lanth, but has lost its Subsector Duke.

[/FONT]

 

[whulorigan]

Sol Subsector Capital

There's been an update of the data on travellermap.com.

The Capital of Sol Subsector has been moved from Lagash to Agidda (presumably because it is a more important world). But note that Agidda has NO X-Boat Routes currently going to it.

 

[savage]

Now Depot Corridor is a TLD world. Are we going backwards.

I'd rather see UWP adjusted to meet a logical plan by the Navy.

 

[inexorabletash]

FYI, I just tossed another feature up under the settings (gear) menu. You can now "Dim Unofficial Data" - anything that hasn't gotten the "final" T5SS seal of approval is slightly grayed out.

It's not on by default. It's a quick hack but looks kinda pretty.

 

[DonM]

Several notes here...

Depots: Marc agreed to some changes, but 1) no illegal TLs, and 2) several are placed for political reasons, and the Navy makes do.

Lanth: Sigh. My theory is that it's used to spy on the Swordies. And yes, you can have a subsector capital without a subsector duke.

Xboats: They are going to get reworked at some point.

Priority: Marc told me to do Aslan first. That's why we're working on those sectors.

 

[Nonespecial]

inexorabletash - Just a heads up. I could be doing something wrong but whenever now whenever I enter T5 tab delimited data into the "Sector Data" text entry area with Poster Maker it does not show the actual worlds entered in as part of my data. This used to work fine even up until just a couple of days ago, and I even tried using an older version of a tab delimited T5 file that I am pretty sure worked. I tried all sorts of different options in Poster Maker but none seemed to work. The routes from MSEC files still show up just fine, and I was able to get Poster Maker to show the world data from a standard SEC file but wanted to let you know about this just in case there could be a problem somewhere.

When I try to use the tab delimited T5 file in Booklet Maker it seems to do the same thing (I'm assuming it calls the same exact APIs as Poster Maker so I'm not surprised) and in the sections on Subsectors it says that the subsector "... contains no charted worlds." I am guessing that maybe something is "broken" now with how the T5 tab delimited files are getting read? I even tried testing just a single world and it was no good.

Anyway, I very much appreciate you, Don's, and everyone else's efforts working on travellermap.com and the http://heldenhaufen.de/T5/ sites. They are terrific and really help to add to my Traveller experiences. Thanks again for all you (and everyone else) is doing. Hope this didn't come across as complaining - I'm simply letting you know that I *think* I found a bug and wanted to let you know about it.

Hopefully the problem is that it is incredibly late, I should be in bed sleeping instead of staying up late building Traveller subsectors, and I'm just doing something wrong...

 

[inexorabletash]

inexorabletash - Just a heads up. I could be doing something wrong but whenever now whenever I enter T5 tab delimited data into the "Sector Data" text entry area with Poster Maker it does not show the actual worlds entered in as part of my data.

Thanks - I believe this is fixed now. I was rejecting unknown allegiance codes - including the 2-letter codes likely in your data - while validating the T5SS data. I've removed that restriction in the live site. There may be similar glitches - keep the bug reports coming!

Note that T5Col and T5Tab files are now expected to use multi-character base codes when necessary instead of the old 'A' = N+S, etc. So 'A' will show up as a "unknown" base type in renders. Legacy SEC files will automagically convert.

 

[Nonespecial]

Thanks - I believe this is fixed now. I was rejecting unknown allegiance codes - including the 2-letter codes likely in your data - while validating the T5SS data. I've removed that restriction in the live site. There may be similar glitches - keep the bug reports coming!

Note that T5Col and T5Tab files are now expected to use multi-character base codes when necessary instead of the old 'A' = N+S, etc. So 'A' will show up as a "unknown" base type in renders. Legacy SEC files will automagically convert.

Working now - thanks! However, I'm now finding that some systems are not showing up when they seem to have stellar data for stars with dwarf size (except brown dwarf - BD - works).

For example: With no other changes, "M6 V" works but "AD" does not (but worked previously). Also, thinking it now required a stellar size I have tried "A0 D" but it seems like any star type of size D that isn't just an entry for Brown Dwarf (BD) does not work. I am not sure if this is due to an intentional format change (and maybe the previous way shouldn't have worked to begin with) or if it is a new bug. I could have created my stellar data incorrectly but it used to work so I just don't know if it never should have worked to begin with or if there is some new bug.

Thanks again - love the site and thanks for all you are doing.

 

[Nonespecial]

Not sure if it helps but I'm mostly getting my sector information from the SectorMaker section on the http://heldenhaufen.de site. That site builds out stellar data by following the strict T5 stellar creation rules but so stellar size is not included for D size stars, and there are also LD stars (even though stellar size L seems to not be an option in the original T5 rules) - but all of this worked earlier on travellermap.com

Thanks.

 

[DonM]

There are no "LD" stars in the T5SS data... Just "D" and "BD".

 

[inexorabletash]

Working now - thanks! However, I'm now finding that some systems are not showing up when they seem to have stellar data for stars with dwarf size (except brown dwarf - BD - works).

Also fixed. This was another case where I was enforcing rules for official data where I should let user data be sloppy.

There are others but those haven't changed, so I'll keep them strict. Giving better feedback on invalid data is on the "to do" list.

 

[Nonespecial]

There are no "LD" stars in the T5SS data... Just "D" and "BD".

That explains why it stopped working with the restrictions in place. So I'm kind of glad it happened now so I know to go and fix my sector's data. I thought the "LD" stars looked kind of funny when I was perusing the results of the random sector generator I used but I figured maybe I was missing something somewhere in the T5 rules or errata and didn't think much of it. Thank you for the clarification.

Also fixed. This was another case where I was enforcing rules for official data where I should let user data be sloppy.

There are others but those haven't changed, so I'll keep them strict. Giving better feedback on invalid data is on the "to do" list.

I'm not seeing the problem again with my original data but now I know I have some things to fix - the life of an RPG gm never ends. My thanks again to both of you for your wonderful sites and all of your work!

 

[Carlobrand]

...Depots: Marc agreed to some changes, but 1) no illegal TLs, and 2) several are placed for political reasons, and the Navy makes do. ...

Depot/Corridor, a naval depot in a sector with eight subsectors but enough Vargr threat to warrant 16 fleets, is tech level D for political reasons, and the Navy makes do. 19 Depots through the Imperium, and no more than 7 are TL F, with 8 TL D and 3 TL C museums. Seems like almost 2/3 are placed for political reasons.

I can understand the desire not to break the rules. With so few real threats, it may be that the Imperium finds old-tech ships adequate for the role of keeping member worlds in line while giving economic boosts to the shipyards of worlds that need it. Perhaps the fleet is equally diverse, a handy mechanism to diminish the power available to some upstart grand duke who might think to assassinate an emperor to claim the throne. It has a certain appeal for those of us who have no fondness for the MegaTrav idea of the Imperium disintegrating in a multi-sided civil war; much harder to support a civil war when the Emperor has a TL F depot in his backyard and another just 2 parsecs spinward of Core in Dagudashaad, while Dulinor settles for a D. Definitely makes it much harder to justify that course of events, which for me makes the lower tech depots very appealing.

However, I also understand that, given paradoxes like a TL D depot supporting a hotly threatened sector, there will be great pressure to ignore that piece of canon for the most controversial locations, so I don't see the effort resulting in the desired outcome in those instances. If one is insistant on hewing to the rules, one should strongly consider revisiting the situation in Corridor, perhaps spiking the population or otherwise making it possible to place a real base where it is most needed, 'cause the politics thing is going to be a hard sell for players familiar with that sector.

I'm also curious as to that rationale in light of the fact that most of the Depot worlds appear altered from their MegaTrav stats. Many law levels were altered, along with some population ratings and government types. I'm curious why the decision was taken to change those worlds, yet not to change them enough to justify a higher tech level for the depots.

...Lanth: Sigh. My theory is that it's used to spy on the Swordies. ...

???

What's wrong with Lanth?

 

[Garnfellow]

Dark Nebula Names

Many of the system names in Dark Nebula appear to have reverted to an older version based on a bad scan of the data in Solomani and Aslan. That scan included a lot of "l"s for "t"s and "i"s. Joshua had cleaned these up a while back. I think this is the whole list of reversions:

Dark Nebula 0109: Oifairouw should be Oifalrouw
Dark Nebula 0206: Eahaeahs should be Eahaeah
Dark Nebula 0305: Aiaokhek should be Aiaokheh
Dark Nebula 0609: Tahetio should be Tahetlo
Dark Nebula 0909: Syasarai should be Syasaral
Dark Nebula 1002: Oldhali should be Oldhall
Dark Nebula 1110: Oeuilyuh should be Osuilyuh
Dark Nebula 1203: Trlenamm should be Trienamm
Dark Nebula 1205: Uawelsa should be Uaweisa
Dark Nebula 1207: Hfleao should be Hfieao
Dark Nebula 1303: Elkhuihi should be Eikhuihi
Dark Nebula 1408: Hlakaoea should be Htakaoea
Dark Nebula 1505: E'loa should be E'ioa
Dark Nebula 1506: Hyeirlh should be Hyeirih
Dark Nebula 1609: Brensal should be Brensat
Dark Nebula 1705: Aowolkles should be Aowoiktes
Dark Nebula 1901: Eariure should be Earlure
Dark Nebula 2109: Tauoilals should be Tauoilais
Dark Nebula 2201: Rlndnoir should be Rindnoir
Dark Nebula 2202: Kelmung should be Kemsung
Dark Nebula 2402: Wlsu should be Wisu
Dark Nebula 2403: Wanllr should be Wanlir
Dark Nebula 2404: Mamait should be Mamalt
Dark Nebula 2903: Strava should be Strova
Dark Nebula 3008: Penrovbl should be Penrovbi
Dark Nebula 3009: Patawldmam should be Patawidmam
Dark Nebula 0117: Hleoe should be Hteoe
Dark Nebula 0120: Ealyurei should be Eatyurei
Dark Nebula 0214: Auiyelyu should be Aulyetyu
Dark Nebula 0315: Ellaorla should be Etlaorla
Dark Nebula 0612: Hliyhoai should be Htiyhoai
Dark Nebula 0613: Hiriiyse should be Hirliyse
Dark Nebula 0716: Paroiere should be Parolere
Dark Nebula 0720: Rosai should be Rosal
Dark Nebula 0811: Uloirli should be Uioirli
Dark Nebula 0817: Htaweai should be Htaweal
Dark Nebula 0916: Petle should be I'etle
Dark Nebula 0918: Ewula should be Ewuia
Dark Nebula 1014: Hweshre should be Hopeshre
Dark Nebula 1112: Oea should be Osa
Dark Nebula 1116: Merplkhnomi should be Merpikhnomi
Dark Nebula 1412: Papohlrme should be Papohirme
Dark Nebula 1418: Uslyao should be Usiyao
Dark Nebula 1512: Nlchekoralo should be Nichekoralo
Dark Nebula 1519: Eaule should be Eauie
Dark Nebula 1615: Sherarehl should be Sherarehi
Dark Nebula 1617: Monlln should be Monlin
Dark Nebula 1620: Ikharlstei should be Ikharistei
Dark Nebula 1715: Khllyw should be Khiiyw
Dark Nebula 1719: Hloa should be Hlao
Dark Nebula 1911: Lla'ouh should be Ila'ouh
Dark Nebula 1915: Kakhlsil should be Kakhisil
Dark Nebula 1918: Khoakla should be Khoakta
Dark Nebula 2017: Ftyelyar should be Ftyeiyar
Dark Nebula 2020: Olaous should be Oiaous
Dark Nebula 2111: Lkhaeal should be Ikhaeal
Dark Nebula 2216: Craln should be Crain
Dark Nebula 2218: Eholol should be Ehoioi
Dark Nebula 2317: Shlro should be Shiro
Dark Nebula 2415: Ilrlyhya should be Ilriyhya
Dark Nebula 2516: Torlsad should be Tortsad
Dark Nebula 2812: Nlnnlhrang should be Ninnihrang
Dark Nebula 2815: Merelace should be Merejace
Dark Nebula 3115: Darnlel should be Damiel
Dark Nebula 3119: Shrlmia should be Shrimia
Dark Nebula 0130: Ktealau should be Kteatau
Dark Nebula 0222: Syerakhlr should be Syerakhir
Dark Nebula 0226: Yehla should be Yehta
Dark Nebula 0227: Seiirye should be Seilrye
Dark Nebula 0321: Lyyoiy should be Iyyoiy
Dark Nebula 0329: Wuhliaweh should be Wuhtiaweh
Dark Nebula 0428: Eltaeikui should be Eftaeikui
Dark Nebula 0429: Hlyeri should be Hlyerl
Dark Nebula 0627: Ao'iyauira should be Ao'iyaulra
Dark Nebula 0630: Stofakhaii should be Stofakhail
Dark Nebula 0827: Khlyu should be Khtyu
Dark Nebula 0828: Akheariafei' should be Akhearlafei'
Dark Nebula 1023: Ftihahe should be Ftihahe'
Dark Nebula 1027: Ilkhah should be Ilkah
Dark Nebula 1127: Hlehekah should be Htehekah
Dark Nebula 1221: Troli'ih should be Troti'ih
Dark Nebula 1223: Holrhesyea should be Hoirhesyea
Dark Nebula 1427: Iyohkelh should be Iyohkeih
Dark Nebula 1428: Alearye should be Aiearye
Dark Nebula 1522: Foiselhyaluh should be Foiseihyaluh
Dark Nebula 1523: Alwal should be Aiwai
Dark Nebula 1628: Rlyikahail should be Riyikahail
Dark Nebula 1724: Syauei should be Syailei
Dark Nebula 1725: Hloklye should be Hloktye
Dark Nebula 1923: Trol' should be Troi'
Dark Nebula 1925: Lyaiah should be Iyaiah
Dark Nebula 1930: Tlylewoiw should be Tiylewoiw
Dark Nebula 2023: Ekhly should be Ekhiy
Dark Nebula 2121: Sewaiair should be Sewalair
Dark Nebula 2128: Louhtah should be Iouhtah
Dark Nebula 2223: Ekhlyeue should be Ekhiysus
Dark Nebula 2230: Troutlyka should be Troutiyka
Dark Nebula 2325: Styarolr should be Styaroir
Dark Nebula 2327: Wuslhahai should be Wusihahai
Dark Nebula 2426: Lweakhte should be Iweakhte
Dark Nebula 2525: O'awly should be O'awiy
Dark Nebula 2728: Aokhiyfti should be Aokhtiyfti
Dark Nebula 2821: Tanjerf-Nebo should be Tanjert-nebo
Dark Nebula 2829: Macarlo should be Macario
Dark Nebula 2830: Fa'her should be Fa'aher
Dark Nebula 0239: Khlyu should be Khtyu
Dark Nebula 0337: Iywaiwolu should be Iywaiwofu
Dark Nebula 0436: Alteariw should be Afteariw
Dark Nebula 0636: Suairiyw should be Sualriyw
Dark Nebula 0834: Fuihalai should be Fuihafai
Dark Nebula 0931: Airlyrlyu'eas should be Airiyrlyu'eas
Dark Nebula 0937: Uryarili should be Uryarlil
Dark Nebula 0938: Fiyhlyha' should be Fiyhiyha'
Dark Nebula 1032: Wyuyelro should be Wyuyetro
Dark Nebula 1232: Islkhas should be Isikhas
Dark Nebula 1235: Elefel'os should be Eiefei'os
Dark Nebula 1238: Teayokhlae should be Teayokhtae
Dark Nebula 1240: Oakhlyye should be Oakhiyye
Dark Nebula 1434: Oihalyo should be Oihaiyo
Dark Nebula 1439: Lkhoalreih should be Ikhoalreih
Dark Nebula 1535: Talea should be Taiea
Dark Nebula 1536: Hrollr should be Hroilr
Dark Nebula 1631: Hrikair should be Hrikalr
Dark Nebula 1637: Alheisaus should be Aiheisaus
Dark Nebula 1731: Ihlye should be Ihtye
Dark Nebula 1740: Aseflhea should be Asefihea
Dark Nebula 1939: Atoliollol should be Atoiloilol
Dark Nebula 2031: Oakhelye should be Oakheiye
Dark Nebula 2033: Eahklhkao should be Eahkihkao
Dark Nebula 2037: Tloueaelel should be Tloueaeiei
Dark Nebula 2131: Ehalriwa should be Ehairiwa
Dark Nebula 2239: Hwulwaoh should be Hwuiwaoh
Dark Nebula 2340: Yetluaya should be Yetiuaya
Dark Nebula 2432: Irlhroalea should be Irihroalea
Dark Nebula 2434: Euhlsai should be Euhisai
Dark Nebula 2435: Ulweallrlao should be Uiwealirlao
Dark Nebula 2537: Qeafowyahlulr should be Oeafowyahlulr
Dark Nebula 2540: Steahryoah should be Steahryoha
Dark Nebula 2635: Khoalao should be Khaolao
Dark Nebula 2837: Brlmate should be Brimate
Dark Nebula 2838: Olrulwos should be Olruiwos
Dark Nebula 2839: Teaolyekh should be Teaoiyekh
Dark Nebula 2936: Tua'alou should be Tua'aiou
Dark Nebula 2938: Glrrsmuh should be Gimemuh
Dark Nebula 2940: Arajfarg should be Araljarg
Dark Nebula 3033: Mlken should be Miken

Although not a reversion, I'm not sure about giving a name -- even a serial number -- to the previously unnamed, unknown Solomani prison world at hex 2601.