Traveller Trade Tool

Here is v1.4.1. The major changes are as follows:
  • Added a subsector map on the 'Input' tab. This shows all subsectors adjacent to the purchase sector, as well as all adjacent subsectors and their corresponding sectors.
  • Updated lookups on 'Input' tab to filter system info based on system name and hex ID; updated lookups on 'Mapping' tab to filter system info based on subsector name and system name. (This should fix problems if there are multiple systems with the same name.)
  • Updated jump distance calculations. (This should fix problems with the jump distance calculations.)
Thanks, as always, for the feedback!
 

Attachments

I'll be giving this a test drive soon, but I want to suggest a minor tweak. The freight section on the Purchases tab has the Tons in Lots section overrunning the input area of the Tons Taken area. Perhaps swap them around?

1763249615323.png
 
Last edited:
Working a lot better but I did find one glitch. The tool shows Marilithe in the Diaspora Sector, but it doesn't exist there. It's in the Massilia Sector.

1763843379821.png1763843448185.png
 
Found a second phantom system. Nobody isn't in the Diaspora Sector. Neither is Wawarbinner. However, it looks like ICA, Nape, and Mana are, though they don't show on the map. There are a lot of discrepancies and that's only on the course I selected. Diaspora has some real issues. I'm stopping my testing as I can't be sure what is really there.

1763865263214.png1763865290313.png
 
Found a second phantom system. Nobody isn't in the Diaspora Sector. Neither is Wawarbinner. However, it looks like ICA, Nape, and Mana are, though they don't show on the map. There are a lot of discrepancies and that's only on the course I selected. Diaspora has some real issues. I'm stopping my testing as I can't be sure what is really there.

View attachment 6701View attachment 6702
It's been more than a month, so I thought I would poke this to see if you have any insight into this and maybe a fix for it somewhere in the pipeline. I appreciate the sheet, but Diaspora is unusable this way. It has the correct data listed for the systems, but the map in the sheet doesn't reflect that. I'd wager there are other sectors with the same issue that the fix for this could correct. Help!
 
Sorry, no. I haven't had any time to work on it. In the meantime, I would recommend using travellermap.com as the source for your map. There is a link to that site in cell C35 on the 'Input' tab. It opens directly to the purchase system you have selected.

If I continue having difficulties, I may end up just removing the Excel map. The purpose of the file is to automate the trading process presented in the core rules. This it does (as far as I can tell). The Excel map is nice to have; however, it is not necessary to achieve the goal of the file. We already have an excellent and far better map at travellermap.com. Also, the Excel map has also made the file unstable and has been causing crashes recently, at least on my end. (Although my computer has been having other instability issues, so the file may not be the sole cause of the crashing.) If I figure out how to remove all the bugs, I will keep it; otherwise I may remove it to keep the tool as functional and focused as possible.
 
Sorry, no. I haven't had any time to work on it. In the meantime, I would recommend using travellermap.com as the source for your map. There is a link to that site in cell C35 on the 'Input' tab. It opens directly to the purchase system you have selected.

If I continue having difficulties, I may end up just removing the Excel map. The purpose of the file is to automate the trading process presented in the core rules. This it does (as far as I can tell). The Excel map is nice to have; however, it is not necessary to achieve the goal of the file. We already have an excellent and far better map at travellermap.com. Also, the Excel map has also made the file unstable and has been causing crashes recently, at least on my end. (Although my computer has been having other instability issues, so the file may not be the sole cause of the crashing.) If I figure out how to remove all the bugs, I will keep it; otherwise I may remove it to keep the tool as functional and focused as possible.
Understood. Thanks. As long as the right systems show up as selectable, that would work
 
Sorry, no. I haven't had any time to work on it. In the meantime, I would recommend using travellermap.com as the source for your map. There is a link to that site in cell C35 on the 'Input' tab. It opens directly to the purchase system you have selected.

If I continue having difficulties, I may end up just removing the Excel map. The purpose of the file is to automate the trading process presented in the core rules. This it does (as far as I can tell). The Excel map is nice to have; however, it is not necessary to achieve the goal of the file. We already have an excellent and far better map at travellermap.com. Also, the Excel map has also made the file unstable and has been causing crashes recently, at least on my end. (Although my computer has been having other instability issues, so the file may not be the sole cause of the crashing.) If I figure out how to remove all the bugs, I will keep it; otherwise I may remove it to keep the tool as functional and focused as possible.

The map is a fun little tool though.
 
That's kind of fun. Where is that tool to be found?
Here on this very forum.

 
Here on this very forum.

Thanks!
 
I had an inspiration this morning! Try this. Here is v1.5. The major changes are as follows:
  • Added code using arrays to generate lists of values for various tables of system info. This avoids the use of formulas which take much longer to calculate. The system box and map codes should be much faster now.
  • Updated map to get info from list of data for local subsectors, rather than the entire data set. This should clean up errors of systems showing in the wrong place on the map.
    • The local subsectors are the subsector for the purchase system, and all adjacent subsectors.
    • The map uses hex ID as the basis for the look-up.
    • Hex IDs only repeat every four subsectors and the list only covers two adjacent subsectors. So there should be no duplicate hexes in the list of systems for local subsectors.
Hopefully that helps.
 

Attachments

I had an inspiration this morning! Try this. Here is v1.5. The major changes are as follows:
  • Added code using arrays to generate lists of values for various tables of system info. This avoids the use of formulas which take much longer to calculate. The system box and map codes should be much faster now.
  • Updated map to get info from list of data for local subsectors, rather than the entire data set. This should clean up errors of systems showing in the wrong place on the map.
    • The local subsectors are the subsector for the purchase system, and all adjacent subsectors.
    • The map uses hex ID as the basis for the look-up.
    • Hex IDs only repeat every four subsectors and the list only covers two adjacent subsectors. So there should be no duplicate hexes in the list of systems for local subsectors.
Hopefully that helps.
Thanks! I’ll give it a test drive tomorrow.
 
I'll give it a better run later today, but it looks good at first blush.

One thing I can't tweak because I don't have a clue how macros work is rearranging where the input and output is on this part that is in the screenshot. I want to move the Tons Taken to the left so the input isn't buried under the numbers for Tons in Lots, but I can't because I'm clueless. I suggest you make that change.

If you wanted to toss in a brief primer on how the macros work, I wouldn't complain and then I could potentially stop bugging you for tweaks. ;)

Also, a total of the available freight would be helpful so you can see how much is there. It could go to the right of # Lots.


Never mind! I solved the macro issues I was having and educated myself. It now looks and acts the way I want, though I'm sure my alterations to the macros were a kludge because I couldn't figure out how to run the summing formula directly in the macro and had to add a cell in the trade sheet to reference. A screenshot of the updated data in now in my next post along with the updated sheet.1767108881341.png
 
Last edited:
Back
Top