EDLD 20261111

Added: community goals in the Missions tab

The Missions tab now ends with a Community Goals section whenever there is a
goal to show. First come the goals you have signed up for, from the journal's
own CommunityGoal list: those still running, with the time left, then those
that have finished and wait to be handed in, marked in green. Each shows its
station and system, the tier reached of the tiers it has, the number of
contributors and your contribution; once you have handed something in, your
band and the reward it pays. The list is replaced each time the game writes
it, so a goal handed in or left drops out, and a new session starts empty
because the game lists nothing at start-up when you have signed up for
nothing. After those come the goals still running that you have not signed up
for, from Frontier's companion API or, without it, Inara, with what each asks
for. The section is in the desktop window, the terminal dashboard and EDCARS,
and reaches EDAM unchanged.

Fixed: community goals from Frontier were never read

EDLD has asked Frontier's companion API for /communitygoals at every dock,
but looked for the answer under names Frontier does not use — communityGoals,
starsystem, contribution — rather than activeCommunityGoals,
starsystem_name, market_name and commander_progress. The list it kept was
always empty, and since nothing showed it, nothing looked missing. It is read
in the documented shape now, and an answer that yields no goals in a shape
other than that is noted in the diagnostic log.

Fixed: Inara's community goals request

The hourly request for the goals Inara has recorded sent its eventData as an
object where Inara's documentation asks for an empty array. Its answer was
kept but shown nowhere, so whether Inara took it was never seen. It sends the
array now, and the Missions tab redraws when an answer arrives.

Fixed: Options page names cut short in ORDER and REBEL

Opened from EDCARS dressed as ORDER or REBEL, the column of Options pages lost
the first letters of NOTIFICATIONS and SESSION MGMT. The column was a fixed
156 pixels, enough for those names in EDCARS's own dress, but the two consoles
space their letters wider, and the names needed 163 and 169. The column now
widens to its widest page name, and the buttons under the pages move with it.

Fixed: a newer release could go unannounced

EDLD asked GitHub for the latest release once, on a thread started with the
program, and read the answer once, during start-up, after waiting for it no
more than two seconds. An answer that came later, on a slow connection or
behind a slow name lookup, was dropped, and the next chance was the next
launch. A failed request, refused, rate-limited or unreachable, was swallowed
whole, so the diagnostic log had nothing to say about any of it, and with no
notice either way nothing showed that the check had not happened. A session
left running for days never asked again, so a release published meanwhile
went unseen. The check is its own watcher now: at start-up and every six
hours after, or 15 minutes after a failure, and whenever it learns of a
newer release it says so then, not at a fixed moment of start-up. A failure
is written to the diagnostic log under --debug.

Added: a newer release in the Alerts panel

A newer release now has a line in the Alerts panel, which reaches EDAM too,
as well as the bars below the desktop window's menu and the terminal
dashboard's header, the scrolling log and Discord. It does not fade or pulse,
survives the clearing of alerts that docking and jumping bring, stays until
Clear, and is replaced by the next newer release, not added to.

Fixed: a leg from a white dwarf was called beyond range

A route through a white dwarf showed the jump after it in red as beyond range,
said the tank ran dry there, and counted a dry stretch longer than a full
tank, though the game had plotted it and the ship could fly it. The Route tab
measured every one-jump leg against the plain jump range and knew nothing of
a white dwarf's supercharge: ×1.5, or ×3 on the Caspian Explorer's SCO drive
Mk II. A neutron star fared no better on the game's own routes, since only
EDLD's Spansh plots, whose neutron legs are several jumps each, were spared
the check. The fuel figures went the same way: a leg out of reach burns
nothing it can name, so the tank was said to run dry at the end of it. Nothing
in the journal contradicted the warning until the jump was made, so it read as
a cautious estimate rather than a wrong one. A leg leaving a neutron star or
white dwarf is now measured against the drive's supercharge, ×4 or ×6 for a
neutron star, and burns the fuel of a jump that much shorter; a supercharge
already taken, from the game's JetConeBoost, carries the next leg wherever it
starts, and the jump spends it. Such a leg shows its boost — "228.7 ly · ×3
boost" — in the desktop window, the terminal dashboard and EDCARS, and reaches
EDAM unchanged.

---

---

Downloads

Platform	File
Linux (x86_64)	EDLD-20261111-linux-x86_64.tar.gz
Windows (x86_64)	EDLD-20261111-windows-x86_64.zip
macOS (Apple silicon)	EDLD-20261111-macos-arm64.zip

No Python install is needed for the binaries. Each archive
carries the licence texts required by the LGPL.

EDLD-20261111.sha256 lists every file above by digest
and EDLD-20261111.sha256.sig signs that list, so one
signature check covers the whole release:

bash scripts/verify_release.sh EDLD-20261111-linux-x86_64.tar.gz

See docs/SIGNING.md to verify by hand.