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

Feat: list Systems with jh connections to other ones #101

Open
dd84ai opened this issue Feb 2, 2025 · 0 comments
Open

Feat: list Systems with jh connections to other ones #101

dd84ai opened this issue Feb 2, 2025 · 0 comments

Comments

@dd84ai
Copy link
Member

dd84ai commented Feb 2, 2025

Description

  • Output in darkapi route that exposes all existing Systems
  • And for each system list present jumpholes
  • and for each jh print its archetype, to which system it leads, if it is dockable, dockable by transport, name and any other useful stuff

Relevant discussion

in systemps_mapped/systems.go

type System struct {
    semantic.ConfigModel
    Nickname           string
    Bases              []*Base
    BasesByNick        map[string]*Base
    BasesByBases       map[string]*Base
    BasesByDockWith    map[string]*Base
    AllBasesByBases    map[string][]*Base
    AllBasesByDockWith map[string][]*Base
    Jumpholes          []*Jumphole
    Tradelanes         []*TradeLaneRing
    TradelaneByNick    map[string]*TradeLaneRing

    MissionZoneVignettes []*MissionVignetteZone

    MissionsSpawnZone           []*MissionPatrolZone
    MissionsSpawnZonesByFaction map[string][]*MissionPatrolZone

    Asteroids   []*Asteroids
    ZonesByNick map[string]*Zone
    Objects     []*Object
    Wrecks      []*Wreck
}

I have already parsed System entity
That lists... jumpholes to other systems

type Jumphole struct {
    semantic.Model
    Nickname  *semantic.String
    GotoHole  *semantic.String
    Archetype *semantic.String
    Pos       *semantic.Vect
    IdsName   *semantic.Int

    System *System
}

jumpholes define their connection by mentioning Another Jumphole nickname
Soooooo... if desired i can expose entity system that has listed its jumpholes
but
it is awkward
there are many extra conditions hmm

if solar, ok := configs.Solararch.SolarsByNick[jh_archetype]; ok {

full list is visible there
Basically System is Connected to another system by Jumphole
Darkwind The Dark Duck — Today at 2:03 AM
only if the Jumphole is having Docking Sphere to be docked
And Not listed in Initial World Locked Gates
And Not Invisible
And if we check if for Transports, it also needs to have Dockable by Caps docking spheres 😅
rwx — Today at 2:04 AM
this includes gates as well?
Darkwind The Dark Duck — Today at 2:04 AM
yeah, i simplified and named Jumpgates as still jumpholes, everything is jumphole: Jumphole, Jumpgate and even Atmospheric point
rwx — Today at 2:05 AM
do they have another archetype? so I can differ them
Darkwind The Dark Duck — Today at 2:05 AM
They should be having different archetype yes
So largely this info will be useless for you unless accounting for all those extra conditions i believe
which requires plentiful data combining
i guess as minimal way it can be outputed as
System with arrray of jump hole
For each jumphole just printing archetype, if locked in initial world, if dockable? and if dockable by transport
And obviously we shoudl be desired printing jumphole leads to which system nickname
it sounds as rather useless info to me though, far better would be actually just grabbing Sorted bases by distance
unless u wish to just include all nearby system bases within your range
regardless how far they are

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant