-
Member
Originally Posted by
mj_godam
hi i still rather confused about the count of 24h limit after hit the threshold
so 24 h limit is count from the first time we open the bot to the second time we open the bot? or from the last time the bot closed/killed to the time we open the bot again? which one is correct?
Thanks in advance
The 24 hours starts when you the bot is closed/killed.
-
Post Thanks / Like - 1 Thanks
mj_godam (1 members gave Thanks to advocates for this useful post)
-
Member
Originally Posted by
advocates
The 24 hours starts when you the bot is closed/killed.
so it counts after the last bot is closed/killed to the next we open the bot again?
thanks for your reply!
-
Member
Originally Posted by
mj_godam
so it counts after the last bot is closed/killed to the next we open the bot again?
thanks for your reply!
Yes it counts once the killswitch activates which means it has reached the caps.
-
Sergeant
How config google account?
-
Member
Hi guys!
I'm really new on this PoGo bots world and I have some noob questions, and ah, English is not my first language, so.. sorry for that.
Do I need to install something else for this bot run properly?
In what file do I put my account login?
Is this bot based on any specific location? Like, Central park... If so, can i change it?
I wanted a bot like this "human-like", I don't mind to farm few ex per day. So, given this info, do I need to change any config?
Last edited by wwkxx; 08-18-2016 at 06:56 AM.
-
Member
Originally Posted by
wwkxx
Hi guys!
I'm really new on this PoGo bots world and I have some noob questions, and ah, English is not my first language, so.. sorry for that.
Do I need to install something else for this bot run properly?
In what file do I put my account login?
I wanted a bot like this "human-like", I don't mind to farm few ex per day. So, given this info, do I need to change any config?
If I'm not wrong you would need to install a framework for your computer, but I'm not sure what's the link but once you're done with that you just need to extract the bot to your desktop and you're good to go.
Once done, start up the bot for the first time and it'll create 2 files, (config.json and auth.json) inside your config folder. Open up auth.json and that is where you put your account details in, if you're using google, I think the default is google, but if you're using ptc, make sure to change to "ptc" inside the auth file, somewhere near the top of the lines.
-
Post Thanks / Like - 1 Thanks
wwkxx (1 members gave Thanks to advocates for this useful post)
-
Member
Originally Posted by
SeriousSensei
Hi guys,
With Niantic implementing the recent CatchFlee ban when you hit 1,000 Pokemon/2,000 Pokestops per day, I figured I'd take a look at implementing a killswitch and other improvements into a current bot (in this case Necro/MobBot). I then took it a little further and increased the humanization factor of the bot by adding varying walk speeds among other internal fixes. With these changes in place, I am hoping that the chances of bans are greatly decreased and that our accounts remain safe.
This bot is NOT intended for users who want ridiculous exp/hr or to snipe all across the globe.
Note: I may or may not continue developing this depending upon user response and usage. If it's a hit, I will work on it further. If not, expect this to be the only release. I do not take any responsibility for banned accounts. While this bot is being worked on to help increase "AI", it is not a guarantee that you will not be banned.
Download Link
MEGA - CLICK
Code:
https://mega.nz/#!NRdCHZjR!CmJFVBBwp-rNkqttnLEpj3mK-8HVqdl9jIM5j86RLck
Decryption Key: !CmJFVBBwp-rNkqttnLEpj3mK-8HVqdl9jIM5j86RLck
v.0.2.0 BETA Updates
Note: This is a BETA release as I haven't had a TON of time to test it yet. It has worked just fine in my trials, but let me know if you encounter further bugs and I will attempt to work on them this weekend.
- Killswitch stat logging. When a killswitch threshold is reached, it will output a .XML log file to your bots-filepath -> KillswitchStats (folder) -> $name-KillSwitchLog.xml. Hopefully this will help those who set lower killswitches but still want to track how many Pokemon they caught during their last run so that they can run again later and adjust thresholds. YOU WILL NEED A FOLDER NAMED "KillswitchStats" IN YOUR BOTS DIRECTORY!Let me know if you have further suggestions on this!


- Added a new option under StartupSettings called "MaximizeKillswitchXP". When this option is set to true, the bot will aim to maximize your experience once the TotalPokemon killswitch has been hit. So, for example, if your killswitch for Pokemon is 5, but for Pokestops its 20, you will always catch 5 Pokemon and hit 20 Pokestops before the bot kills itself. In a future release I will have it work the other way around too, but for now I have never hit my Pokestop cap before hitting my Pokemon cap.

- Added incense support! For whatever reason, the base I used did not provide incense usage support. I have worked it into TuringBot so you should see a nice boost to Pokemon/hr when you have incense available.
- Minor mathematical fixes to change important stats from 'bankers rounding' to a more accepted method. This will enhance numeric accuracy.
- Minor text fixes

v.0.1.1Updates
- HTTP(S) Proxy Support! You are now able to enter your proxy information into the auth.json file and the bot will tunnel your connection through that IP if it is a working IP address. Personally, I set up 'squid' on my Windows 2008 R2 server and am using it as a proxy. Google/YouTube how to do this if you're a server owner! Note: Socks4/5 is not supported, sorry!


- Tweaked the standard configs to provide better out of the box settings. I still suggest checking the config.json going forward.
- Minor text fixes

v.0.1Updates
- Humanized walking - The speed you enter in the config file now has a floating point! No more walking at the same exact speed. You don't walk at a consistent 20km/h when playing in person, so why should the bot? (ex. If you set 40km/h in the config, the bot will walk from Pokestop to Pokestop at a range of 32km/h to 48km/h)
- Pokemon/Pokestop tracker - All Pokemon catches and Pokestop visits are logged at the top status bar. Keep an eye out for the thresholds of 1,000 pokemon/2,000 pokestops per day!
- Killswitch - Going to be away from your computer? Set a killswitch value to have the bot close once a certain number of Pokemon are caught or Pokestops are looted.
- Improvements to how Pokestops are chosen/traveled to - Hopefully this will give a boost (albeit minor) to exp/hr.
- Minor text fixes

Upcoming Updates
- Proper tracking of your threshold status over a 24 hour time period. I will be working to create a local file to store your current pokemon/pokestop # and timestamp so that the bot can intelligently continue botting even after crashes.
- Get incense usage working properly.
- Implement CatchFlee counter so that the bot can perform a certain action (only collect pokestops? close? not sure yet) when flee-bans are found.
- KillswitchMaximizeExp - I will be working on adding an option to continue to collect pokestops even once your killswitch limit for pokemon has been reached. It will also work in that if you hit your pokestop limit first, it will continue to catch pokemon until both thresholds have been hit. This will require a minor codebase rework so this will take some time.
Usage Suggestions
- Do NOT bot on your main! While I am trying my best to make this bot as humanlike as possible, there are NO guarantees. You could very well be banned. Only bot on accounts you don't mind losing.
- Keep walk speed at or under 50km/h
- IMPORTANT: Keep the killswitch set - Have the bot kill itself when 975 pokemon/1975 pokestops are reached. It does not work off of your current local timezone but rather the bots runtime, so if you kill the bot and restart it, you'll need to remember the amount of pokemon caught and pokestops visited from the previous run during the 24 hour timeframe and adjust the killswitch accordingly.
- Do not snipe (at least on your main) - Users are reporting an increase of CatchFlee errors when changing locations quickly! Sniping is currently pretty buggy and I am not devoting as much time to fixing it as you'd probably prefer. Use other bots if you'd like to snipe for now!
Pictures

Uptade and no translate fixe. WOW GG !
-
Member
Originally Posted by
advocates
If I'm not wrong you would need to install a framework for your computer, but I'm not sure what's the link but once you're done with that you just need to extract the bot to your desktop and you're good to go.
Once done, start up the bot for the first time and it'll create 2 files, (config.json and auth.json) inside your config folder. Open up auth.json and that is where you put your account details in, if you're using google, I think the default is google, but if you're using ptc, make sure to change to "ptc" inside the auth file, somewhere near the top of the lines.
Could this be the .Net Framework?
And btw, many thanks for the answer!
-
Master Sergeant
Running this since the release and no ban yet.
Precisa de ajuda? pergunte aqui neste tópico.
Brazilian support.
-
Post Thanks / Like - 1 Thanks
wwkxx (1 members gave Thanks to ffriozi for this useful post)
-
Member
Originally Posted by
wwkxx
Could this be the .Net Framework?
And btw, many thanks for the answer!
Yep, the .net framework sounds right, no problem mate.
-
Member
Originally Posted by
ffriozi
Running this since the release and no ban yet.
non stop? how long it takes to hit the threshold?
-
Member
I'm running it for almost 3 hours and currently my pokemon capture is at mid 400.
-
Member
I understand that sniping is disabled but it can be enabled right?
-
Member
Hello.
Can you add the feature to the bot automatically run itself again after 24 hours counter passed?
So we don't need to worried about the time limit when we want to run it again.
-
Member
I made an account here just to ask this, but is there a missing pokeball trow option in encounters? Seeing as not every player always trows accurately. Forgive me if this is already in the bot, but i am looking to switch to this bot, this was one of the only function I am missing at the moment. (the edited necrobot 0.9 has it for example). Also would a transfer on catch (in case of low IV for example) work?
Sincerly,
Donny
Last edited by donny110; 08-18-2016 at 08:17 AM.
Reason: missed some information