So I got into botting PokemonGo yesterday because I wanted to see what it was all about..
And NecroBot was working just fine and when I tries starting it up this morning it just started thrwing me exceptions.
This is what it looks like, are they doing an update?
And no my account is not banned.
And yes the account name & password is correct.
Probably temporary banned, Pokemon GO botting was dead ages ago.
(Mar 7, 2017 07:23 PM)Tsunfire Wrote: Probably temporary banned, Pokemon GO botting was dead ages ago.
Not banned, can play on my phone and what not, and this bot was updated like 2 weeks ago so its back, you're welcome.
(Mar 7, 2017 07:31 PM)passwords Wrote: Not banned, can play on my phone and what not, and this bot was updated like 2 weeks ago so its back, you're welcome.
Well of course you can play but exceptions arise when the bot has inhuman config which result in a temporary ban.
Mar 7, 2017 07:34 PM
(This post was last modified: Mar 7, 2017 07:38 PM by passwords.)
(Mar 7, 2017 07:32 PM)Tsunfire Wrote: Well of course you can play but exceptions arise when the bot has inhuman config which result in a temporary ban.
How come its working on other bots then? ;s
Sorry i'm just finding this very weird.
Why im not using the other bots you might be wondering..
Because Necro has the best exp rate.
I also ried with with newsly created accounts..
I think there has been an update and thats probably it.. I'll keep this thread updated.
(Mar 7, 2017 07:34 PM)passwords Wrote: How come its working on other bots then? ;s
Sorry i'm just finding this very weird.
Why im not using the other bots you might be wondering..
Because Necro has the best exp rate.
I also ried with with newsly created accounts..
I think there has been an update and thats probably it.. I'll keep this thread updated.
Exp rate is meaningless when you're capped daily. The issue is that the login URL changed in 0.57.4, and they just killed the old one.
(Mar 7, 2017 07:23 PM)Tsunfire Wrote: Probably temporary banned, Pokemon GO botting was dead ages ago.
Botting never died, and won't die until it's not profitable anymore.
Mar 7, 2017 08:10 PM
(This post was last modified: Mar 7, 2017 08:10 PM by passwords.)
Quote:Exp rate is meaningless when you're capped daily. The issue is that the login URL changed in 0.57.4, and they just killed the old one.
Do you reckon they will update te bot anytime soon?
(Mar 7, 2017 08:10 PM)passwords Wrote: Do you reckon they will update te bot anytime soon?
Of course.
Bossland is currently looking into the login procedure. Good chance they'll release it.
They're pretty good with time, so I'd say 1 to 3 days before that's public. Then it's up to the dev to update the bot.
Another option is for someone else to mitm the request, but it's one of those things that requires specific tools.
(Mar 7, 2017 08:16 PM)SL x TnT Wrote: Of course.
Bossland is currently looking into the login procedure. Good chance they'll release it.
They're pretty good with time, so I'd say 1 to 3 days before that's public. Then it's up to the dev to update the bot.
Another option is for someone else to mitm the request, but it's one of those things that requires specific tools.
I guess I can wait that long, thank you sir! 🤝
so if u have any news please post, because i have your same prob..thanks!
(Mar 9, 2017 03:47 AM)Pakimerda89 Wrote: so if u have any news please post, because i have your same prob..thanks!
If the bot you're using can't login, then it's
a) Using the free hashing method. That has been killed.
b) They're sending an invalid hash for the initial request. You'll have to wait for them to update. Shouldn't be long now. I found my mistake, which is also the same for a few public APIs.
Mar 9, 2017 05:20 PM
(This post was last modified: Mar 9, 2017 05:20 PM by Zero.)
pretty sure botting is dead nowadays...
probably temp ban
There was an api update that changed the way accounts login. It made all bots go down for awhile but they should be back up by now. I am not entirely sure about necrobot
(Mar 10, 2017 08:52 AM)Defiance. Wrote: There was an api update that changed the way accounts login. It made all bots go down for awhile but they should be back up by now. I am not entirely sure about necrobot
Funny enough, it wasn't the login change. They started validating the hashes, which caused issues on the initial request on some bots + public APIs. 1 extra byte causing a bad hash ...
Not everything was affected.
It's perfectly working for me. :D
|