-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fixed 'pokemon_caught' event #5539
Conversation
Removes "catch error 1" and removed redundant if/else logic
@Gobberwart, thanks for your PR! By analyzing the annotation information on this pull request, we identified @javajohnHub, @solderzzc and @nivong to be potential reviewers |
DO NOT MERGE... minor bug-fix to come. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I'm curious as to why these events are special from other events. Why not declare them in the same way as other events?
pokemon_caught needs additional logic so it can be limited to only specific conditions (iv>x, cp>y etc.) as for the other ones... shrug. Someone's personal formatting preference? |
Should be OK to merge now |
Short Description:
Fixes "catch error 2" appearing in telegram instead of correct catch message.
Fix removes a lot of redundant code. Tested with no errors.
Fixes/Resolves/Closes (please use correct syntax):