Add support for multiple Elite:Dangerous accounts

[Djuwanna]

Request EDDI be able to discern which Elite Dangerous account is logged in and provide separate configurations for multiple accounts (support for EDSM, Materials, etc.)

Right now, when I switch between multiple Elite accounts I have to remember to reconfig EDDI for the correct account before I log in or I end up with inaccurate information both locally and being uploaded to EDSM (I actually had to have EDSM delete one of my accounts so I could recreate it and reupload the correct information - my fault obviously, but multiple account support would have prevented my error). And I have to replace the materials .json file with a "zeroed out quantities" materials .json file when switching accounts or the only things that are updated are those materials I have, not those I don't have (which I'm betting is a Frontier thing - they probably don't send zero quantity information).

EDMC (as an example) is able to switch accounts on-the-fly and remembers different logons and API's for the various accounts. Can EDDI be written at some point to do the same?

[Tkael]

Also, adding this would allow us to support having different configurations for live and beta releases.

[Tkael]

There is an unimplemented Commander event that we can use to ensure all commander data is recorded under the correct commander name during the initial loading journal events (the old Commander continued event fired too late to be reliable).

Initial thought would be to add the commander name to the configuration data files saved to %appdata%/EDDI by renaming the files. E.g. shipmonitor.json could become (name).shipmonitor.json or (name).beta.shipmonitor.json
What character set does Elite Dangerous allow for commander names? With that sort of formatting, the commander name must be able to be saved as a valid file name.

The other option would be to include multiple cmdr names in a single json file.

[mwerle]

The other option would be to include multiple cmdr names in a single json file.

Probably safest, generate a uuid (or calculate a hash) over the Commander name and use that elsewhere; avoids any potential characterset and formatting issues.

[Timnus]

as far as i know. Frontier allows the full qwerty keyboard character set for commander names. there is a Character length limit.

[Tkael]

When we implement this, we can also implement storing the active config in memory to reduce unnecessary reads from the file system.

[Tkael]

@parduz has suggested having EDDI be as portable as possible configuring the location of EDDI's settings during installation (perhaps via a settings file saved with the .exe?)

[juhaeske]

Any possibility/work around to add multiple cmdr feature?
And I do not mean multiple windows accounts. EDDiscovery has it, EDEngineer too.
3 Cmdrs hete...