Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shipyard - includes fighters? #901

Closed
lwt-pressy opened this issue Nov 3, 2018 · 1 comment
Closed

Shipyard - includes fighters? #901

lwt-pressy opened this issue Nov 3, 2018 · 1 comment
Assignees
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.

Comments

@lwt-pressy
Copy link

EDDI version in which issue found

EDDI-3.1-b3

Situation

The Shipyard gets filled up with fighters and ships from the beta

Wanted

It would be nice to habe a delete button to delete unwanted ships (e.g. fighter) and it would be nice that the commander data would be splitt up for normal and beta (like eddiscovery does it.

I also didn't check if the mixup (normal/beta) will show up in the material monitor, as i normally use the material monitor in inara.

@Tkael
Copy link
Member

Tkael commented Nov 3, 2018

There are two issues here...

  1. EDDI currently doesn't support multiple accounts/configurations (a variant of Add support for multiple Elite:Dangerous accounts #505)
  2. The shipyard is being populated with fighters
    Since Add support for multiple Elite:Dangerous accounts #505 already targets multi-configurations, I'm going to revise the issue title to focus solely on fighters in the shipyard.

Your shipyard is reloaded whenever you start a new session in Elite Dangerous. Bouncing from the main menu back into game should clear any issues with the Shipyard data that you see. But it's not our intent to include fighters in the shipyard data.

@Tkael Tkael changed the title Shipyard - mixed with beta and also fighters Shipyard - includes fighters? Nov 3, 2018
@Tkael Tkael added 6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour. PR submitted A PR has been submitted, but not accepted yet. labels Nov 3, 2018
@Tkael Tkael self-assigned this Nov 3, 2018
@richardbuckle richardbuckle removed the PR submitted A PR has been submitted, but not accepted yet. label May 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants