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

Spin Fort- Move to Fort : add timedout forts to recent_forts #3916

Closed
wants to merge 1 commit into from
Closed

Spin Fort- Move to Fort : add timedout forts to recent_forts #3916

wants to merge 1 commit into from

Conversation

vosk
Copy link

@vosk vosk commented Aug 14, 2016

When restarting the bot, movetofort might pick a fort that spinfort will not spin due to cooldown.
When iterating cooldown forts in spinfort, add them to to recent_forts if not already contained, to guide
movetofort to other fort

@mention-bot
Copy link

@vosk, thanks for your PR! By analyzing the annotation information on this pull request, we identified @douglascamata, @BriceSD and @TheSavior to be potential reviewers

@julienlavergne
Copy link
Contributor

julienlavergne commented Aug 14, 2016

Could be solved with #3897

@elicwhite
Copy link
Contributor

Closing this in favor of the approach that will be taken after #3897

@elicwhite elicwhite closed this Aug 14, 2016
@vosk
Copy link
Author

vosk commented Aug 16, 2016

Let me get this straight. I added a simple 3 line fix that uses ACTUAL server information, and you consider this an inferior approach compared to dumping to a json file after a hypothetical restart. So your argument is that "no, the server is wrong, that particular pokestop is not a recent fort, the cooldown is incorrect". Also, why do you think these changes are incompatible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants