What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

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!

problems in the update 133

Problem here also. See attached logfile.
Inventory bag is full but you also don't get the XP.

Edit: Logged into Nox and no problems with spinning the stops. Get the " bag is full" message but receive the XP.
 

Attachments

Last edited:
There is another problem i have noticed with the 135 update
Before, when i stop the bot and restarted it. The previous list of the catched pokemons witll canceled and a new list would start all over again
Now, the new list continues with the old one,so i can't tell exactly how much pokemon i caught in a single log session
 
updated the bot to 136
failed at looting pokestop when the inventory is full ==> problem solved
thanks a lot guys

but the (CAUGHT) LIST is Still having the same problem.

when i stop the bot and restart it, the (CAUGHT) List continue with the old list of the caught pokemons. it does not cancel the old list and start with a new empty one like it used to be
 
updated the bot to 136
failed at looting pokestop when the inventory is full ==> problem solved
thanks a lot guys

but the (CAUGHT) LIST is Still having the same problem.

when i stop the bot and restart it, the (CAUGHT) List continue with the old list of the caught pokemons. it does not cancel the old list and start with a new empty one like it used to be


What what do you mean by that?
Do you have a screenshot?
 
the problems in 136 update

1. after pausing a a pokestop, i get ""session expired, relogging", the bot won't relog, so it would stop

session expired, relogging.... stopped.webp


2. when i try to relog manually, it says "could not connect to login servers". so i have to close the bot completely and open it again to be able to restart it.

could not connect to log in server.webp

3. once i restart it again the no. of caught pokemons after restarting the bot continues with the previous counting instead of restarting the count from (Zero) like it used to be

no. of caught pokemons after restarting the bot.webp
 
Back
Top