Sunday, December 16, 2018

Traveller Map API, Trade Routes

Still cannot overlap routes, but switching from the MSEC format to the XML format for the metadata gives me more options. I can have dashed routes (no idea why it was dashed - I think when I did this originally I was just going for interesting looking!), custom allegiance codes, regions, more fun stuff.

I really need to get back to my ship tracking program, probably start over yet again and not go the UWP route. Go with a simpler installer maybe. And really clean up the cargo stuff: I was integrating 3 different systems and it did not come together well. After doing all that, I think a better schema can be made that incorporates all three systems into a single table.

Basically, a cargo is only a few core things:

  1. Minimum volume (dTons)
  2. Maximum volume
  3. What is it? In Classic and Mongoose, this matters. T5 seems to gloss over it and everything is the same price from the same system for the same volume. Hate that....
  4. Base purchase price
  5. D66 roll (Classic and I think Mongoose, but I've not paid enough attention to Mongoose). This would allow for rolls on the cargo table to only be those specified in the rules. 
For the ship, the above is part of the ship's cargo, which would have:
  1. cargo ID
  2. cargo code
  3. lot size (dTons)
  4. purchase date
  5. purchase system
  6. purchase price
  7. sell date
  8. sell system
  9. sell price
Tricky part is the cargo code. I do have a masochistic preference for the BITS cargo codes as there is a lot of room for adventure there. T5 has its own way of doing things, so the cargo code is based on the version played. T5's code is actually fairly easy to calculate, it is just boring. So I may have both the T5 code and the BITS code. So a cargo listing could look something like:

Cargo dTons Purchase World Purchase Price Purchase Date Cargo Code Selling World Selling Price Selling Date
Gems 5 D'Arlee 100000 110-1105 C-Ri Cr100000 3225683-42244A41-[100-160-320-70]-(0)

Which, if you read the code, may indicate that for some reason or another this is actually a hazardous cargo. Hope your steward / cargo master knows the codes (digression: there was an interesting conversation about cargo management on COTI, and if it should be a new skill. I prefer the steward skill to cover that rather than yet another, pretty specialized skill).

Anyways, my revised trade map:

No comments: