Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster Handling (hide or delete redundant intra-cluster links, treat clusters as entities) #336

Open
MHaroldPage opened this issue Jun 5, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@MHaroldPage
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

NB CG says this is a potential candidate for the " Special/user-call (advanced, I suppose)", and therefore not high priority.

If you generate Short Links (say up to 4ly) then the galaxy resolves into neat clusters of worlds.
image

When you generate Long Links (say 4-6ly), the clusters become connected by (call them) Cluster Exits.

This has the advantages of

  • Chunking complex information.
  • Creating a sense of narrative geography.
  • Reflecting natural political/economic boundaries
  • Creating comprehendible story or gaming environments without sacrificing 3D

However, additional Long Links usually clutter up the cluster, e.g if you have a loop of of 4 stars connected by Short Links, you get a web of long links connecting the stars:

image

Problem 1: Chart cluttered with redundant information for big scale navigation, for which it's enough to know that clusters are connected by Cluster Exits.

Problem 2: It's hard to represent a universe in which wormholes connect by the shortest route, i.e. in which intra-cluster jumps don't exist.

Problem 3: No organic way to handle or navigate clusters, which are the natural political/economic/cultural units. E.g. A cluster of 7 stars could represent several months Traveller play. It would be useful to be able to handle the cluster in isolation, except for the Long Link cluster exits.

Describe the solution you'd like
A clear and concise description of what you want to happen.

In descending order of good-to-have:

  1. Option to hide or delete intra-cluster links, e.g. skip long links for stars that are already connected. It would look something like this (red scrawls indicated Cluster Exits):
    image

  2. Option to do (1) above for a selected cluster or system, thus allowing more granular navigation without visual clutter.

  3. Option to show only a selected cluster, plus Cluster Exits.

  4. Option to treat clusters as entities, with their own database entries.

  5. "Grand Cluster view" in which each cluster is represented by a single icon, and Long Links between clusters are shown.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

No obvious workarounds occur to me, other than manually editing the map.

Additional context
Add any other context or screenshots about the feature request here.

@ljramones ljramones added this to the v0.7.3 milestone Feb 1, 2022
@ljramones ljramones added this to Needs triage in TRIPS development via automation Feb 1, 2022
@ljramones ljramones added the enhancement New feature or request label Feb 1, 2022
@ljramones ljramones self-assigned this Feb 1, 2022
@ljramones ljramones modified the milestones: v0.7.3, who knows when Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
TRIPS development
  
Needs triage
Development

No branches or pull requests

2 participants