Necro 0.8.6 avoid CatchFlee ban configuration

[fedee253]

I've been using it for 8 hours and no ban yet!! But I'm getting like 15-17k only exp/h.
I think it's because of the message "did not find a pokemon within the location" appearing so much times. I don't know why, it didn't happen before.

[samurouh88]

I've been using it for 8 hours and no ban yet!! But I'm getting like 15-17k only exp/h.
I think it's because of the message "did not find a pokemon within the location" appearing so much times. I don't know why, it didn't happen before.

you are sniping i asume

[Hoully88]

so is the 10 km/h without sniping safe from the ban hammer...i suppose nothing is completely safe but is it a good chance as long as we are staying in one location with the 10 km/h config we should be safe

[Brick3]

Working configuration to avoid CatchFlee for Necro 0.8.6

I figured this would be drowned in the other thread so I am releasing a configuration that will avoid CatchFlee with the latest release of Necro (v0.8.6).
It does however severely limit the experience per hour but it works.

  "DisableHumanWalking": false,
  "WalkingSpeedInKilometerPerHour": 4.0,
  "MaxSpawnLocationOffset": 10,
  "FastSoftBanBypass": false,
  "DelayBetweenPlayerActions": 5000,
  "DelayBetweenPokemonCatch": 5000,

Without sniping
Download 4 km/h - (average human walking speed) 15k exp/hr: Download
Download 10 km/h - 25-30k exp/hr: Download

With sniping
Download 10 km/h - 50k exp/hr: Download

Download Necro: Releases * NECROBOTIO/NecroBot * GitHub

You can probably tweak these values some but these are confirmed working form me the past hour. The actual cause for CatchFlee is still not confirmed but I strongly believe it is related to the dialogue box in the Pokémon Go app regarding moving too fast that you have to click "OK" on if you play the game legitimately and that bots currently do not verify that click.

Why does CatchFlee happen?
CatchFlee appears to happen when the server detects that you are moving too fast. By limiting movement speed and using human like movement we can prevent it. It does however severely limit your experience per hour.

Other
Please go through the settings before running this in regards to transferring and evolving Pokémon. I have just changed the default config to avoid CatchFlee.

For more discussion on CatchFlee and other types of soft bans please visit the stickied thread: [Guide] New temp ban only post here!

Updates
2016-08-12 16:00 - Added another config that also works which is somewhat more aggressive (10 km/h and shorter delay)

Pokemon's don't flee due to high walk speed dummy, it's happening when you get soft ban or because of Niantic's new ban type; you can still use pokestops but pokemon's always flee.
Why would you even write your theory when it's not proven and like it's a fact?

[mickeymike1834]

Pokemon's doesn't flee due to high walk speed dummy, it's happening when you get soft ban. Why would you even write your theory when it's not proven and like it's a fact?

I guess he's one of the staff working in Niantic.

[Hoully88]

i thank you for posting the config i am choosing not to use sniping as i feel that's probably more likely to get caught but 20k XP an hour is going to take me forever and a day to get to level 40 LOL

EDIT: can we maybe use Disney in Hong Kong i heard lots of pokestops there?

[Killshame]

I cannot download necrobot.. any links please?

[xSantin]

I've been using it for 8 hours and no ban yet!! But I'm getting like 15-17k only exp/h.
I think it's because of the message "did not find a pokemon within the location" appearing so much times. I don't know why, it didn't happen before.

What confing are you using?

[fedee253]

What confing are you using?

I'm using the 10km/h with sniping. It''s been 12 hours now, I'm lvl 19. No ban yet.

[NotThizTime]

You can also turn on Snipes, make a safe config

 "GetSniperInfoFromPokezz": false,
  "GetOnlyVerifiedSniperInfoFromPokezz": false,
  "GetSniperInfoFromPokeSnipers": false,
  "GetSniperInfoFromPokeWatchers": false,
  "GetSniperInfoFromSkiplagged": false,
  "MinDelayBetweenSnipes": 70000,
  "SnipeAtPokestops": true,
  "SnipeIgnoreUnknownIv": false,
  "UseTransferIvForSnipe": false,
  "SnipePokemonNotInPokedex": false

You are doing it wrong. To disable Sniping, you only need to change "SnipeAtPokestops" to false.

[Fadelol]

Pokemon's don't flee due to high walk speed dummy, it's happening when you get soft ban or because of Niantic's new ban type; you can still use pokestops but pokemon's always flee.
Why would you even write your theory when it's not proven and like it's a fact?

I never said they flee because you walk too fast. I said that a too high movement speed triggers the new CatchFlee soft ban. All my testing yesterday on 10+ fresh accounts where I ran one account per IP-address I got the CatchFlee soft ban on accounts with a travel speed of 25 km/h or higher within 30 minutes. On accounts with below 25 km/ travel speed I did not get it. I am not posting this as a wild and crazy theory. I have made several posts detailing my observations and tests on the subject and have had many other people telling me they have come to the same conclusion.

I will quote myself on a post in the elite forum on a serious discussion on the soft ban that I made almost 24 hours ago;

Previously known soft bans
So let's first establish the previously discovered soft bans:

• Spin-ban or loot failed ban is a soft ban related to having an account logging in or visiting coordinates too far between each other. This soft ban can be resolved by spinning a Pokéstop up to 45 times.
• IP-ban is a soft ban related to having too many users or API-calls from a single IP-address which is prevented by running only 1 bot per IP-address and resolved by changing IP-address.

Both of these bans are temporary and up to an hour and have been known for days/weeks.

Enter the catch flee ban
Now since yesterday reports of a new type of soft ban has been emerging. Let's call it the catch escape or flee-ban. I have been observing it since this morning on a number of accounts and have done some testing to gather data on it. For some background I had been running settings similar to this on the accounts receiving the new catch escape ban:

• WalkingSpeedInKilometerPerHour: 25 km/h
• DisableHumanWalking: False

As well as settings to catch every Pokémon I could encounter with no sniping being used. I also ran no more than one bot per IP-address. Now when observing this the first thing I wanted to find out was if the new ban was IP-related or not. So I fired up a new account and bot on the same IP-address than the previous one, but with some tweaked settings. In particular I changed WalkingSpeedInKilometerPerHour to 5 km/h.

The first thing I noticed was that the bot was running fine. It is definitely not related to the IP-address but rather to that particular account. I have now been running the new account for a while without further catch escape or flee bans.

Now this leads me to believe that the new type of soft ban is connected to the feature introduced last patch relating to driving or at the very least movement speed. In the app you will receive a notice if you are moving too fast that you have to accept. They might have introduced that at first, then a few days later turned on a feature which disables Pokémon catching unless you verify that you are a passenger/not driving. Just like they did with unknown6 which was implemented a few patches earlier and then suddenly turned on. This could mean it has nothing to do with botting per se but rather user safety. This could be confirmed with a mitm seeing if the client sends something to the server when clicking the moving too fast dialogue.

See, I am not just making things up.

• I have had a theory on what causes the CatchFlee soft ban (too high walking speed)
• I have then tested that theory multiple times with the same result (i.e. comparing low and high walking speed)
• I have then come up with another theory on what is actually the underlying cause (dialogue window in the actual game not being clicked by the bots

The theory on the underlying cause isn't anything I can verify however so that remains a theory. I would however like to think that, due to my previous testing, it looks very likely I have come to the correct conclusion regarding the cause of the soft ban in relation to movement speed. The reason why everybody is not experiencing the changes at once and why some can run higher speeds for a while is probably because they roll out the changes region by region (i.e. server by server).

If you have any other data to suggest otherwise, dummy, please tell us instead of telling me I am wrong or calling me a dummy. The only thing I have been doing is trying to help people out, I have no monetary interest in running bots. I do it because I find it interesting and fun, and it's pretty much the same with helping people out. But yeah I clarified my text a bit more so you won't misunderstand again.

[rizqa06]

how to fix this?

[slowmo1991]

Good Bye!

Due to legal action being started against other bot creators/devs (we did not receive a letter yet) the Project development will be stopped. All Source Files / Downloads will be removed. We now have to say Good Bye to the awesome Community. Over 100k Members on Discord and 500k Downloads a day! The Discord Community will remain open for Discussions. It was fun, we had a nice time. Thank you for the Donaions, all Devs will be getting their share by today.

Your NecroBot Team

thats why github download link wont work

[skyNcez]

runnig for 1 hour. with the 10K km cfg. its slow but safe for now.
better then nothing. thanks alot!

[grobusto]

8km/h here, and editing some delays. I think they know the default delays of our bots, they are not idiot.

And the bot is configured to bot near my location, and i use a vpn.

No catchflee, no soft ban since 17hours! I stop the bot sometimes, to be sure.