Issues, Workarounds & Localization

With the Crucible expansion, the Scanner Filters editor now has options for the various Groups (Radar, Magnetometric, Gravimetric etc.) However, I'm not sure how the new scanner filters are supposed to be used in practice. For example:


Scenario #1:

1. There is one signature, in a system, and you begin scanning it. You have your filter set to hide Gravimetric signatures.
2. You get a weak result ( < 25% ) on the signature. Its Group is still undetermined.
3. On the next scan attempt, you suddenly get no results. This means that either:

1. The signature was a Gravimetric and got filtered (Strong result, => 25%)
2. The signature fell outside of your probe's range and didn't get picked up (Outside of probe range)
3. The site despawned

Problem:
A player has no idea if the signature is hidden because:

• they succeeded in finding out what it was and it got filtered, or
• they just lost track of the signature

Scenario #2:

1. There are two signatures in a system, both Groups undetermined.
2. Scanning the first signature, it gets hidden because it's a Gravimetric.
3. We then proceed to scan the second signature. However, with this scan result, because the Scan Results for the first signature have dropped below 25% and the Group has changed back to undetermined, the signature gets unfiltered and displays again.

Problem:
A site you don't want will get successfully hidden by the filter on a scan attempt, but as you carry on scanning the other signatures in a system, it will end up being revealed again, because the Scan Results window only remembers a signature's Group and Type (site name) if you get a 100% hit. Once you perform a new scan, the previous results are discarded.


Suggestion:
System scanner remembers Group and Type of signature once the player has revealed them by scanning. If a player scans the signature again and gets a weak hit (< 25%), the Scan Results window should still display the Group and Type if they've revealed it earlier.

Bonus points if you get it to remember this even when jumping through systems, and only resetting it after downtime