EDLD 20261112

Added: the Engineering window

Engineering is a window of its own again, with two tabs. Fitting shows one
ship at a time, picked from a list of every ship owned, then the builds
planned for hulls not owned yet, then New (Planned)…, which asks for the hull
from a list and starts one. The window is split into equal halves: each slot
and what is fitted on the left, the target build on the right, a module that
differs in red and engineering still to do in amber. Target… takes the build: an EDSY or Coriolis link, long or short, an
EDOMH link, or SLEF JSON exported by EDSY, Coriolis or EDSX, and refuses a
build for another hull. A planned build is edited the same way and has Apply
to, which makes it the target of an owned ship of its hull, drops the plan and
shows that ship.

Under the slots, in the same two halves, Work left lists what each slot still needs — the module to
buy, or to take out of storage when one of that kind is stored, the grades
still to roll with the rolls each takes, the experimental effect — and
Materials lists each material the work costs against what is held, with
what is short. Shopping list… suggests the trades that cover a shortfall from what
the build does not need, within a trader's column before across one, and the
nearest material trader of each kind. A grade takes as many rolls as its
number, so G1 to G5 is fifteen; a grade rolled part way takes the rest of its
rolls.

Recipes, EDSY links and EDOMH ships are read with tables EDLD ships with,
data/eddb.sqlite, made from EDSY's eddb.js and refreshed with each
release; nothing is downloaded for them. Every EngineerCraft in the journals
is checked against the tables at start-up and as it happens, and where they
disagree the journal's recipe is the one used and the difference is logged
once. The traders come from the journals first: every station docked at that
has a Material Trader, its kind taken from a MaterialTrade made there, the
nearest first and marked as traded at. Spansh fills in the rest, but only
stations whose kind it states; a trader's kind is no longer guessed from the
station's economy, which named the wrong kind for some.

Materials is the Ship window's former Engineering tab, moved: the materials
travel with every ship, not the one being flown. In EDCARS the window has the
Engineering section; in the Dashboard layout and the terminal dashboard it is
a large window chosen under Options → Display. EDAM receives it as the
engineering group, with Fitting showing the ship chosen on the desktop.

Changed: Discord without discord-webhook

EDLD posts to the Discord webhook itself, with Python's own HTTP client, so
discord-webhook and requests are no longer needed, installed or bundled. A
post Discord refuses now says why in the terminal, where before nothing was
printed; a rate limit is waited out once and the post retried.

Fixed: forum channels

With ForumChannel on, no thread name was ever given, so Discord refused
every post to a forum channel's webhook and, since the refusal was not
reported, nothing appeared and nothing said why. The first post now starts a
thread — named CMDR <name> with ThreadCmdrNames on, otherwise
ED Live Dashboard and the date and time — and everything after goes into
it. Turning ForumChannel off returns posts to the channel itself.

Changed: community goals with neither CAPI nor Inara

The Missions tab's Community Goals section now shows when neither Frontier's
CAPI nor Inara has answered, saying that goals not joined come from one of
them, connected under Preferences › Data, and that a goal joined at its
station appears from the journal. Goals already joined are listed above it as
before.

Removed: funding links

The "Support EDLD Development" strip along the bottom of the desktop window,
its View menu toggle and the same links in Help → About are gone, along with
.github/FUNDING.yml.

Fixed: EDDN fleet carrier bartender messages

The fcmaterials_capi/1 message, the bartender's orders from a CAPI market
poll of a fleet carrier, was sent after every poll, docked or not: CAPI
answers with the last market docked at, so EDLD uploaded a carrier's orders
from a planet's surface, again at every start, and EDDN flagged each one. It
is now sent only while docked at that carrier, and only when its orders have
changed. A Location that says the ship is not docked, as after restarting
the game while landed, now clears the docked station, which only Undocked
did before. The message also carried the game version and build from the
journal; a message built from CAPI names the CAPI endpoint instead, so it now
sends CAPI-Live-market for both. Messages built from the journal still carry
the journal's values.

Changed: EDCARS's sections

The rail now runs Alerts, Command, Helm, Objectives, Exploration, Mining,
Fleet, Engineering, Career, then Settings, with Ctrl+1 to Ctrl+9 in that
order. EDCARS still opens on Command, and tells EDAM to.

Added: engineering in the Ship window's Modules

Each engineered module has a line under it with its grade, blueprint and
experimental effect — G5 Increased Range (Mass Manager) — set in so the
grade sits under the module's name, past its class and rating. A roll at an
engineer changes the line at once rather than at the next Loadout. EDAM
receives these as a new note row and draws them the same way.

Fixed: material trades were never counted

A MaterialTrade names each side's material and amount Material and
Quantity, where the other material events say Name and Count; the trade
was read as the latter, so both sides came back empty and were skipped. Every
trade left the Engineering tab showing what was held before it until the
next login's Materials snapshot put it right, and since the numbers were
merely stale nothing looked wrong. Materials given as mission rewards, given
to an engineer, and given to research were not counted at all, for the same
lack of any visible failure; all four are counted now.

Fixed: no materials when the newest journal holds no login

The materials came only from the Materials snapshot the game writes at
login, read while replaying the newest journal. A newest journal without one
— the launcher started and closed, a crash before login — left the tab empty
until the next login, and an empty tab reads as nothing held rather than as
nothing read. At start-up the materials are now taken from the newest
snapshot in the earlier journals and every material event after it, as they
stood when the game last closed; checked against the journals, they match
update_stock.py to the unit.

---

Downloads

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

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

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

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

See docs/SIGNING.md to verify by hand.

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.