Fix max distance when sniping #4772
Merged
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
…igger with snipe enabled.
|
@Jasperrr91, thanks for your PR! By analyzing the annotation information on this pull request, we identified @danielsdian, @buluba89 and @BreezeRo to be potential reviewers |
|
This fixed the problem 👍 |
|
Nice to have :) very good catch. I was intending to fix this, but never thought the fix can be so clean. |
|
👍 |
This was referenced Aug 28, 2016
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.
Short Description:
People were complaining about the sniping not adhering to the maximum distance. This was caused by a statement that didn't trigger whenever snipe was turned on.
Fixes/Resolves/Closes (please use correct syntax):