Repository navigation
Replies: 1 comment
|
I popped it over to Issues, though I do appreciate you putting this into its own thread. The other threads are getting confusing. 🤣 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As promised here my thoughts on a multi-commander setup.
Issue
When the journal contains info for more than one commander the data displayed is randomly selected.
Example: The CMDR section shos info on commander A, the FC info is for an FC belonging to commander B, the exobiology data shown may belong a commander C.
Current Solution
The app recognises and identifies all commanders in the journal and shows an according message. To display information correctly for one commander only, the server setting Commander needs to be set to the desired commander name, Save Settings needs to be clicked and the server restarted using the button Restart now.
This is emminently doable and does not require a big effort. Besides it is a problem for only a limited amount of players. However, since the data is already enumerated, it appears that an automation of these steps should be fairly straightfoward.
Proposed Solution
Again I refer to ED Discovery, where on start-up the last used commander is selected and only the entries pertaining to that commander are displayed. Changing to a different commander is done simply by selecting that commander from a drop-down list, which triggers a re-read of the journal with entries now shown only for the new commander.
So, instead of a message showing the commanders found and re-direct the player manually to the Server Settings, a similar drop-down field (or something equivalent) should be shown and after selecting the new commander, a server re-start should be initiated by the tool automatically. Whether the last-used commander can be stored and then used on start-up I don't know, but it still would be better if just the data of one commander is shown to begin with.
If a last-used commander value is not available, perhaps some default value could be defined separately (or favourite, doesn't really matter how it is named).
Notes
I guess the only thing left after that would be to ensure that in fact all data shown only belong to that commander across all tabs. I'm saying this because I thought at one point that I had selected commander B and the exobiology data still seemed to be from commander A, but it may have been a timing/update issue. Not sure.
All reactions