Did not find a Pokemon within the SnipingScanOffset!

[wyyyxz]

This problem happens if u r using Necrobot + pogolocationfeeder or any other feeders.

After compare the cords in Necrobot and the cords in Pogofeeder it's easily to see:

1. The cords in pogofeeders are correct!
2. But the cords scanned in Necrobot are something else.

I don't know why Necrobot is doing this i'm no programmer.

Can any dev check on this problem I found please?

I've tried to change offset range to larger but won't solve it. Then I released the cords in Necrobot are completely different than the ones in pogofeeder,.

Temporary solution is Not to use pogofeeder atm and change snip Pokezz to false too. It cause same problem with Pokezz feeder.

If anyone find out why Necrobot uses different cords to snip, please reply to this thread. Thanks

[wyyyxz]

If u compare the pokemon names and cords in Necrobot to pogofeeder u will see they are different.

[Juan1]

I have the same problem. ''Did not find a Pokemon within the SnipingScanOffset"

[leo2311]

V0.8.0 have a problem with snipe, devs are working to fix it. V0.7.7 work good, use this utill they release a new update.

[yukina12]

m using 7.6 still work like a charm

[NgelawakGan]

It happen to me too :/

[kingchenc]

Guys, its a problem with "SnipingScanOffset" ... The Devs know it... just sit on discord ^^ Wait for a update...
OR... Play with settings on "SnipingScanOffset" ... set higher, but then... risky to get bann...

[sebflex]

Guys, its a problem with "SnipingScanOffset" ... The Devs know it... just sit on discord ^^ Wait for a update...
OR... Play with settings on "SnipingScanOffset" ... set higher, but then... risky to get bann...

which value is high, but "not risky" ?

[kingchenc]

which value is high, but "not risky" ?

Thats a good Question Bro... I dont Know...
Standart is 0.0003 -> "SnipingScanOffset": 0.003,
Just play with settings... 0.001? 0.01? Its your own risk if you play with that setting...

Better wait for a update, or go back to 0.7.6/7

[eartyearth]

Thats a good Question Bro... I dont Know...
Standart is 0.0003 -> "SnipingScanOffset": 0.003,
Just play with settings... 0.001? 0.01? Its your own risk if you play with that setting...

Better wait for update, or go back to 0.7.6/7

[deleteddddd]

[Xfxpower]

V0.8.0 have a problem with snipe, devs are working to fix it. V0.7.7 work good, use this utill they release a new update.

"wasabi AFK - Heute um 14:48 Uhr
@everyone Just an FYI... For those who are having problems with sniping... its simply down to your settings, the statement made in announcements about there being an error with snipingoffset is completely incorrect (which is removed), ... I am running Necro 8.0 and sniping right now... it works absolutely fine

https://s10.postimg.org/os66jlx49/snipe.png"

[BIOABOMAI]

mine is 1! im f¨*cked? hahaha

"MinDelayBetweenSnipes": 1,
"SnipingScanOffset": 1.0,

i got the same error but still catching! *img