Release Elite Dangerous Market Connector (EDMC)

Elite Dangerous Market Connector ("EDMC") is a third-party application for use with Elite Dangerous. Its purpose is to facilitate supplying certain game data to, and in some cases retrieving it from, a number of websites and other tools.

To do this it utilises the Journal Files written by the game when played on a PC. It also makes use of Frontier's Companion API ("Frontier's CAPI"), accessible once you've authorised this application.

It does not work with Console game accounts, and is no longer supported on Windows 7.

See the link above for more information about what it can do for you.

------------------------------------------------------------------------------------------------------
Problems Updating from 3.4.3.0/3.43

There was an issue with the old 3.4.3.0/3.43 (and earlier) versions when checking for an update. This turned out to be due to the size of the 'appcast' file for this having grown with all the more recent changelog entries. To solve this I culled all the changelog entries in that file from before 4.1.6. I'll try to keep an eye on this in the future, but if you're still on such an old version and have issues with the program crashing when seeming to offer an update please upgrade manually from the latest release.
---------------------------------------------------------
  • We now test against, and package with, Python 3.10.2.
    As a consequence of this we no longer support Windows 7.
    This is due to Python 3.10.x itself not supporting Windows 7.
    The application (both EDMarketConnector.exe and EDMC.exe) will crash on startup due to a missing DLL.

    This should have no other impact on users or plugin developers, other than the latter now being free to use features that were introduced since the Python 3.7 series.
    Developers can check the contents of the .python-version file in the source (it's not distributed with the Windows installer) for the currently used version in a given branch.



Release 5.3.4 (VirusTotal)


Whilst EDMarketConnector.exe was fixed for the Odyssey Update 11 difference in Journal file names, EDMC.exe was not. If you're wondering, that's the command-line utility that, for instance, Trade Computer Extensions uses to obtain data.
  • Use the new common function for finding latest journal file in EDMC.py.
  • Quietens some NavRoute related logging for the benefit of EDMC.py. This is now at DEBUG level, rather than INFO.



Release 5.3.3 (VirusTotal)

Unfortunately 5.3.2 failed to fully address the issues caused by the different Journal filenames when using the Odyssey Update 11 client. It's fine if you run EDMarketConnector first and then the game, as the code path that detects a new file always does just that.

But the code for EDMarketConnector startup to find the current newest Journal file relied on sorting the filenames and that would mean the new-style names would always sort as 'oldest'.

This release fixes that code to properly use the file modification timestamp to determine the newest file on startup.

Release 5.3.2 (VirusTotal)

This release contains one change to cope with how Frontier decided to name the Journal files differently in the Update 11 Odyssey client.

Release 5.3.1 (VirusTotal)

This release addresses some issues with newer EDDN code which could cause erroneous alerts to the player, or sending of bad messages.
  • EDDN: Cope with ApproachSettlement on login occurring before Location, such that we don't yet know the name of the star system the player is in.
    Closes #1484
  • EDDN: Cope with ApproachSettlement missing planetary coordinates on login at/near a settlement in Horizons.
    Closes #1476
  • EDDN: Change the CodexEntry "empty string" checks to only apply to those values where the schema enforces "must be at least one character".
    This prevents the big 'CodexEntry had empty string, PLEASE ALERT THE EDMC DEVELOPERS' message from triggering on, e.g. NearestDestination being empty, which the schema allows.
    Closes #1481

Plugin Developers​

  • If you use a sub-class for a widget the core code will no longer break if your code raises an exception. e.g. a plugin was failing due to Python 3.10 using collections.abc instead of collections, and the plugin's custom widget had a configure() method which was called by the core theme code on startup or theme change. This then caused the whole application UI to never show up on startup.
    This also applies if you set up a button such that enter/leave on it, i.e. mouse in/out, causes the theme.py code for that to trigger.
    So, now in such cases the main UI should actually show up, although your plugin's UI might look weird due to theming not being properly applied.
    The plugin exception WILL be logged, at ERROR level.

Release 5.3.0

As has sadly become routine now, please read our statement about malware false positives affecting our installers and/or the files they contain. We are as confident as we can be, without detailed auditing of python.org's releases and all the py2exe source and releases, that there is no malware in the files we make available.

This release is primarily aimed at fixing some more egregious bugs, shortcomings and annoyances with the application. It also adds support for two additional EDDN schemas.

  • We now test and build using Python 3.10.2. We do not yet make use of any features specific to Python 3.10 (or 3.9). Let us restate that we absolutely reserve the right to commence doing so.
  • We now set a custom User-Agent header in all web requests, i.e. to EDDN, EDSM and the like. This is of the form:
    EDCD-EDMarketConnector-<version>
  • "File" -> "Status" will now show the new Odyssey ranks, both the new categories and the new 'prestige' ranks, e.g. 'Elite I'.
    NB: Due to an oversight there are currently no translations for these.
    Closes #1369.
  • Running EDMarketConnector.exe --reset-ui will now also reset any changes to the application "UI Scale" or geometry (position and size).
    Closes #1155.
  • We now use UTC-based timestamps in the application's log files. Prior to this change it was the "local time", but without any indication of the applied timezone. Each line's timestamp has UTC as a suffix now. We are assuming that your local clock is correct and the timezone is set correctly, such that Python's time.gmtime() yields UTC times.
    This should make it easier to correlate application logfiles with in-game time and/or third-party service timestamps.
  • The process used to build the Windows installers should now always pick up all the necessary files automatically. Prior to this we used a manual process to update the installer configuration which was prone to both user error and neglecting to update it as necessary.
  • If the application fails to load valid data from the NavRoute.json file when processing a Journal NavRoute event, it will attempt to retry this operation a number of times as it processes subsequent Journal events.
    This should hopefully work around a race condition where the game might not have yet updated NavRoute.json at all, or has truncated it to empty, when we first attempt this.
    We will also now NOT attempt to load NavRoute.json during the startup 'Journal catch-up' mode, which only sets internal state.
    Closes #1348.
  • Inara: Use the <journal log>->Statistics->Bank_Account->Current_Wealth value when sending a setCommanderCredits message to Inara to set commanderAssets.
    In addition, a setCommanderCredits message at game login will now only ever be sent at game login. Yes, you will NEED to relog to send an updated balance. This is the only way in which to sanely keep the 'Total Assets' value on Inara from bouncing around.
    Refer to Inara:API:docs:setCommanderCredits.
    Closes #1401.
  • Inara: Send a setCommanderRankPilot message when the player logs in to the game on-foot. Previously you would HAVE to be in a ship at login time for this to be sent.
    Thus, you can now relog on-foot in order to update Inara with any Rank up or progress since the session started.
    Closes #1378.
  • Inara: Fix for always sending a Rank Progress of 0%.
    Closes #1378.
  • Inara: You should once more see updates for any materials used in Engineering. The bug was in our more general Journal event processing code pertaining to EngineerCraft events, such that the state passed to the Inara plugin hadn't been updated.
    Such updates should happen 'immediately', but take into account that there can be a delay of up to 35 seconds for any data sent to Inara, due to how we avoid breaking the "2 messages a minute" limit on the Inara API.
    Closes #1395.
  • EDDN: Implement new approachsettlement/1 schema.
  • EDDN: Implement new fssallbodiesfound/1 schema.
  • EDDN: We now compress all outgoing messages. This might help get some particularly large navroute messages go through.
    If any message is now rejected as 'too large' we will drop it, and thus not retry it later. The application logs will reflect this.
    NB: The EDDN Gateway was updated to allow messages up to 1 MiB in size anyway. The old limit was 100 KiB.
    Closes #1390.
  • EDDN: In an attempt to diagnose some errors observed on the EDDN Gateway with respect to messages sent from this application some additional checks and logging have been added.
    NB: After some thorough investigation it was concluded that these EDDN errors were likely the result of long-delayed messages due to use of the "Delay sending until docked" option.
    There should be no functional changes for users. But if you see any of the following in this application's log files PLEASE OPEN AN ISSUE ON GITHUB with all the requested information, so that we can correct the relevant code:
    • No system name in entry, and system_name was not set either! entry: ...
    • BodyName was present but not a string! ...
    • post-processing entry contains entry ...
    • this.body_id was not set properly: ...
    • system is falsey, can't add StarSystem
    • this.coordinates is falsey, can't add StarPos
    • this.systemaddress is falsey, can't add SystemAddress
    • this.status_body_name was not set properly: ...
    • You might also see any of the following in the application status text (bottom of the window):
    • passed-in system_name is empty, can't add System
    • CodexEntry had empty string, PLEASE ALERT THE EDMC DEVELOPERS
    • system is falsey, can't add StarSystem
    • this.coordinates is falsey, can't add StarPos
    • this.systemaddress is falsey, can't add SystemAddress
    • Ref: #1403 #1393.

Translations​

  • Use a different workaround for OneSky (translations website) using "zh-Hans" for Chinese (Simplified), whereas Windows will call this "zh-CN". This is in-code and documented with a comment, as opposed to some 'magic' in the Windows Installer configuration that had no such documentation. It's less fragile than relying on that, or developers using a script/documented process to rename the file.
  • As noted above we forgot to upload to OneSky after adding the Odyssey new ranks/categories. This has now been done, and some new phrases await translation.

Plugin Developers​

We now test against, and package with Python 3.10.2.

  • We've made no explicit changes to the Python stdlib, or other modules, we currently offer, but we did have to start explicitly including asyncio and multiprocessing due to using a newer version of py2exe for the windows build.
  • We will now include in the Windows installer all of the files that py2exe places in the build directory. This is vulnerable to a later version of our code, python and/or py2exe no longer causing inclusion of a module.
    We have endeavoured to ensure this release contains at least all of the same modules that 5.2.4 did.
    We are looking into including all of Python stdlib, but if there's a particular part of this we don't package then please ask us to by opening an issue on GitHub.
  • We now have an .editorconfig file which will instruct your editor/IDE to change some settings pertaining to things like indentation and line wrap, assuming your editor/IDE supports the file.
    See Contributing.md->Text formatting.
  • As noted above, prior to this version we weren't properly monitoring EngineerCraft events. This caused the state passed to plugins to not contain the correct 'materials' (Raw, Manufactured, Encoded) counts.
  • config.py has been refactored into a sub-directory, with the per-OS code split into separate files. There shouldn't be any changes necessary to how you utilise this, e.g. to determine the application version.
    All forms of any import statement that worked before should have unchanged functionality.
  • We now include FDevIDS as a sub-repository, and use its files directly for keeping some game data up to date. This should hopefully mean we include, e.g. new ships and modules for loadout exports in a more timely manner.
    Developers of third-party plugins should never have been using these files anyway, so this shouldn't break anything for them.
  • It's unlikely to affect you, but our requirements-dev.txt now explicitly cites a specific version of setuptools. This was necessary to ensure we have a version that works with py2exe for the windows build process.
    If anything this will ensure you have a more up to date version of setuptools installed.

----------------------------------------------------------
Release 5.2.4

This is a very minor update that simply imports the latest versions of data files so that some niche functionality works properly.
  • Update commodity.csv and rare_commodity.csv from the latest EDCD/FDevIDs versions. This addresses an issue with export of market data in Trade Dangerous format containing OnionHeadC rather than the correct name, Onionhead Gamma Strain, that Trade Dangerous is expecting.
    This will only have affected Trade Dangerous users who use EDMarketConnector as a source of market data.

Release 5.2.3

This release fixes one bug and fixes some example code.
  • Odyssey changed the order of some Journal events. This caused our logic for tracking the following to break, and thus not report them ever to Inara:
    • Ship Combat, Trade and Exploration ranks.
    • On-foot Combat and Exobiologist ranks.
    • Engineer unlocks and progress.
    • Reputations with Major Factions (Superpowers).
    • This is now fixed and the current state of all of these will be correctly reported to Inara if you have API access for it configured.

Developers​

  • Now built using Python 3.9.9.
  • Updated PLUGINS.md to state that we don't actually include all of Python's standard library.
  • The click_counter example plugin code has been corrected to both actually work fully, and pass our linting.

Release 5.2.2

This release adds one new feature and addresses some bugs. We've also updated to using Python 3.9.8.
  • Windows now has "minimize to system tray" support.
    • The system tray icon will always be present. - There is a new option on the Settings > Appearance tab -
      Minimize to system tray.
    • When this new option is active, minimizing the application will also
      hide the taskbar icon.
    • When the new option is not active, the application will minimize to the
      taskbar as normal.

Bug Fixes​

  • If a CAPI query failed in such a way that no requests.Response object
    was made available we attempted to blindly dump the non-existent object. We now check that it actually exists, and log the specifics of the exception.
  • A user experienced the game writing a NavRoute.json file without a
    Route array, which caused the application to attempt sending a badly formed navroute message to EDDN. That message was then remembered and constantly retried.
    • We now sanity check the NavRoute.json contents to be sure there is a
      Route array, even if it is empty. If it's not present no attempt to send the EDDN message will be made.
      If this scenario occurs the user will see a status line message No 'Route' array in NavRoute.json contents.
    • For any EDDN message that receives a 400 status back we will drop it
      from the replay log.

Release 5.2.1

This release primarily addresses the issue of the program asking for Frontier authorization much too often.
  • Actually utilise the Frontier Refresh Token when the CAPI response is "Unauthorized". The re-factoring of this code to make CAPI queries threaded inadvertently prevented this.
Thanks to all that reported this problem, helped track it down, and tested the release candidates.

Release 5.2.0

  • The 'Update' button is disabled if CQC/Arena is detected.
  • Frontier CAPI queries now run in their own thread. There should be no change in functionality for users. This affects both EDMarketConnector (GUI) and EDMC (command-line).
  • File > Status will now use cached CAPI data, rather than causing a fresh query. Currently if data has not yet been cached nothing will happen when trying to use this.
  • Trying to use File > Status when the current commander is unknown, or there is has been no CAPI data retrieval yet, will now result in the 'bad' sound being played and an appropriate status line message.
  • File > Save Raw Data also now uses the cached CAPI data, rather than causing a fresh query. This will write an empty JSON {} if no data is yet available.
  • New docs/Licenses/ directory containing all relevant third-party licenses for the software this application uses.
  • Settings > Output > File Location 'Browse' button will now always be available, even if no output options are active.
  • The 'no git installed' logging when running from source is now at INFO level, not ERROR. This will look less scary.
  • EDMarketConnetor command-line arguments have been re-ordered into logical groups for --help output.
  • Support added for several new EDDN schemas relating to specific Journal events. The live EDDN server has been updated to support these.
    Schema support added for:
    • codexentry/1
    • fssdiscoveryscan/1
    • navbeaconscan/1
    • navroute/1
    • scanbarycentre/1
  • If a message to EDDN gets an 'unknown schema' response it will NOT be saved in the replaylog for later retries, instead being discarded.

Bug Fixes​

  • Pressing the 'Update' button when in space (not docked, not on a body surface) will no longer cause a spurious "Docked but unknown station: EDO Settlement?" message.
  • A bug preventing --force-localserver-auth from working has been fixed.
  • horizons and odyssey flags should now always be set properly on all EDDN messages. The horizons flag was missing from some.

Developers​

  • Now built using Python 3.9.7.
  • New journal_entry_cqc() function for plugins to receive journal events specifically and only when the player is in CQC/Arena. This allows for tracking things that happen in CQC/Arena without polluting journal_entry(). See PLUGINS.md for details.
  • Command-line argument --trace-all to force all possible --trace-on to be active.
  • Contributing.md has been updated for how to properly use trace_on().
  • EDMC.(py,exe) now also makes use of --trace-on.
  • EDMarketConnector now has --capi-pretend-down to act as if the CAPI server is down.
  • Killswitches now have support for removing key/values entirely, or forcing the value. See docs/Killswitches.md for details.
  • state['Odyssey'] added, set from LoadGame journal event.
  • You can now test against a different EDDN server using --eddn-url command-line argument. This needs to be the full 'upload' URL, i.e. for the live instance this is https://eddn.edcd.io:4430/upload/.
  • New command-line argument --eddn-tracking-ui to track the EDDN plugin's idea of the current BodyName and BodyID, from both the Journal and Status.json.
 
Last edited:
Release 3.46
This should be the final release of EDMC based on Python 2.7. The next release after this, assuming this one doesn't introduce new bugs, will be based on Python 3.7. Any plugins that users have installed will need to have been updated to work under Python 3.7 by the time that next version of EDMC is released. During EDMC startup, at most once per day, you might see a popup with the text:

One or more of your enabled plugins do not yet have support for Python 3.x. Please see the list on the 'Plugins' tab of 'File' > 'Settings'. You should check if there is an updated version available, else alert the developer that they will need to update the code when EDMC moves to Python 3.x

A small bug means that popup will never appear, but you can still check File > Settings > Plugins tab and see what plugins are listed in the section with the text Plugins Without Python 3.x Support.
If any of your plugins are listed in that section then they will need updating, by you or the original developer, to work with Python 3.7. See Migrating to python 3.7 for more information.
Anyone who wishes to try out the forthcoming Python 3.7-based version should see Release 3.51 beta0, but please do not install that unless you're technically savvy enough to make coherent bug reports, thankyou.
Changes in this version:
  • The CAPI CLIENT_ID has been changed to one under Athanasius' account, so when users are asked to (re-)authenticate with Frontier they'll see Elite Dangerous Market Connector (EDCD/Athanasius) as the application asking for permission. There's been no change to the use of the data Frontier then gives access to.
  • Updated translations (as of 2019-09-26 in general and 2019-11-04 for Polish).
  • Linux: Should now appear on task bar whilst in dark mode theme.
  • INARA: Send correct opponentName for Interdicted and Interdiction events.
  • Send SAASignalsFound events to EDDN.
  • Add Agronomic Treatment introduced for a community goal.
  • Fix Detailed Surface Scanner rating.
  • Fix for the "Inara 400 The reputation value exceeds the valid range" error.
  • Minimum interval between checks for a new version of EDMC has been reduced from 47 hours to 8 hours.
  • There is a new option, within the 'Configuration' tab, 'Disable Automatic Application Updates Check when in-game' which when active should prevent update checks from showing a popup whilst you're in-game. You can still use Help > Check for updates to trigger a manual check.
  • Support added for the journal CarrierJump event, triggered when you're docked on a Fleet Carrier as it performs a jump. This is now sent to: EDDN, Inara, EDSM. NB: EDSM doesn't yet support this event at the time of writing, so will still not track such Carrier Jumps in your Flight Log or current location. Generally when EDSM is updated to handle such new events it will back-process stored unrecognised events.

NB: There's some issue with 3.44 updating to this new 3.46. If you use the in-app prompt to install it will kill the old running EDMarketConnector.exe and attempt to run the new installer, but that then fails in some manner and you're left with 3.44 still installed. I'm investigating now.
 
Last edited:
I'd neglected to properly edit the update feeds file, so it was still pointing to the 3.44 installer file despite saying it was for 3.46. Fixed!
 
One small bug I didn't catch, that popup warning about Python 3.x and plugins won't ever happen. But if you look on File > Settings > Plugins you will see any plugin without Python 3.x support listed in an appropriate section.
 
I've also spotted a puzzling issue with the EDMarketConnector.exe not showing the correct icon. This worked fine for the 3.44 build, yet doing that afresh exhibits the same "no icon" problem. It's currently working OK on my Python 3.7 build environment so I'm inclined to just let this slide until the next, Python 3.7 based, release.

It's py2exe that builds the .exe and is meant to take care of incorporating the icon, and nothing has changed about how that is being specified, nor are any errors thrown during the ubild process so <insert shrugging emoji>.
 
Last edited:
This 3.46 EDMarketConnector.exe icon thing... some of us are seeing the icon, some of us not. I've just checked a fresh build of the 3.44 .exe, which for me doesn't show the icon, and it has an identical SHA256 checksum to the github .msi 3.44 file which does show the icon for me. So this is Windows 10 doing something bizarre.

I've already tried removing %LOCALAPPDATA%\IconCache.db and rebooting, it made no difference.

So, I'm definitely inclined to leave this be given things are still working sanely for me with the python3 branch built using Python 3.7.7.
 
1593326871506.png
 
There are some new phrases awaiting translations on https://marginal.oneskyapp.com/collaboration/project/52710 if anyone has the skills for the supported languages. If you find anything you think is wrong and can't edit then poke me to 'Unfinalize' the translation(s). I can also look at adding new languages if there's a volunteer to make a new translation.

Any work ready to go when I make the next release will be included :) .
 
NB: If you're helping with translations you only need to care about the ones under the "EDMarketConnector / Miscellaneous" project and not the "EliteOCR / EliteOCR" one!

I'm pretty sure the EliteOCR project has been dead for many years now, made moot by the Journals and CAPI as data sources.
 
Hi all !

Now I'm forced to flood the logs from the game with my hands on Inara. Can I use your program by giving her access only from Inara ? So she can fill in the logs from the game on Inara.

Without providing any logins and passwords from the game itself.

Thank you.

Example:
1. Specify in the EDMS settings where the logs and the key to Inara's website should be stored.
2. Start EDMS and it will automatically fill in the logs on Inara's website.
 
Last edited:
Now I'm forced to flood the logs from the game with my hands on Inara. Can I use your program by giving her access only from Inara ? So she can fill in the logs from the game on Inara.

Without providing any logins and passwords from the game itself.

Thank you.

Example:
1. Specify in the EDMS settings where the logs and the key to Inara's website should be stored.
2. Start EDMS and it will automatically fill in the logs on Inara's website.
Yes, EDMC supports Frontier Authentication, it hasn't asked for your game login details for a long time now.

You can then set the options in EDMC so that it only sends to Inara (don't enter an EDSM API Key, and if you really don't want to then disable the options for sending to EDDN). You'll obviously then need to always be running EDMC when you play the game.
 
If anyone has had 3.50 or 3.51 installed (or running from source) in order to test against Python 3.7 then could you please switch to 3.99.0.0 or the beta branch of the source code. See the first link for Release Notes. If you're feeling particularly brave you could use the develop branch which will have the latest code I've merged in from Work-In-Progress branches.

Check the open Issues before reporting any problems you see. I'll likely be making a 3.99.1.0 pre-release today or tomorrow to fix a few more things.

If all goes well with that then expect the actual 4.0.0.0 release of Python 3.7 based EDMC some time next week.
 
The next full release of EDMC will be 4.0.0.0. As well as fixing some bugs and including some other enhancements this will be the big move from Python 2.7 to Python 3.7. So, with that in mind, I'd like as many users as possible to install and test this 3.99.2.0 pre-release to help find any new bugs before that big change is offered to everyone.

You can get it from Pre-Release 3.99.2.0 . Install by simply running it. It's the same as if EDMC offered you a new version and you went through with installing it.
As always, please report any issues on GitHub. If you want to discuss or check anything first then find us in the #edmc channel of the EDCD Discord Server.
You should read all of the changelogs for 3.99.0.0, 3.99.1.0 and 3.99.2.0. I'll make the easy by pasting them here:
3.99.0.0

  • This release is based on Python 3.7, not 2.7, so a user might find some of their plugins stop working. If you have any that do not have the proper support you'll see a popup about this, at most once every 24 hours, when you start the program. As directed on that popup you can check the status of your plugins on 'File' > 'Settings' > 'Plugins' in the new 'Plugins Without Python 3.x Support:' section. If the popup gets annoying then follow the directions to Disable a plugin. For any plugins without Python 3.x support you should first ensure you're using the latest version of that plugin. If that hasn't been updated then you might want to contact the plugin developer to see if they'll update the plugin. For some plugins check this list.
  • Translations updated:
  • New languages: Serbian (Latin, Bosnia and Herzegovina) (175/175), Slovenian (Slovenia) (144/175).
  • New phrases were added and the only 100% translated languages are now: French, German, Ukrainian, Spanish, Russian, Czech, Japanese, Serbian (Latin), Portugese (Portugal), Serbian (Latin, Bosnia and Herzegovina). Please do contribute on the OneSkyApp project if you are able to.
  • Fixes a bug where certain combinations of 'Output' and 'EDDN' options would lead to both reverting to their defaults.
  • EDDB plugin now uses a system's SystemAddress to construct the URL to view the system on eddb.io. This removes the need for the systems.p file. That file will be removed in a future version, plugin authors should not be relying on its presence.
  • EDDB plugin now uses a station's MarketID to construct a URL to view the station on eddb.io. This removes the need for stations.p. That file will be removed in a future version, plugin authors should not be relying on its presence. NB: It's now using the system's "Population" data from Journal messages to determine if the system has stations or not. This allows for the × as station name to be clickable to open the eddb.io page for system when you're not docked. It's known that some systems with stations have a Population of "0" and thus won't allow this functionality. This is Frontier's issue, not EDMC's. If you logged out in a populated system, run EDMC afresh, and use the 'Update' button you won't see the × until you login fully to the game.
  • New 'Help' > 'About E:D Market Connector' menu item to show the currently running version. Includes a link to the release notes.
3.99.1.0

  • Fix a bug where if you copied a Journal file to the live location, resulting in a "Journal.YYMMDDHHMMss.XX - Copy.log" file, the application would pick it up as 'new' and potentially re-send duplicate data to all of EDDN, EDSM and Inara. Now the only files the application will take note of must:
  1. Start with Journal. or JournalBeta.
  2. Have the 12-digit date/timestamp, followed by a .
  3. Have the 2 digit serial number, followed by a .
  4. Nothing else before the trailing log.
  • Fix the 'Release Note' URL in the 'About' popup to use the correct format.
  • Fix the location of Registry keys for the update checker, WinSparkle, to be under EDMarketConnector instead of EDMarketConnector.py.
3.99.2.0

  • Added Swedish to the translated languages. Thanks to Gurra.
  • Will throw an exception, rather than a Segmentation Fault, if run on Linux without DISPLAY properly set.
  • Corrects setting of WinSparkle (updates checking) options to be under the new 'EDCD' Registry key.
 
Hi Athan,

the usage of EDMC.exe (which TCE is using) from the V3.99.2.0 installation producing an error on any command line parameter (-o/-m/-l etc.).
The error message is "Can't read Journal file: b"name 're' is not defined".
Also the -v parameter reports the version 39.92, which is also wrong.
EDMC 3.51beta is working properly.

Hopefully you find the issue before release, otherwise the TCE users will take out their torches :)

I can't report it on Github actually, cause my account there has an issue, so I can't login. Hope this get fixed by Github any time soon.
 
Last edited:
Hopefully you find the issue before release, otherwise the TCE users will take out their torches :)

I can't report it on Github actually, cause my account there has an issue, so I can't login. Hope this get fixed by Github any time soon.
I've opened this issue for it and will take a look in the next day or so latest.
 
I can't report it on Github actually, cause my account there has an issue, so I can't login. Hope this get fixed by Github any time soon.
I've made a new release with just these fixes and an updated Swedish translation: Release 3.99.3.0


Pre-Release 3.99.3.0
Consider this as 'beta3' for the following full '4.0.0.0' release.

* Fix up EDMC.exe (command line tool):
* Correctly report the version with -v.​
* Don't error out on checking Journal filenames.​
* Updated Swedish translation.
 
Last edited:
installed 3.99.3 allways get the "server down" message, is the server actually down or is a bug too?

edmc gives no server down message
 
Top Bottom