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

Jump to bottom

Countermeasure Feedback #2817

Closed
8 tasks done
alexanderson1993 opened this issue Mar 3, 2020 · 0 comments
Closed
8 tasks done

Countermeasure Feedback #2817

alexanderson1993 opened this issue Mar 3, 2020 · 0 comments
Labels
type/feature an issue describing new functionality

Comments

@alexanderson1993
Copy link
Member

alexanderson1993 commented Mar 3, 2020 •
edited

  • On my screen there's quite a bit of button overlap happening. (Layout Corners)
  • It would still be nice to be able to select a countermeasure and "recycle" a portion of the materials back into their supplies.
  • One of the biggest issues I worry about is that we don't see a built countermeasure until it gets deployed.  So as an FD that's a lot of information to try to look through at the time they are trying to use it.  It would be nice that once it is created we can see what they have done built and programmed.
  • I'd still like the ability for them to say whether a countermeasure is "active" or "inactive".  That way they have the potential to use them without deploying them externally.  Perhaps to tell the difference on core the ones in the ship are at the top of the list and highlighted colors based on their active status.
  • Can the modules be in alphabetical order?  Seems kind of random.
  • It would be nice on the core side to be able to click a check box or something for the specific module so we can keep track if we have responded to it, destroyed it, or something else.  Or maybe just a little field we can type a note.
  • If I have a battery it says, "Power 100%" on core and so I am just curious how it is calculating that.
  • When I configure the countermeasure I can only configure one module, correct?
@alexanderson1993 alexanderson1993 added the type/feature an issue describing new functionality label Mar 3, 2020
github-actions bot pushed a commit that referenced this issue Mar 7, 2020
@semantic-release-bot
chore(release): 2.7.0
a21f594 
# [2.7.0](v2.6.1...2.7.0) (2020-03-07)

### Bug Fixes

* **Countermeasures:** A number of fixes to countermeasures. Adds ability to activate countermeasures before they are launched. Sorts available module list. Built modules can be removed and the resources are recycled for half of their original value. Add a field for flight directors to add notes to countermeasures so they know how they responded to them. Countermeasures that have not been built are now visible to the flight director. Fixes [#2817](#2817) ([5de3de5](5de3de5))
* **Damage Report Config:** Fixes an issue where Long Range Message damage report configurations don't accept destination values. Closes  [#2826](#2826) ([fdc8964](fdc8964))
* **Library:** Fixes an issue where new library entries cannot be added. Closes [#2795](#2795) ([58e5569](58e5569))
* **Sensors:** Fixes an issue where sensors core doesn't load at all. Closes [#2813](#2813) ([ab918bd](ab918bd))
* **Viewscreen:** Fixes an issue where having the viewscreen core layout open causes videos to auto-next multiple times. ([230d302](230d302))

### Features

* **Targeting:** Add an extra option to make it possible to target contacts that are moving by clicking on them. Closes [#2822](#2822) ([3a74c51](3a74c51))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature an issue describing new functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexanderson1993