New EDR version 1.0.2 "Jabadub" is out!
It will auto-update on its own at shutdown (close the game and EDMC, wait for a while, relaunch).
If you are new to EDR, check https:://edrecon.com
Your support is also appreciated:
https://patreon.com/lekeno
New: visual summary of legal records
Added "sparklines" graphs to commander profiles similar to what's been available in the
EDR discord bot. This graph when used in combination with the other bits of information on the profile (e.g. clean/wanted scans, max and last bounties for the past 90 days, role, etc) should give you a good idea of what sort of commander you are looking at.
How to read the visual summary
- each bar represent a month's worth of data
- the current month is on the right edge (highlighted in cyan), it goes back in time from there toward the left edge
- the first graph shows the number of clean scans in a given month
- the second graph shows the number of wanted scans in a given month
- the third graph shows the maximum bounty on record in a given month
How to read the clean and wanted graphs
- these two graphs share the same vertical scale to facilitate relative comparisons between the number of clean vs. wanted scans
- the higher the clean bar, the more this commander got scanned with a clean status
- the lower the wanted bar, the more this commander got scanned with a wanted status
- color palettes are also used to indicate the order of magnitude, e.g. pale green or red for less than 10 scans, light red up to 100, red up to 1000, blue or purple if above (rare)
How to read the bounties graph
- this shows the maximal bounty a commander got scanned with in a given month, the higher the bar, the higher the bounty.
- a grey + red color palette is also used to indicate the order of magnitude of the bounty: 0 credits, less than 1k, less than 10k, less than 100k, etc. (Above 10 billion is in purple)
Customization
You can configure the layout and style by following the instructions in the igm_config.v3.ini file located in the config folder.
Misc: bug fixes
- Some reports weren't accepted due to a last (hopefully) powerplay canonicalization issue