You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
ifsolar, 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
The text was updated successfully, but these errors were encountered:
Description
Relevant discussion
in systemps_mapped/systems.go
I have already parsed System entity
That lists... jumpholes to other systems
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
fl-darkstat/darkstat/configs_export/trades/trade_routes.go
Line 227 in f2ffe60
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
The text was updated successfully, but these errors were encountered: