Another System Generator: As Above So Below

[Terry Mixon]

Fantastic to hear. And I agree. I wanted the filter for my own custom trade routes I plan to build.

Travel Zone filters are easy and I will look at them next. The only thing stopping me from making a filter for everything was thinking up the UI for a super long list. But I knew I would end up there.

Anything else helpful for anyone? # belts? Cx or Ex values?

I'd wager the belts would be helpful to some. Honestly, you're going to have people wanting to filter on all kinds of things.

Right now, the filter controls look like this:



You could easily subdivide things when they get to crowded to make it easier to see by doing like Advanced Data and Advanced Styling Rules to have it expand.

 

[mavikfelna]

Being able to open a system in a pop-up window or side bar and see the full extended system info would be nice. If it's an existing system on Travellermap, pulling up the data sheet from there would be helpful. But the extended system information is useful for planning development or plotting trade routes.

 

[bartlebyfosco]

Being able to open a system in a pop-up window or side bar and see the full extended system info would be nice. If it's an existing system on Travellermap, pulling up the data sheet from there would be helpful. But the extended system information is useful for planning development or plotting trade routes.

If you control+click a hex you get the basic details, with a button on the bottom of the window that let's you expand the system details.

Is that what you mean?





Of course the extended data in the TravellerMap is limited, but if you build out a mongoose generated system using the full generation down to the moons you can see that too.

One idea is to take the OTU sector from Travellermap and expand the full system using the Mongoose engine. It sort of works now. But is not tested.

 

[mavikfelna]

If you control+click a hex you get the basic details, with a button on the bottom of the window that let's you expand the system details.

Is that what you mean?

View attachment 7906



Of course the extended data in the TravellerMap is limited, but if you build out a mongoose generated system using the full generation down to the moons you can see that too.

One idea is to take the OTU sector from Travellermap and expand the full system using the Mongoose engine. It sort of works now. But is not tested.

View attachment 7907

Yes, that's what I was looking for. Thank you.

 

[bartlebyfosco]

I would. By filtering it, I would only see the valid ports of call. I don't have to interpret what zones they are. Blank means nothing valid there. A visible system means a valid port of call.

I only just realized this morning that my import was not importing Travel Zones at all! Everything was Green!

So version 0.7.2 was pushed into production this morning:

1. Fixed Travel Zone import bug
2. Added filters for Belts and Travel Zones (use R, A, or G)
3. Updated Filter UI to make room

As always new changes introduce the risks of new bugs, so please let me know if you see anything that is not working. And as always anyone who uses it is welcome to make a request to make it better for their game.

Normal caveats apply - free software, still in development, blah blah blah.

Updates I have on my list in no particular order:
- Added generation engines for Architect of Worlds and Cepheus Universal
- Export sectors into Obsidian (and other markdown readers)
- More customizations on look and feel