PF Trap
In this post the Admin mentioned a trap they stepped into. This might have led to the bans meaning the bot could actually be safe now. Only time will tell.
HatchingEggy - Today at 3:15 PM
Dear @everyone,
Pokefarmer and Lazymon are in the process of being updated to a new version.
I have to admit that we stepped into a trap with Build 170. (GG Niantic!)
We updated in the middle of an ongoing "ban-wave" and server issues from Niantic and this caused a lot of false positives and assumptions of what is going on however a few moments later we published an updated Build .171 which with a bit of time seems to have fixed the issue.
Pokefarmer is stable and runs smoothly which is fine. It's verified that our API implementation is working well and implements it correctly.
All other developers we know are already informed to fix their code to avoid the trap that we've stepped into. That trap I am talking about is what caused massive captchas.
A side note for developers: Niantic still has the old API opened and I highly recommend to not use it as it'll flag your account to get banned.
So, what did change in this update for Pokefarmer and Lazymon?
Besides a single label that shows the current supported API there are no new features
or fixes in Pokefarmer or Lazymon. All changes are under the hood to guarantee stability and the latest API features.
It's time to document our findings and to pick up our usual work. Lazymon and Pokefarmer updates continue on Sunday/Monday.
Thank you for being patient and helping each other.
P.S.: We're extending all Pokefarmer, Lazymon and Hashing Keys to add another day as we were ready 23 hours after that forced version change.
Love,
Eggy
P.P.S We truly are sorry for any users that may have been caught in the Niantic trap, we thank you for continuing to have faith and trust in us.
