Bot Development - 48 hours? Here's Why It Won't Happen.

[camorandis]

As we all know, Niantic has updated their server API. This means that all bots that previously relied on RocketAPI are no longer currently functional.

Nox Works. Why Not Bots?
The only difference between a bot and an emulator (Nox) is the method of which the experience is conveyed to Niantic.
- Emulators use native code structures and with the right software&root, they are practically unstoppable if you correctly spoof your virtual device's serial.
They will always work because they rely on updated apps in the Play Store, and these client-side changes will continue to work with Niantic's API.
- Bots use network code structures to make the global Niantic servers think that a physical device is connecting to the network, polling for updates and sending updates of their own. In order for this to work, there must be a seamless and efficient API protocol developed between the client&server.

API
An Application Program Interface is a communication hub. It streamlines all functions contained within a netcode environment, into an object-oriented class.
Note that for a major release to change its client/server API this soon after launch is a rare event. We knew they weren't ready for release, and this only reinforces that assertion.

- The new API is encrypted. Before the bot developers can even begin to change their data structures, functions, arguments, etc, that are necessary to spoof a Go connection, they have to figure out what algorithm to use - if the salt (hash) can be detected or polled - and even then, they still have to update endless lines of code to guarantee a working connection. If anything comes out in 48 hours I will be honestly surprised, but expect many bugs.

- Niantic made a server-side change that will probably put botting to an end for sure. Even if you have a bot programatically set to send 10,000 requests, Niantic is putting a 10,000ms delay on each request. This means that the requests will be polled on Niantic's end, and placed in a global Que that updates every 10 seconds.
Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

I am a programmer, fluent in C# and C++. I have been observing this fiasco go down, and wanted to give my 1 cent to a very confused community. Necro is a formidable dev, but I don't think that him - nor any other developer/reverse engineer - can get around the new server-side Poll Limit.

Get ready for Necrobot - Slowpoke Edition.

[Owneh]

As we all know, Niantic has updated their server API. This means that all bots that previously relied on RocketAPI are no longer currently functional.

Nox Works. Why Not Bots?
The only difference between a bot and an emulator (Nox) is the method of which the experience is conveyed to Niantic.
- Emulators use native code structures and with the right software&root, they are practically unstoppable if you correctly spoof your virtual device's serial.
They will always work because they rely on updated apps in the Play Store, and these client-side changes will continue to work with Niantic's API.
- Bots use network code structures to make the global Niantic servers think that a physical device is connecting to the network, polling for updates and sending updates of their own. In order for this to work, there must be a seamless and efficient API protocol developed between the client&server.

API
An Application Program Interface is a communication hub. It streamlines all functions contained within a netcode environment, into an object-oriented class.
Note that for a major release to change its client/server API this soon after launch is a rare event. We knew they weren't ready for release, and this only reinforces that assertion.

- The new API is encrypted. Before the bot developers can even begin to change their data structures, functions, arguments, etc, that are necessary to spoof a Go connection, they have to figure out what algorithm to use - if the salt (hash) can be detected or polled - and even then, they still have to update endless lines of code to guarantee a working connection. If anything comes out in 48 hours I will be honestly surprised, but expect many bugs.

- Niantic made a server-side change that will probably put botting to an end for sure. Even if you have a bot programatically set to send 10,000 requests, Niantic is putting a 10,000ms delay on each request. This means that the requests will be polled on Niantic's end, and placed in a global Que that updates every 10 seconds.
Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

I am a programmer, fluent in C# and C++. I have been observing this fiasco go down, and wanted to give my 1 cent to a very confused community. Necro is a formidable dev, but I don't think that him - nor any other developer/reverse engineer - can get around the new server-side Poll Limit.

Get ready for Necrobot - Slowpoke Edition.

Sniping should be pretty unaffected though.

[keyfrags]

Sniping should be pretty unaffected though.

Yeah, but for that we need working Pokevision or Skiplagged or similar sites.

[TechXPlays]

It'll be a bit if its all like this now. About time someone (besides the developers of the bots) with a brain spoke up

[Taranis]

- Niantic made a server-side change that will probably put botting to an end for sure. Even if you have a bot programatically set to send 10,000 requests, Niantic is putting a 10,000ms delay on each request. This means that the requests will be polled on Niantic's end, and placed in a global Que that updates every 10 seconds.
Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

Why should the bot be slower then walking? they will be at least at the same speed while the bot runs without you

[MonsterMMORPG]

So Brain farted Niantic Developers finally put api request time limit

[darknes4oy]

Until an official dev speaks im calling this post BS

[kaizooo]

a bot which injects into nox,should work then ,or did i miss something?

[cancelled]

As we all know, Niantic has updated their server API. This means that all bots that previously relied on RocketAPI are no longer currently functional.

Nox Works. Why Not Bots?
The only difference between a bot and an emulator (Nox) is the method of which the experience is conveyed to Niantic.
- Emulators use native code structures and with the right software&root, they are practically unstoppable if you correctly spoof your virtual device's serial.
They will always work because they rely on updated apps in the Play Store, and these client-side changes will continue to work with Niantic's API.
- Bots use network code structures to make the global Niantic servers think that a physical device is connecting to the network, polling for updates and sending updates of their own. In order for this to work, there must be a seamless and efficient API protocol developed between the client&server.

API
An Application Program Interface is a communication hub. It streamlines all functions contained within a netcode environment, into an object-oriented class.
Note that for a major release to change its client/server API this soon after launch is a rare event. We knew they weren't ready for release, and this only reinforces that assertion.

- The new API is encrypted. Before the bot developers can even begin to change their data structures, functions, arguments, etc, that are necessary to spoof a Go connection, they have to figure out what algorithm to use - if the salt (hash) can be detected or polled - and even then, they still have to update endless lines of code to guarantee a working connection. If anything comes out in 48 hours I will be honestly surprised, but expect many bugs.

- Niantic made a server-side change that will probably put botting to an end for sure. Even if you have a bot programatically set to send 10,000 requests, Niantic is putting a 10,000ms delay on each request. This means that the requests will be polled on Niantic's end, and placed in a global Que that updates every 10 seconds.
Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

I am a programmer, fluent in C# and C++. I have been observing this fiasco go down, and wanted to give my 1 cent to a very confused community. Necro is a formidable dev, but I don't think that him - nor any other developer/reverse engineer - can get around the new server-side Poll Limit.

Get ready for Necrobot - Slowpoke Edition.

Even if there is a 10 second delay, it still works. "Slowpoke Edition" or not

[Fadelol]

Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

No they won't. That would break the functionality of the regular client as well. Where are you getting this information? We simply do not know yet because the new API has not been reverse engineered yet. I mean, you are mostly correct but you portray this as the end of botting for Pokemon Go - something that we cannot conclude with the limited information we have so far.

The only reference to a 10 second response I am aware of is the interval for detecting new Pokémons and this was already implemented over 24 hours ago and did not have an immediate impact on bots at all.

Sniping should be pretty unaffected though.

No because all sniping bots require the same API functions as the usual bots to function. So does all of the sites like Skiplagged etc. required to detect the Pokémon in the first place.

[gustavowee2]

I am very upset, it seems that is the end of the bots ... Is there no chance of them coming back? Neither pokesnipers? Or unban?

[lapeiro]

that only means the bot will be 2x slower... we used to have the 5 sec delay anyway...

[rsxtypers]

As we all know, Niantic has updated their server API. This means that all bots that previously relied on RocketAPI are no longer currently functional.

Nox Works. Why Not Bots?
The only difference between a bot and an emulator (Nox) is the method of which the experience is conveyed to Niantic.
- Emulators use native code structures and with the right software&root, they are practically unstoppable if you correctly spoof your virtual device's serial.
They will always work because they rely on updated apps in the Play Store, and these client-side changes will continue to work with Niantic's API.
- Bots use network code structures to make the global Niantic servers think that a physical device is connecting to the network, polling for updates and sending updates of their own. In order for this to work, there must be a seamless and efficient API protocol developed between the client&server.

API
An Application Program Interface is a communication hub. It streamlines all functions contained within a netcode environment, into an object-oriented class.
Note that for a major release to change its client/server API this soon after launch is a rare event. We knew they weren't ready for release, and this only reinforces that assertion.

- The new API is encrypted. Before the bot developers can even begin to change their data structures, functions, arguments, etc, that are necessary to spoof a Go connection, they have to figure out what algorithm to use - if the salt (hash) can be detected or polled - and even then, they still have to update endless lines of code to guarantee a working connection. If anything comes out in 48 hours I will be honestly surprised, but expect many bugs.

- Niantic made a server-side change that will probably put botting to an end for sure. Even if you have a bot programatically set to send 10,000 requests, Niantic is putting a 10,000ms delay on each request. This means that the requests will be polled on Niantic's end, and placed in a global Que that updates every 10 seconds.
Even if the API gets deciphered, decrypted, and restructured - Niantic will only respond to 1 request at a time, 10 seconds apart. Rendering your bot not only slower than walking, but useless paperweight.

I am a programmer, fluent in C# and C++. I have been observing this fiasco go down, and wanted to give my 1 cent to a very confused community. Necro is a formidable dev, but I don't think that him - nor any other developer/reverse engineer - can get around the new server-side Poll Limit.

Get ready for Necrobot - Slowpoke Edition.

WRONG! 12-48 bots galore

are you ****ing stupid?

no game has ever stopped bots and never will

we the user will always be smarter then the devs

we bot they patch we bot

its been this way since the dawn of computers u ****ing jack nugget

and im sorry but you know nothing about c you ****ing toolbag

[chekhop]

WRONG! 12-48 bots galore

are you ****ing stupid?

no game has ever stopped bots and never will

we the user will always be smarter then the devs

we bot they patch we bot

its been this way since the dawn of computers u ****ing jack nugget

and im sorry but you know nothing about c you ****ing toolbag

Why you so mad? Chill bro

[Demmon]

Well, if maps can't scan enough times because of the delay, what about adding more clients scanning?

I mean, if the delay was 5 and now 10, why not scanning with twice as much clients?

That's a simple idea, I don't know how it really works