Expected Behavior
When the "Exclude Rarity" option is used, e.g. to exclude pokemon that are "Uncommon and below", those pokemon should never be drawn.
Current Behavior
RocketMap first displays all pokemon and then removes the excluded rarities en masse. This makes panning the map awkward and slow.
In contrast, when individual pokemon are excluded Via the "Hide Pokemon" feature, they are never drawn.
Possible Solution
Move the check for rarity exclusion to the same location as the check for individual exclusion?
Steps to Reproduce (for bugs)
Context
The "exclude by rarity" feature is potentially much more useful now with the new dynamic rarity, but currently runs slowly and awkwardly.
Your Environment
- Version used: latest
- Python 2.7
- Windows 10
Reactions are currently unavailable
Expected Behavior
When the "Exclude Rarity" option is used, e.g. to exclude pokemon that are "Uncommon and below", those pokemon should never be drawn.
Current Behavior
RocketMap first displays all pokemon and then removes the excluded rarities en masse. This makes panning the map awkward and slow.
In contrast, when individual pokemon are excluded Via the "Hide Pokemon" feature, they are never drawn.
Possible Solution
Move the check for rarity exclusion to the same location as the check for individual exclusion?
Steps to Reproduce (for bugs)
Context
The "exclude by rarity" feature is potentially much more useful now with the new dynamic rarity, but currently runs slowly and awkwardly.
Your Environment