-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
"Once" Rewards affecting Filters #84
Comments
Well, I don't know general consensus here tbh. I was under the assumption that people would be fine hitting it once as well (maybe i am mistaken however?) |
If you have a filter for 2 APs for a raid you want to farm, and this raid has a "once" AP and a "permanent" AP, it will trigger. If you have done the event, you no longer get the "once" AP despite the reward showing up every time. Thus, making the 2 AP filter effectively useless as it will hit nearly every day skip. The work-around is to never count the "Once" items in filter calculations. |
I know the workaround for it, I just am not sure if I should implement it. While it may seem like a good idea in context of an event like Cinderace/Charizard/Greninja, it is possible that random raids also have "Once" rewards. You cannot then farm for these rewards anyway since the raid will disappear (for potential non 7* raids with "Once" in their reward tables). The solution for this however can be to read RAM to figure out if this "Once" has been triggered or not and then count accordingly. This can even make the display of rewards more intuitive since it wont have stuff like Once written next to the reward anymore, it will be exactly what the user sees. |
Well, yeah, of course, that's why I suggested the work-around until the solution is found. And if you are unsure the workaround should be implemented for all users, we have this beautiful new options tabular form, turning it off or on could just be a checkbox. |
Describe the bug
For events, there is a "once" award (e.g. for Cinderace, it is an Ability Patch). Even after completing the event, the "once" award is still calculated in filters despite not being available.
To Reproduce
Expected behavior
I don't expect the filters to hit the "once" awards at all (option?, thoughts?)
The text was updated successfully, but these errors were encountered: