-
Notifications
You must be signed in to change notification settings - Fork 131
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
Clear finished quests #1030
base: legacy
Are you sure you want to change the base?
Clear finished quests #1030
Conversation
Im working fine with cleanup_every_spin set to True - But sometimes the quest got solved anyway. |
No this wont clean solved quests, but reduce the cases where quests are solved. |
It will eventually. To run efficiently, the check for finding finished quests only happens if less trash cans than expected were found - that's less than one in the case of running cleanup every spin. This means that it'll only clean quests for you if you have three (or less if a trash can can't be found for another reason). |
This is all about clearing finished (=solved) quests (to the stack). |
Yeah I thought this was related to PR1029, will also test this ;) |
This is now obviously conflicting with the new AR quest mess, specifically the changes coming with #1051. I will have to reconsider this whole feature and check if the upcoming PogoDroid will even allow to do this. So put on hold for now. |
Reworked to check for finished quests on the initial startup, and when the quest log is unexpectedly full ( Working on recent master with updated PD keeping an AR quest in inventory. Testing would now be welcome :-) |
Uhm this was left for ages I guess.... What's the state of the PR here? |
There would be an exception thrown if the OCR part of quest checking failed. This commit fixes the problem.
@Grennith been running this myself ever since I created the PR. I guess nobody cares anymore because we didn't get another "spin 3 pokestops" quest since then. It would still be relevant if this quest ever came back. |
2022-02-21 'upstream/master' into cleanup-finished-quests
Review and testing required !!!
Related issue: #869
The recent event bringing a "spin 3 pokestops" quest highlighted the problem of handling finished quests during quest scan. While it's not usually a problem on pure scanner accounts, events and changes can severely impact scan performance by introducing quests a quest scanner unintentionally finishes before it's able to delete them.
The most stable way to handle this issue is usually to set
cleanup_every_spin
in area settings toTrue
(or using quest enhancer addon). However, this negatively impacts scan performance in dense areas, because the time and resource heavy ocr routines have to run more frequently.However, this PR attempts to handle finished quests as far as a scanning software is able to. It works as follows:
deletionscanless than the expected amount of trashcans is foundthe quest log is unexpectedly full, a check for finished quests will follow.In the end, this PR results in - ideally - requiring manual intervention once every 14 days to retrieve weekly breakthroughs, instead of possibly every day to clear up individual finished quests. It'll also explicitly identify the issue in the logs instead of the workers failing without an explicit cause.
Notes:
the change inthis has been revertedmapadroid/ocr/matching_trash.py
was necessary because quests blocked by the breakthrough were identified as having a trashcan - raising the threshold to0.65
reliably fixed this without causing any false negativescleanup_every_spin
set toFalse