-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot should pause/slow down when its raining near his coordinates #4595
Comments
I really can't see the purpose of this. They won't be factoring weather into bot detection as there'll still be players who go out in all sorts of weather. All this would be doing is adding an unneeded level of complexity. |
No reason why it can't be a feature request though, I'd be surprised if anyone wanted to implement it though. Let's see if anyone replies :) |
No problem with this remaining to be a FR, but I imagine this will hang around for quite some time. |
The bot should also walk slower during sales since there is obviously more people in the street during these days. |
Hmmm, the sarcasm is strong in this one LOL |
Sorry, this is too extreme for even the next 6 months worth of work. Plus the amount of work they would have to do to determine such things and consider them conclusive for bans is... unlikely to happen. |
Short Description
This bot is meant to be the most human-like possible, why not try to simulate a pause/slow down outside while its raining near the coords he is moving.
Possible solution
Using the random pauses type, linked it with a openweather provider, we could trigger a pause while the weather provider reports bad weather near the coordinates, it would be configurable like "pauseIfRaining" or "pauseIfBadWeather", there could be some kind of setpoints for define this kind of bad weather.
How it would help others
This won't actually avoid the bot being detected, unless Niantic does some kind of pattern analysis with weather cross data, but it would make the bot behaves more like a human on that situations.
The text was updated successfully, but these errors were encountered: