Skip to content

Release 3.3.0#486

Merged
GQuantrill merged 8 commits into
mainfrom
release
Jul 18, 2026
Merged

Release 3.3.0#486
GQuantrill merged 8 commits into
mainfrom
release

Conversation

@GQuantrill

Copy link
Copy Markdown
Owner

Promotes release to main for the 3.3.0 minor release.

What's new

Don't track K-space (opt-in)

A new Tracking section in the map settings (right sidebar) with an opt-in "Don't track K-space" toggle. When it's on, auto-mapping stops cluttering your map with the empire systems you gate through: it records only the K-space system you first jump into from wormhole space, and the last one before you jump back into a hole — everything in between is skipped, and those edge systems connect only to their wormholes. Hi-sec, low-sec and null-sec only; Pochven is always kept.

Bookmark format fixes

  • {dest_type} now shows the destination class (e.g. C2) again, instead of accidentally showing a hole's pinned destination system.
  • New {leads_to} token for your bookmark format — puts the actual leads-to (a specific system like J110555, or the class/band you set) in the bookmark name.

Version bumped to 3.3.0 (web + server). A v3.3.0 GitHub release/tag will be cut after merge.

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
Release: don't-track-K-space option + bookmark token fix
@GQuantrill
GQuantrill merged commit e33013c into main Jul 18, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant