EDEXO 1.3.3 — portable

A journal-linked exobiology and colonisation companion for Elite Dangerous. Compare reads your local journal, merges scans and organic signals, and predicts the candidate species on a body from FSS/DSS telemetry alone — with payout ranges, first-footfall tracking, a system map, a customisable HUD and a species encyclopedia. Colonize follows your construction sites and plans the hauling, trip by trip.

This release is the single-file portable build. For the unpacked program folder plus the two console builds, see v1.3.3-zip — same version, same code.

Download EDExoCompare.exe and run it. Nothing is installed.

The neutron route now knows your drive: the range and the fuel of every jump come from the drive module's own figures, so a route is planned on the range the ship really has at every stop, with a margin near the limit. A new Scan route tab shows each system of your route from above with the shortest way over the bodies worth mapping and the biology, and the route lists say what each system pays.

New

1. Scan route. A new screen (the "+" tab menu, or the Menu): the system you are in, seen from above, every star and planet where its orbit puts it now, at true scale under a grid of squares from 1 ls to 100,000 ls that follows the zoom. Planets worth mapping above a value you set (default 500,000 cr) and bodies with biology left to sample join a route: the shortest way there from the arrival star, numbered on the map and listed with each leg's distance. Bodies your honk counted but nobody has scanned stand on an outer ring as "?" and fill in as you scan. ◀ ▶ go through the systems of the route you plotted; Next known jumps to the next one whose bodies are known; a search shows any system. The mouse wheel zooms to the mouse, faster the further out; Compact shows every orbit on a log scale, the whole system at once.
2. What a route's systems pay. A discovered system's panel on the galaxy map shows the FSS value of every body, the DSS value of the planets worth mapping, and the expected exobiology, body by body, with the bodies still missing from its honk's count. The NavRoute "Next" list and the neutron route's stops show the same in a line each, with a total for the route.
3. Plotted systems are kept. Every system on a route you plot in the game is kept, not only the last 200 routes: a new layer, Plotted systems – not visited, marks them on the galaxy map, and the map's search finds them by name, tagged "Plotted in-game, not visited".
4. A refuel bar on the HUD. At a refuel stop of the neutron route the HUD shows how much to scoop: at least enough for the next refuel, at most what every supercharge before it still reaches.

Changed

1. The jump range comes from your drive. The range and the fuel of each jump are worked out from the drive module's own figures (optimal mass, most fuel a jump, its fuel law) and your Loadout, as soon as the ship is fitted, for any fuel level and cargo: no jumps needed first. On a tester's Caspian, 68 supercharged jumps matched to the hundredth of a tonne. An unknown drive falls back to your own jumps as before.
2. Supercharges are counted at their real fuel. A short supercharge burns less than the drive's most, so the ship stays heavier than the old plan thought and its range shorter: the planner now counts every supercharge's own fuel, and no longer plans hops a few light years past what the ship reaches.
3. A margin near the limit. A neutron-to-neutron hop within 2 % of the supercharge's reach is planned as a supercharge and a normal jump; hops well inside it stay one supercharge. It costs a jump or two on a trip across the galaxy.
4. The plan starts from the fuel you have. With the game running, the tank as it is; with it closed, the last level your journals give (a jump, a scoop, a refuel), including the jumps you made while EDEXO was not running. "Fuel now" in the route says which.
5. Any system as a stop. The neutron route's stops can be any system Spansh knows, and stations by name ("Explorer's Anchorage"), not only systems with biology on record.
6. Species rules re-measured on a whole year of EDDN data: a few rules that the second half of the year contradicts were dropped, so some bodies show species they had hidden; none shown before is lost.

Fixed

1. Engineering at an engineer counts at once. A new FSD roll (or heavier armour) changed the range only after the next login; it now counts from the roll.
2. The Guardian FSD Booster's bonus no longer grows as the tank empties: a supercharge with one could be planned past its reach.
3. The HUD's own text colour stays when you switch the HUD colour; "Scheme's text" goes back to the scheme's.

The first start re-reads your journals once (the scan route needs the time of each orbit).

Where your data lives

%LOCALAPPDATA%\ED Exo Compare\ — settings, your LAN key, your EDSM credentials if you add them, the species you have scanned on foot, your Fix corrections, the journal folder you chose, your HUD layout, where your windows were, the systems you looked up on Spansh (kept 30 days), the shared exomastery folder, and the prediction caches. Nothing of yours is kept in the program folder, so replacing it on an update loses nothing. On Linux the same lives in ~/.config/edexo-compare. Backups go only where you point the Backups tile.

Your journals are read, never copied out. Uploads to EDSM, Canonn and EDDN happen only if you turn them on yourself. Looking a system up sends only its name or number to Spansh.

Windows will say the publisher is unrecognised. The executable is not code-signed, so SmartScreen asks first: "More info" → "Run anyway".

Licence

Code: PolyForm Noncommercial 1.0.0 with two additional permissions (showing the app in streams and videos is free; releases up to and including 1.2.20 stay MIT). Data: CC BY-NC-SA 3.0 (credit, no commercial use, share alike; part of it is derived from EDAstro) — see data/LICENSE-DATA.txt. The species photographs are Elite Dangerous screenshots: Frontier's game art, under Frontier's terms — NOTICE.md names every contributor and says which images are borrowed from the ED-DSN community. The list of Frontier-populated systems and looked-up systems come from Spansh.