Mixed-edge routing
A BFS over the union of jump-drive and stargate edges builds the shortest path, mixing capital jumps with gate hops where it helps.
Mixed jump-drive + stargate capital routes
Plan a capital route mixing jump drive and stargates, with intermediate waypoints and total jump-count computation. The algorithm is a Dijkstra/BFS variant over the union of the stargate graph (from the SDE) and the jump-drive graph (computed dynamically).
Schematic mockup — the real tool is interactive
Set where you start and where you end
Optional mid systems force the path through them
Hull class and JDC fix the max range
Get the leg sequence and total jump count
A BFS over the union of jump-drive and stargate edges builds the shortest path, mixing capital jumps with gate hops where it helps.
Each waypoint is computed as its own segment then stitched together, with the full chain reported as a single total jump count.
Any hop can be re-routed: open Alternatives for nearby jump targets, or scan local stargates to convert a leg into a gate jump.
Every step is labelled stargate or jump-drive with its LY delta from the previous system, so fatigue planning stays explicit.
The route sequence flags security, NPC stations and daily/recent kills per system, surfacing hot grids before you commit the jump.
Origin, destination, mid-waypoints, hull class and JDC are packed into the URL, so the link recomputes the identical path on load.
Rotatable pseudo-3D camera
Top-down d3 pan/zoom
Combines stargate and jump-drive graphs: finds the fastest route using both.
Every segment is labelled as gate jump or jump drive, with system, region, light-year distance and security status.
Add intermediate waypoints and the planner optimises the route through each in the given order.
JF, Industrial, Dread, Carrier, FAX, Super, Titan, Black Ops.
Total jump count, taking into account the maximum range of the chosen ship class.
Yes, by adding intermediate waypoints: the planner passes through each in the given order.
Stargate-traversed systems show security status; for capital jumps the planner auto-filters non-jumpable systems.