Why they can't make a bot of simulator(NOX or BlueStacks)?

[peter5566]

Why they can't make a bot of simulator(NOX or BlueStacks)? And don't focus(Don't be obsessing) on unknown6.

 

[Phazzer99]

There's a few reasons:

First, it'll be easier to maintain. There's a helluva lot of effort going into it now, but once it's figured out Niantic will have to do the same amount of work (if not more) to change it on their end so what's been figured out now no longer applies. With a client interface, all they would have to do is update the client. (Look at Honorbuddy and WoW, every time Blizzard drops a patch HB is down for days)

Second, more features. With direct API access, you can do whatever you want. By connecting to an emulator (or directly to a phone) you're limited by what the connection to the emulator/phone can provide.

Third, it's more fun. Speaking as someone who works in software development, the more challenging route is usually the more interesting one.

 

[Tinytox]

There's a few reasons:

First, it'll be easier to maintain. There's a helluva lot of effort going into it now, but once it's figured out Niantic will have to do the same amount of work (if not more) to change it on their end so what's been figured out now no longer applies. With a client interface, all they would have to do is update the client. (Look at Honorbuddy and WoW, every time Blizzard drops a patch HB is down for days)

Second, more features. With direct API access, you can do whatever you want. By connecting to an emulator (or directly to a phone) you're limited by what the connection to the emulator/phone can provide.

Third, it's more fun. Speaking as someone who works in software development, the more challenging route is usually the more interesting one.

That's all very valid, I'd like to add that any android emulation based botting is usually pixel based, AutoIt, etc. While this can work all well and good (mybot.run for Clash of Clans is a perfect example), it takes more maintenance, operates poorly in comparison, and generally speaking, have less features/features take longer to build out/are less stable.

Things that operate within an Android environment are also usually easier to detect, assuming that the tool lived inside the emulation (Like an Android app), which means process/running application based bans would probably go up eventually.

 

[NTCLANNAD]

Deleted

 

[NTCLANNAD]

That's all very valid, I'd like to add that any android emulation based botting is usually pixel based, AutoIt, etc. While this can work all well and good (mybot.run for Clash of Clans is a perfect example), it takes more maintenance, operates poorly in comparison, and generally speaking, have less features/features take longer to build out/are less stable.

Things that operate within an Android environment are also usually easier to detect, assuming that the tool lived inside the emulation (Like an Android app), which means process/running application based bans would probably go up eventually.

Not agree.

First and Most importantly, Graph recognition is 100% SAFE. PC end android simulator based bots are the safest ones in Clash of Clans. They survived every single official *****down on bots. Not a single PC bots were detected. Because its impossible to detect PC based bots that dont read memory. On the other hand, nearly all Iphone/mobile phone based bots got detected and many of them got permanently banned.

Second, Function/features wise, they certainly have more features than API based bots. A good graph recognition bot can do anything humanly possible. graph recognition technology is already very advanced. Its just take some time to make them perfect.

Third, in terms of maintenance issue. Clearly, in graph recognition based bots , the works related to updating bots after each patch would be peanuts compared to the current catastrophic problem we have with the new API thing. And the API problem can never be solved by a single company, its a nightmare

 

[peter5566]

Fix bot - 2 week later - fix API or any unknownX(Niantic) - 2 week later - Fix bot
and so on indefinitely

 

[Phazzer99]

Fix bot - 2 week later - fix API or any unknownX(Niantic) - 2 week later - Fix bot
and so on indefinitely

That's the thing, Niantic CAN'T 'fix' the API once it's *****ed. In software development, the back-end systems are anywhere from 50-90% of the effort that goes into what you're working on. The stuff the end-user sees is trivial compared to it. In order to compensate for the API being *****ed, Niantic would basically have to rewrite the entire (or a very large chunk) of the game from scratch. They would then have to do the same thing to all of their server code. They would then have to modify the UI portion of the game to work with the new code. They would then have to lock out all of their users from the app until their phone can update the app. Niantic didn't even do this when writing Pokemon Go. The underlying systems are effectively the same as Ingress, all they did was change some of the field names and make a new UI. Undoing the work that is going into *****ing the API right now would be virtually impossible for Niantic to pull off without spending massive amounts of time and resources.

It's important to note that what is happening right now is not due to an update that Niantic made to the API. What Niantic has done is start validating a hash that has existed since day one. The data has always been there, they just started actually using it.

 

[Dosenbeer]

That's the thing, Niantic CAN'T 'fix' the API once it's *****ed. In software development, the back-end systems are anywhere from 50-90% of the effort that goes into what you're working on. The stuff the end-user sees is trivial compared to it. In order to compensate for the API being *****ed, Niantic would basically have to rewrite the entire (or a very large chunk) of the game from scratch. They would then have to do the same thing to all of their server code. They would then have to modify the UI portion of the game to work with the new code. They would then have to lock out all of their users from the app until their phone can update the app. Niantic didn't even do this when writing Pokemon Go. The underlying systems are effectively the same as Ingress, all they did was change some of the field names and make a new UI. Undoing the work that is going into *****ing the API right now would be virtually impossible for Niantic to pull off without spending massive amounts of time and resources.

It's important to note that what is happening right now is not due to an update that Niantic made to the API. What Niantic has done is start validating a hash that has existed since day one. The data has always been there, they just started actually using it.

Awesome! Thanks for that!

 

[NTCLANNAD]

That's the thing, Niantic CAN'T 'fix' the API once it's *****ed. In software development, the back-end systems are anywhere from 50-90% of the effort that goes into what you're working on. The stuff the end-user sees is trivial compared to it. In order to compensate for the API being *****ed, Niantic would basically have to rewrite the entire (or a very large chunk) of the game from scratch. They would then have to do the same thing to all of their server code. They would then have to modify the UI portion of the game to work with the new code. They would then have to lock out all of their users from the app until their phone can update the app. Niantic didn't even do this when writing Pokemon Go. The underlying systems are effectively the same as Ingress, all they did was change some of the field names and make a new UI. Undoing the work that is going into *****ing the API right now would be virtually impossible for Niantic to pull off without spending massive amounts of time and resources.

It's important to note that what is happening right now is not due to an update that Niantic made to the API. What Niantic has done is start validating a hash that has existed since day one. The data has always been there, they just started actually using it.

They can just find a way to detect who is using it and ban accounts, sue websites. In fact, I think Niantic already is capable of flagging API botting and GPS spoofing users. Whilst graph recognition bots never get detected, unless its running on a mobile phone. So, for our bot users, its not about hack the API, its about how to avoid permanent ban. Actually those who are currently hacking the API already said they dont support bot and they have hinted API bots can be detected.