Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Bot do not move more it stays in the same area\ please and lot the same pokestops over and over agen and agen
what have you done to PokeFarmer Bot. ? ?
Yes i can upload logs but i DO NOT want to upload them publicly since i think Niantic is also registered here on this forum
The mod will ask for log, I am not a mod. (Which makes my response unofficial)
Your bag is full! Bot will not farm the same pokestop again for the next 5 minutes once it has been farmed already. The bot sees it as an unfarmed pokestop again and again and it will not stop until it is farmed, and that will not happen because your bag is full, so your bot will be on perpetual loop. The only way that the loop can be broken by itself is when a pokemon shows up, and your bot will try to capture it spend pokeball, then you will have space in your bag, and the pokestop can now be farmed. Then the bot will finally walk away. Emptying your bag will simply fix this.
How to fix this? look at the number of pokeball you have. then subtract 5 from it and remember the number.
-Log out and go to your setting.
-Go to inventory, and check the "recycle item ball and keep" then put the number.
-Log back on again.
Your bot will recycle anything above that number. And since you subtracted 5 from it, your bag will never get full. This will allow the bot to farm as many pokestop as he can without filling your bag and will earn you 50 points everytime. Once the pokestop is farmed, the bot will not farm it again until it's green again, which takes about 5 mins.
But make sure that you put limit on other items too, revive, raspberry and other items can easily fill the gap unless you also put a limit on them.
That is not the problem.. Checking this box will cause your bot to stay near a lured pokestop (and only if it is lured) and wait until a pokemon spawned in that pokestop. At that time, there will not be any activity by the bot. His problem is that it keeps trying to spin the same pokestop lured or not, over and over, and the text box at the bottom shows it. It will only happen when the bot recognized this as an unfarmed bot, but unable to farm because the bag is full. I know the bug that he encountered from first hand experience, not a hearsay.
The mod will ask for log, I am not a mod. (Which makes my response unofficial)
Your bag is full! Bot will not farm the same pokestop again for the next 5 minutes once it has been farmed already. The bot sees it as an unfarmed pokestop again and again and it will not stop until it is farmed, and that will not happen because your bag is full, so your bot will be on perpetual loop. The only way that the loop can be broken by itself is when a pokemon shows up, and your bot will try to capture it spend pokeball, then you will have space in your bag, and the pokestop can now be farmed. Then the bot will finally walk away. Emptying your bag will simply fix this.
How to fix this? look at the number of pokeball you have. then subtract 5 from it and remember the number.
-Log out and go to your setting.
-Go to inventory, and check the "recycle item ball and keep" then put the number.
-Log back on again.
Your bot will recycle anything above that number. And since you subtracted 5 from it, your bag will never get full. This will allow the bot to farm as many pokestop as he can without filling your bag and will earn you 50 points everytime. Once the pokestop is farmed, the bot will not farm it again until it's green again, which takes about 5 mins.
But make sure that you put limit on other items too, revive, raspberry and other items can easily fill the gap unless you also put a limit on them.
Ok here is my conclusion of this problem . the bot function bad in a dense poke-stop area at the lowest walking speed stays in the same 100 - 200 meters all the time.
the bot should have settings for not visiting the same pokestop before 1 hour have past or 1.5 hours
I can say that this might fix the problem .
what i had to do was to turn up the speed to runing and set it to go to pokestops and gyms . then first the bot starts to move around like it shud.
only problem is that i want to walk and not run .
Short story bot do not function proper in walk mode in dens pokestop area
i put 1 of them back to walk speed and left the setting for pokestop and gym , it seems to do better now
i will se if it stays better if it do i will not post more in this tred , unless you want me to report back later . that is
thanks for all comments and everyone that spoke up and posted in this thread
Pintone, I'm assuming that limiting your pokeball just like my original advise fixed your problem.
However, this is really a bug that needs to get fixed by the programmer or the developer, as this has nothing to do with the pokefarmer setting, but a bug that I already explained earlier.
Your problem is similar to this,
I was surprised that no one else other than you complained about it. This will happen when your bag is full, and you may not know it esp when the bot is left unattended. This may also give you a soft ban, spinning the same pokestop over and over again for hours.
If I am to write a simple BASIC subroutine for this (which you should be able to understand, it will go like this.
50 T=T+1
1000 REM POKESTOP ENCOUNTER
1010 REM UNFARMED P=1 FARMED P=0
1020 IF P=0 THEN GOTO 2000
1030 GOSUB 5000
1100 IF T>=350 THEN P=1
1110 IF P=1 THEN GOTO 1000 ELSE 2000
2000 REM MOVE ALONG
2100 REM POKEMON ENCOUNTER
2110 T=T-1
4000 END
5000 REM SPIN
5010 REM EXECUTE SPIN ROUTINE
5020
5100 REM RESET POKESTOP FROM UNFARMED TO FARMED
5020 P=0
5030 RETURN
You will see that the bot is trapped in a loop and can only get out unless the value of T(your bag) is lessened below 350, either by setting a limit on the setup, or when it encountered a pokemon, assuming that capturing a pokemon is priority over spinning the pokestop, or by restarting the bot, and putting it away from pokestop and close to a pokemon.
I would say that If I am a programmer, I would insert the line
1005 IF T>=350 THEN GOTO 2000
to fix the bug.
But again, of course, my advise is unofficial and you should take it with a grain of salt.
