Originally Posted by
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.