System Architecture & Logic
The operational core of Nav-Fi³ 2300AD is the Star Route Engine, built on a static catalog of real StarSystem coordinates (NSL survey data) rather than a live external map service. Every route stored in the system is a graph of jump vectors along the StarLane network — precomputed once, not fetched on demand.
The architecture is still built on Navigational Determinism: once a route is compiled and validated, its physical parameters (coil discharge, transit time, distance) become immutable until manual recalculation or link termination.
Technical Specs
Data Synchronization Logic
Calculated from real 3D StarSystem coordinates (x/y/z), in light-years, against the 7.7 ly Stutterwarp jump threshold.
612 charted StarSystems, connected wherever two systems fall within jump range — 198 reachable from Sol's main network, the rest isolated in disconnected clusters.
Shortest-path routing over the StarLane graph, driven by the asset's Stutterwarp efficiency rather than a fixed drive rating.
Tracks the Stutterwarp drive's charge state across jumps — repeated long jumps require discharge time before the coil can engage again.
Nav-Link Status Lifecycle
The system operates in two mutually exclusive modes tied to the navigation hardware. Understanding the transition between these states is vital for crew safety.
PLANNING_MODE
- Mutable Waypoints
- Dijkstra Recalculation
- Manual Cursor Sync
- Discharge Simulation
NAV_SYNC_ACTIVE
- Immutable Vector Graph
- Transit Control HUD
- Real Transit Time (Distance ÷ Efficiency)
- Bookmark Auto-Update
Operational Protocols
Protocol Delta: Manual Cursor Sync
When the route is inactive, the navigator has exclusive access to Set Bookmark. This function instantly synchronizes the virtual position with a waypoint loaded in the table.
Use this function strictly to realign the Nav-Computer in the event of forced jumps, stellar emergencies, or when the vessel is towed off-course.
COMMAND Execute: Set Bookmark on NODE_CURRENT. Success.
Protocol Epsilon: Transit Execution
Executing a jump (Transit) triggers a sequence of atomic operations synchronized with the Stutterwarp coil:
- 01. Leg Distance Calculation
- 02. Coil Discharge Lock Check
- 03. Real Transit-Time Leap (Distance ÷ Efficiency)
- 04. Bookmark State Persistence
Protocol Zeta: Logistics Integration
The navigation system is bi-directionally linked with the Cargo Hold Management System.
- Automatic Origin Logging (Loot)
- StarSystem-Aware Liquidation Lookup
- JIT Tonnage Definition
Every transit waypoint acts as a potential Liquidation Terminal. Note that Tactical Controls (Recalculate, Transit, Bookmark) require deployment on a linked Asset. Players have a read-only perspective of the current flight plan to maintain focus on survival and roleplay.
Advanced Diagnostics
"COIL DISCHARGE LOCK: discharge time required before the drive can jump this leg again."
This error state blocks transit execution. It indicates the Stutterwarp coil has not had enough discharge time since the last jump to safely engage the next leg.
Correction Matrix
The discharge preview shows the exact hours remaining before the coil can safely engage again — advance the session date past that window before retrying.
Engage the RECALCULATE subroutine. The system will query the StarLane network and automatically inject intermediate StarSystem nodes, breaking an oversized leg into shorter, safer jumps.
Other Known Interrupts
- NAV-LINK CONFLICT — an active navigation session already exists for this asset.
- NAV-SYNC ERROR — waypoint synchronization failure, no active waypoint set.
- ASTROGATION ERROR — target coordinates out of range, or destination already reached.
- NAV-COMPUTER LOCK — Stutterwarp efficiency (ly/day) is required for transit tracking; set it on the route edit page.
// SECURE TERMINAL END // ALL DATA COMPLIANT WITH COLONIAL NAVAL CODE //