SectorMaker

October 25, 2020

New: • Added a major new feature. You can now search a specific era (milieu) on TravellerMap, get a list of defined sectors for that era, and import that sector's data and metadata for reference or editing. Notes on imported data: • If any of a world's characteristics contain question marks for the codes, the characteristic is created with a value of zero instead. • World type is set to "planet" unless the Locked or Satellite remarks exist. In this case, the satellite orbit is set to the median value. Planet orbit is calculated randomly according to the standard rules. • World habitable zone value is set to normal unless the Cold, Hot, Frozen, Tropic, or Tundra remarks exist. • Alien race names and associated population percentage code in the remarks is ignored except in the case of an extinct alien race. • In the case of multiple stars, the second is assumed to be the primary companion, the third is assumed to be close, the fourth is assumed to be the close companion, etc. • Special case stars, BD (brown dwarf), BH (black hole), and NS (neutron star) are imported and displayed properly, but can't be created normally. • Style sheet data is ignored, so some items appearance may vary from TravellerMap, but this can be edited after import. • Indefinite length data such as a world's Name, Bases, or Nobility may be truncated. • Base codes are shown in the system data string on the World view and displayed on maps, but may not be valid for editing on the World view due to T5 rules for valid codes. • Imported data from Travellermap is subject to change at any time. Variations in the import data format may cause a crash or the inability to update maps. If this occurs, let me know what sector and era is causing the problem and I'll update the app. Changes: • Removed the requirement for Cy or Mr trade codes to exist in order to display an O: owner code hex number in the Remarks. • Newly created Allegiances now indicate what sector they belong to. • Deleting a sector now deletes all allegiances created for, or imported with, that sector. Define new allegiances for each sector instead of using an existing one. If you have more than one sector with the same name, deleting one will delete allegiances for all of them.