When no Fort is nearby, bot attempts to call GetMapObjects() quickly. #1649
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…are no nearby Forts. Also fix logic so if MaxTravel is 0, we don't hit gyms.
schnapster
pushed a commit
to schnapster/NecroBot
that referenced
this pull request
Dec 8, 2016
…apobjects_fix When no Fort is nearby, bot attempts to call GetMapObjects() quickly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Applies a 30 second cooldown to the check for the next stop is there is no more nearby. Also fixes a bug where if you set MaxTravelDistanceInMeters to 0 it would attempt to spin forts.
I am open to comments on where to put it, it seemed the best place for the cooldown that was reachable for other places was in Navigation.