no looting #101
Comments
|
#102 |
|
nope @samuraitruong just few seconds ago |
|
Agree with it no looting here also. |
|
ot: guys you should not make your pogo nick public to avoid direct ban. |
|
@REDESTOR i removed your images, crop them please or paint over username. |
|
@kalamera thanks for the lookout |
|
@REDESTOR post your config, it helps identify issues |
|
{ |
|
got this since 9.7 and above from noxxdev just 9.6 works for me |
|
+1 |
|
@REDESTOR Not to be contrary, but these screenshots do not show the behavior fixed in 102. That is, multiple pokestops visited without looting. This just proves a softban. There are numerous ways this could be caused. Do you have a shot showing sustained pokestop visits but no looting? @samuraitruong Correct me if I am wrong, but unless this bot was compiled from source, the #102 fix is not in the bot until a release. |
|
Correct |
|
@Silph-Road OK, thanks. So again, not to be an ass, but this is proof of nothing but a softban (IP, activity, etc.) We won't know if #102 fixed the issue unless we compile ourselves or wait for 0.9.8.9. Not sure if the botting community at large understands how fixes are folded into the final product. Fixes are not in the bot you are downloading unless they are compiled from the source or part of an official release. Even noting behavior that shows an issue is sort of a waste of time unless you have a freshly compiled or released bot. That sound right? |
|
True, the fix just got pushed in the last few hours and it's something that we test and when it seems appropriate we push a compiled release. In simpler terms for users who don't understand how fixes work: Fixes are not live or real time as the fix is located in the zip you download. Thus, many fixes are package together in one single release. A more pressing matter: |
|
you see, same release, few people work, few report doesn't work. We know that is bug, but how to find it. only when we debug it. One you are on this , people reference to a pull request you must know that code fix, not a release . you can download compiled from CI. every pull request will be build automatically. |
|
@samuraitruong @Silph-Road Thanks guys for explaining that. Great info there. You might want to sticky that to the "Report issue" text. :) Unfortunately, you still need users that are willing to read before posting. A good place to check if an issue has been addressed already would be by checking the "Closed" issue section first before posting. Is that correct? I know how frustrating it can be to have the same bugs reported over and over because the fixes haven't been released yet. |
|
No prob, yes I was planning to add that fix explanation to the issues template! And I like the idea of adding check closed issues. I dunno how I missed that :-p We can I guess add the auto appveyor links, hmm just might start doing that. |
|
Try this, it should have fix incorporated. |
|
Post back with feedback and you can reference 0f2bd71 as the build version. |
|
@Silph-Road I will give it a try a little later and let you know. Thanks again. |
ghost
added
the
|
@Silph-Road Started happening again with the bot from the link you provided. I purposely put the bot in a tight area. Check the time stamps. It looks like enough time has passed between like stops for them to be good again, but they were still showing purple on the GUI and they weren't looted. |
|
@Silph-Road, @ajns73 keep having the same problem with the new version, please look at the time stamps in both screen shots, there are just few minutes of difference, a soft ban doesn't go in minutes, i just paste an example of the behavior, if i let it run it continues for hours without looting advertising softban (false), and when i check in older version or cell phone it runs fine ....almost check with different acc |
|
@REDESTOR @Silph-Road Mine issue does not last that long. It does loop every hour i.e. - when it gets to not looting, it will not loot 4 or 5 stop is a row. Then it goes back to normal for a while, then loop not looting. However, that was with the linked version. Since the release (0.9.8.9) I have seen normal behavior. To be fair, this coincided with a location change. In other words, I broke the golden rule and changed too many variables at once.
|
|
9.8.9 attention time stamps... |
|
@REDESTOR FYI, I never actually got a softban (false or otherwise) like you did. I did however see the behavior from your bottom screen. Bot almost seemed l frozen and it just sat there on the visualizer. Again, to be fair, there are Google Walk problems right now that are producing the same result (lack of movement on the visualizer), so I don't know if those are realted. |
|
well 9.6 use google api and has no problem for me, and i just get that "pseudo/false" soffban with 9.7 and above, i just made 9.8.8 run well once for about 4 hours, stop it then try again and get the pseudo softban problem... maybe if recompile it based on 9.6 just adding the new stuff ...don't know just saying for me is the most stable version...guess i'll keep using 9.6 till it dies... or get a permaban... |
|
@REDESTOR Have you tried 0.9.9? That solved the other Google Walk issues. If they were related to your issues with looting, perhaps this will solve that. I have not had a looting issue in 3 hours. Like I said before, though, I moved my bot. Different location and then back home. EDITAre you using an elevation API? I have long suspected that this might cause this behavior. Space is 3D, walking into the side of a hill doesn't get you to the pokestop ON TOP of it. You know what I mean? |
|
Hmm.. ill wait a few hours and try it different location...i used to bot only in my neighbor and 2-3 snipes a day with pokes above 95iv |
|
@REDESTOR Same here. Last night I moved it to my work neighborhood overnight. This morning I moved it back to my home neighborhood. As I said before, I changed to many variables at once so I don't know what really did the trick. |
|
nope continue false ban... |
i made the bot fuction once, but now its no looting at pokestops, and advertise of a FALSE softban...I check it with 9.6 and my phone and there was no problem fix it please...
The text was updated successfully, but these errors were encountered: