Release: don't-track-K-space option + bookmark token fix#485
Merged
Conversation
New per-user Tracking option (right sidebar > Tracking) that declutters K-space from auto-mapping. When on, only the K-space systems bordering a J-space jump are recorded: - the first K-space system entered from J-space (the wormhole exit), and - the last K-space system before jumping back into J-space (added retroactively at that jump). Everything gated through in between is skipped, and the two edge K-space nodes connect only to their wormhole neighbours (no gate lines between them). HS/LS/NS only; Pochven is always tracked. Client-only (auto-mapping is entirely client-driven): useLocationTracking now remembers the previous PHYSICAL system so it can see the departure class and retroactively add the last K-space. Setting nexum.tracking. skipKspace (default false = today's behaviour). New 'Tracking' sidebar section + i18n across all 9 locales.
feat: opt-in 'don't track K-space' tracking option
The 'don't track K-space' logic lived in useLocationTracking, but
nexumDebug.simulateJumps called applyJump directly — so the simulator (and
only the simulator) ignored the filter and still tracked every K-space hop.
Extracted the filter into a shared applyTrackedJump(curr, prevPhysical,
prevAnchor, {skipKspace, canAdd}) used by BOTH the live tracker and the
simulator, so simulateJumps now reproduces exactly what real flying
records. The simulator tracks the previous physical system + connection
anchor and logs skipped K-space hops.
…lator fix: apply the skip-K-space filter to the jump simulator too
{dest_type} resolved to whLeadsTo || wh.dest, so a hole pinned to a
specific system showed that system (e.g. J110555) instead of a class —
despite being labelled 'Destination class'.
- {dest_type} is now the destination CLASS via whDestClass (the type's
charted dest, e.g. D364 -> C2), falling back to the leads-to only when
it's itself a class/band (a K162 tagged 'C4'), never a pinned system.
- New {leads_to} token carries the raw leads-to: a pinned system
(J110555) or the class/band the user set.
So '{sig} {dest_type} {type} {age}' now gives 'ABC-123 C2 D364 0h', and
'{leads_to}' adds the specific destination. Existing formats using
{dest_type} to show a pinned system should switch that token to
{leads_to}.
fix: bookmark {dest_type} shows destination class; add {leads_to} token
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes
qatorelease.Don't-track-K-space tracking option (#482, #483)
New per-user opt-in under a Tracking heading in the right sidebar. When on, auto-mapping records only the K-space systems that border a J-space jump — the first one entered from J-space and the last one before jumping back into J-space — skipping everything gated through in between. HS/LS/NS only; Pochven is always tracked. #483 routed the jump simulator (
nexumDebug.simulateJumps) through the same shared filter so it reproduces live behaviour.Bookmark format fix + new token (#484)
{dest_type}was showing a hole's pinned destination system (e.g. J110555) instead of its destination class. It now resolves to the class from the wormhole type (D364 → C2), and a new{leads_to}token carries the pinned system / class-band the user set.All merged via CI-green PRs.