EDDiscovery: a captain's log and 3D star map for Elite Dangerous
Captains log and 3d star map for Elite Dangerous
At a glance
- What is it?
- EDDiscovery reads Elite Dangerous journal files and turns them into a searchable history, material and mission state, and a 3D galaxy map. It is a Windows-first tool with a Mono-limited Linux path, and its value depends on how much you want to see at once.
- Who is it for?
- Adopt EDDiscovery if you play Elite Dangerous on Windows and want a persistent, searchable record of your travels, materials, missions and rank in one window, with optional voice and tablet control. Do not adopt it if you only want a lightweight background uploader, or if you need a fully supported Linux client: the README states the Linux path runs under Mono with limitations.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 20, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What EDDiscovery is for, and who ends up using it
Elite Dangerous writes a journal as you play: docking, scans, combat, trade, rank changes. The game itself does not keep a long, browsable record of that. EDDiscovery exists to read those journals and turn them into something you can actually look at, which the README describes as tracking "your Elite Dangerous travels, combat, trading, rank etc." It is a third-party desktop tool, not a mod and not part of the game.
The audience is narrower than "all Elite players". If you fly long expeditions and want to see where you have been on a 3D map of the galaxy, or you want your current materials, commodities and mission list in one place, this is aimed at you. The same applies if you want events vocalised, or a tablet acting as a Roccat-style control grid next to your HOTAS. If you just want your scan data pushed to a community database and nothing else, EDDiscovery is heavier than you need.
The README is explicit about scope: EDD works on the PC, and you can install it on your Elite PC or on another laptop that pulls journal information over a share. Console commanders can run it on a laptop and configure it to download journal information from the Frontier servers, which is the only path for players who cannot reach a local journal directory.
How the journal pipeline and the 3D map fit together
The core mechanism is journal ingestion. Elite Dangerous writes local journal files; EDDiscovery reads them and converts each entry into an event it can display, store and act on. Everything else in the application is downstream of that stream: the history view, the materials and commodity state, the mission list, and the add-on hooks that fire when an event arrives.
The 3D map is the second half. The README says it shows travel history plus data from Spansh or EDSM to aid your journey through the galaxy, and there is a simpler 2D map alongside it. So the map is not only a rendering of your own route. It is your route drawn on top of third-party galaxy data, which is why the EDSM and Spansh integrations matter to the map rather than being a separate feature.
Outbound data is a third path. The README lists EDDN, described as run by edcd.github.io and distributing information on shipyards, markets, stations and scans to the EDCD community, alongside EDSM, Inara, Spansh, IGAU, Coriolis, ED Shipyard, ED Astro and a Canonn plugin. That means the tool is both a reader of your journals and a publisher of selected data to shared databases. Those are different consent decisions, and the README does not spell out per-integration defaults.
Extensibility is deliberately broad. Add-ons can vocalise events, take voice commands through a Free Voice Control pack, bind keyboard shortcuts, read and vocalise joystick inputs, place information on OBS, play MP3s on events through a soundblaster pack, and take commands from the local Elite chat interface via a Chat Console. Beyond that, EDDiscovery supports third-party DLLs and Python plugins. The repository layout reflects this: separate projects for ActionLanguage, BaseUtilities, CAPI, EliteDangerousCore, ExtendedControls and the main EDDiscovery project, with UnitTest alongside them.
Installing EDDiscovery on Windows and running a first session
The README points at the releases page rather than a package manager, and it gives a specific instruction: on the latest release page, scroll to the bottom and download the .exe installer, unless you want the program and its data in the same place, in which case unzip the .zip version into a folder you choose. There is no winget, chocolatey or distro package mentioned in the README. The releases listed at the time of writing include 19.1.11, 19.1.10 and 19.1.9.
If you prefer to build from source, the repository has a solution file at the root and helper scripts for fetching submodules and fixing packages. The README does not document the build steps themselves, so treat these as the entry points rather than a complete recipe:
git clone https://github.com/EDDiscovery/EDDiscovery.git
cd EDDiscovery
./fetchsubmodules.bat
./fixpackages.batAfter that, open EDDiscovery.sln in a C# toolchain and build. The README is silent on which Visual Studio version or .NET target is required, so check the solution before assuming your installed toolchain will work.
On Linux, the README states EDD works with limitations using Mono, and the repository carries monobuild and monobuildmac scripts. Those are the only Linux build hints in the README; there is no documented supported configuration beyond that.
Once running, the first useful thing to confirm is that EDDiscovery can see your journals. If it is on the same PC as Elite, that should be automatic. If it is not, you either point it at a share or, for console commanders, configure it to download journal information from the Frontier servers. After that, open the history view to confirm events are arriving, then the materials and mission views, then the 3D map to see your travel history against EDSM or Spansh data.
Where EDDiscovery stops being the right tool
The Linux story is the clearest limitation. The README says EDD works on Linux using Mono "with limitations" and never enumerates them. That is a weak support statement for anyone who does not run Windows, and it is worth reading as a warning rather than a compatibility guarantee. If Linux is your only platform, you are on an explicitly qualified path.
The second limitation is weight. EDDiscovery installs a desktop application with an installer, a database, a 3D renderer, an add-on system, DLL and Python plugin surfaces, and a web/tablet interface. If your actual goal is to push scan and market data to EDDN and see it on EDSM, you are paying for a lot of UI you will not use. The README never claims to be minimal, and the feature list makes the opposite case.
The third is the integration surface itself. EDDiscovery both reads journals and sends data to EDSM, Inara, Spansh, EDDN and others. The README lists the partners but does not document what is sent by default or how to disable an individual integration. If you care about exactly which of your flight data leaves the machine, you will need to verify that in the settings rather than in the README.
Finally, the README does not document rollback or downgrade. If a new release changes your stored data, there is no stated way back to a previous version. The release notes are the place to look, and the README points there without summarising them.
EDDiscovery compared with EDMC and EDCoPilot
The closest comparison people search for is EDDiscovery versus EDMC. The structural difference is what each one is for. EDMC is a background companion: it sits next to the game and forwards journal events to community services. EDDiscovery is a foreground application: it keeps a history you can browse, state you can inspect, and a 3D map you can plan on. If you want a small process and a browser tab, EDMC's shape is closer to that. If you want the log and the map in the same window, EDDiscovery is the one that has them.
Against EDCoPilot, the split is presentation. EDCoPilot is a voice-and-assistant style companion; EDDiscovery's voice features come from add-ons, including a Free Voice Control pack for recognition and packs that vocalise events, read joystick inputs and play MP3s on events. So voice in EDDiscovery is an extension of a log-and-map application, not the product itself.
There is also a comparison with Exploration Buddy, and the same logic applies: the more an alternative is built around a single job, the less it will do the things EDDiscovery does with history, materials, missions and the galaxy map. None of these differences are documented in the EDDiscovery README; they follow from what each tool is described as doing.
Maintenance cadence, licence and what an upgrade costs you
The repository is not archived, and the last push was on 2026-09-15. Releases have been arriving steadily: 19.1.9 on 2026-07-12, 19.1.10 on 2026-09-02, and 19.1.11 on 2026-09-12. That is an active release line, and the release titles name concrete changes such as Rhino modules and slots, Nomad additions, Caspian fixes and planetary signals.
The practical upgrade cost is that EDDiscovery is a desktop application with local state, not a service you redeploy. Upgrading means running a new installer or unpacking a new .zip over your existing install, and the README does not describe a migration step or a downgrade path. If you keep the .zip layout so program and data live together, back up that folder before upgrading; if you used the installer, the data location is not documented in the README.
On licensing: EDDiscovery is Apache-2.0, and the README carries an Apache 2 badge. Apache-2.0 permits commercial and private use and modification, and it includes a patent grant, but it also carries notice and attribution obligations if you redistribute the code or a modified version. This is a description of the licence, not legal advice; read LICENSE.md in the repository before you redistribute anything. Note also that the README states EDDiscovery is not affiliated with or endorsed by Frontier Developments, so the licence covers the tool, not the game or its assets.
Editorial conclusion
Adopt EDDiscovery if you play Elite Dangerous on Windows and want a persistent, searchable record of your travels, materials, missions and rank in one window, with optional voice and tablet control. Do not adopt it if you only want a lightweight background uploader, or if you need a fully supported Linux client: the README states the Linux path runs under Mono with limitations. Before committing, verify that the release you download matches the installer type you want (.exe versus .zip), that your journal folder is reachable from the machine you install on, and whether you need console journal download from Frontier's servers.
Frequently asked questions
What is EDDiscovery?
It is a third-party captain's log and 2D/3D map for Elite Dangerous players, described in the README as a tool that can track your travels, combat, trading and rank. It reads Elite Dangerous journal files and displays history, materials, commodities and missions, with a 3D galaxy map drawing on Spansh or EDSM data.
How do I install EDDiscovery?
The README directs you to the latest release page, where you scroll to the bottom and download the .exe installer, or unzip the .zip version into a folder of your choice if you want program and data in the same place. It also links an install video.
How do I use EDDiscovery?
Once it is reading your journals, the README lists the main surfaces: your ED history, your current materials and commodity state, mission lists, expedition planning, the 3D galaxy map and the simpler 2D map. Add-ons add voice, keyboard shortcuts, OBS output and a tablet control grid.
Is EDDiscovery safe?
The README does not make a safety claim. What it does state is that EDDiscovery is not affiliated with or endorsed by Frontier Developments, and that it integrates with EDSM, Inara, Spansh, EDDN and others, so data can leave your machine. The README does not document per-integration defaults, so check the settings yourself.
What does "EDDiscovery is updating the system database" mean?
The README does not explain this message or name a system database. It does describe EDDiscovery integrating with EDSM, Spansh, Inara and EDDN, which are external data sources, but no update process or its duration is documented.
What is the difference between Spansh and EDSM in EDDiscovery?
The README treats both as data sources for the 3D galaxy map, saying it shows travel history and data from Spansh or EDSM to aid your journey. It also lists both as partner integrations but does not compare what each one supplies.
Community notes