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

Snipe task: prevent incorrect player position setting; Evolve task, fixed never evolve case; Null reference exception in SnipeScanForPokemon fix #1852

Merged
merged 6 commits into from
Aug 1, 2016

Conversation

actislav
Copy link
Contributor

@actislav actislav commented Aug 1, 2016

splited getpokedexcount fix from last pull request

…f you know how)

SnipePokemonTask added one more try finally block.... did not see it in first attempt to fix player coordinate bug
# Conflicts:
#	PoGo.NecroBot.Logic/Tasks/GetPokeDexCount.cs
@recon88 recon88 added the ready label Aug 1, 2016
@actislav
Copy link
Contributor Author

actislav commented Aug 1, 2016

Also Null reference exception in SnipeScanForPokemon ScanResult check fix

@actislav
Copy link
Contributor Author

actislav commented Aug 1, 2016

Fixed never evolve potential case, fixed logic of evolve

@actislav actislav changed the title Snipe task: prevent possible incorrect player position setting Snipe task: prevent incorrect player position setting; Evolve task, fixed never evolve case; Null reference exception in SnipeScanForPokemon fix Aug 1, 2016
@AiksuCoding AiksuCoding closed this Aug 1, 2016
@AiksuCoding AiksuCoding removed the ready label Aug 1, 2016
@BornSupercharged BornSupercharged merged commit 3388bb5 into NecronomiconCoding:master Aug 1, 2016
schnapster pushed a commit to schnapster/NecroBot that referenced this pull request Dec 8, 2016
Snipe task: prevent incorrect player position setting; Evolve task, fixed never evolve case; Null reference exception in SnipeScanForPokemon fix
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.

5 participants