• Visit Rebornbuddy
  • Fixed: After finishing an enqueued user action rethinks

    Discussion in 'Pokefarmer Support' started by jokerjr, Jan 11, 2017.

    1. jokerjr

      jokerjr Member

      Joined:
      Dec 24, 2016
      Messages:
      34
      Likes Received:
      0
      Trophy Points:
      6
      Fixed: After finishing an enqueued user action rethinks about what to do next, to prevent "silly bot behavior".

      can someone explaine to me what this fixed please because if i ask him to walk to a pokestop lets say 5 blocks away he still ups and walks all the way back to get pokemon he seen 5 blocks back really need some way to like reset the bots thinking or something and not have to log out and log back into the game all the time
       
    2. iCKR

      iCKR Moderator Moderator

      Joined:
      Jun 12, 2012
      Messages:
      4,270
      Likes Received:
      43
      Trophy Points:
      48
    3. ssrpengel

      ssrpengel New Member

      Joined:
      Nov 5, 2016
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      0
      This is an answer to what I believe is occurring now compared to before, and a few ideas about how things could work. I don't think there is a bug that requires a support request and logs posted, but merely that the silly-bot behavior is still silly, just in a different way and not what the OP wants, yet... Maybe this is more of a discussion item, but I think the developer(s) should read what is said since only they can change what happens.


      What USED TO happen is:

      After finishing an enqueued walk/loot, the bot would walk back to the pokemon closest to the start then catch all the pokemon along the way and end up at the pokemon closest to the destination so while the bot walked the enqueued path about 3 times, you do end up close to the destination.

      Now, the NEW 169 behavior is:

      After finishing an enqueued walk/loot, the bot starts catching pokemon closest to the destination, but catches every pokemon it saw along the way so eventually ends up back closest pokemon to the start of the walk, and while it only walks the enqueued path twice, it doesn't end up when you told it to walk to, which is the OP's goal of enqueuing a walk, I think.

      What a REAL PERSON does is:

      Walks the path AND catches/spins (or ignores pokemon/pokestops) along the way as they were walking. Humans DO NOT remember every single pokemon they saw during a 5 block walk (to use the OP's example) and then go catch them, either in reverse order (now) or the same order (before) as they were seen. This makes the bot more thorough than a human but it makes it impossible to actually end up at a purposeful destination unless no pokemon were encountered during the walk, which is rare in a good area.


      I think what the OP is wanting is a way to end up at the destination and start catching pokemon that are seen once they arrive and FORGET/IGNORE the pokemon seen along the way. This is what happens if you are riding your bike or diving a car between areas rich in pokemon and don't want to waste time or drive dangerously catching the few along the way. This is also what the OP is simulating by enqueing a walk, waiting for it to happen, then stopping and restarting the bot so it doesn't remember any pokemon it saw while walking.


      What I'd propose is keeping the current behavior as a useful bot-like behavior for those who like catching all seen pokemon along a boomerang path, but ADD THE OPTION TO WALK-BUT-FORGET/IGNORE pokemon that were seen along the path and only catch the pokemon if they are seen again after the enqueued walk is over.

      An alternative to having another menu option or two (to forget/ignore) to the pokestop-click menu would be to have a checkbox or toggle-button somewhere in the UI while the bot is running, during an enqueued walked or even otherwise, so it doesn't remember any pokemon while the toggle is disengaged, and could be reengaged after the enqueued walk is over. It would be more useful to have the catching/spinning automatically resume upon reaching the destination, but if that's too difficult just adding a toggle would allow a user who wants to sit and watch the bot walk, manually control when catching/spinning is occurring, just like stopping and restart the bot does, now, but without the somewhat dangerous relogging in. The problem is we can't change any of the settings while the bot is running, even though some make sense to be changed while it is running--whether to catch pokemon or spin pokestops being two obvious ones.

      Being able to toggle catching/spinning on an off in real time would help people continue to walk to hatch eggs if they're close to having spun or caught the maximum allowed items in a day. The only problem would be that you couldn't turn off both catching and spinning because then there'd be nothing to walk between that would automatically disappear like happens now when you catch a pokemon or spin a pokestop and it becomes unavailable so the bot turns its attention immediately elsewhere.

      For me the ultimate goal would be to do things like a human and catch (or ignore) any pokemon seen along the walk while an enqueued walk is taking place. This requires more sophistication, where there is a purposeful walk occurring at the same time as the ad-hoc and opportunistic catch/spin activities, instead of the enqueued walk and the opportunistic activities being mutually exclusive, but it would be the most efficient as the enqueued walk distance is only travelled once, and the pokemon are all caught along the way. Obviously there needs to be a mode where we can walk without the delay of catching/spinning, too, as proposed above.
       
      Last edited: Jan 11, 2017
    4. jokerjr

      jokerjr Member

      Joined:
      Dec 24, 2016
      Messages:
      34
      Likes Received:
      0
      Trophy Points:
      6


      thank u ssrpengel that is what i was totally meaning with my post if i asked it to walk 5 blocks to a pokestop then i would like it to stay there not walk all the way back and there is NO log that needs to be posted that seem to be the only thing the mod like to post for some reason and not reading into the question that was asked at hand
       
    5. ssrpengel

      ssrpengel New Member

      Joined:
      Nov 5, 2016
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      0
      Just add a random log that includes an enqueued walk and is from 169.
       
    6. CAcove

      CAcove Moderator Moderator

      Joined:
      Dec 14, 2014
      Messages:
      896
      Likes Received:
      59
      Trophy Points:
      28
      Actually we require the most recent logs of the issue from the last time it happned. The fresher the better, not random logs.
       
    7. ssrpengel

      ssrpengel New Member

      Joined:
      Nov 5, 2016
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      0
      In general what you say about most recent logs is true, but in this situation any log with an enqueued walk from 169 (or later until the behavior is changed) would be as relevant as any other for this particular issue if you read and understand what is being discussed. It's not really a bug, just a this-should-be-designed-better-and-is-worse-than-before (for the OP) situation. The bot is working as intended, just not very useful for the OP, where the OP is not being unreasonable in their expectation for how things should work and what is useful. My initial reply was to explain the bot's behavior change to the OP and posit alternative solutions to the developers.

      The only relevance a log-file has is to demonstrate the OP is operating version 169 and not a previous version so the situation they are describing is not for a previous version so is irrelevant to the discussion. Again, reading and understanding what is being talked about will make this obvious.

      BTW, OP = original poster.

      As a summary of what is being discussed, here is a step-by-step description of what to do and what occurs to reproduce what the OP is describing:

      • Wait until it is just after 4 minutes past the hour so the Pokémon won't get cleared from the map and become invisible as they are collected partway through the demonstration!
      • Start up PF 169 (or newer) and login.
      • Set the location of the bot (the yellow pokeball) to be on one side of a known dense pokemon-nest area.
      • Start Bot.
      • Observe the bot collecting pokemon and looting pokestops in the general area where it was started.
      • Click on a distant pokestop on the other side of the dense Pokémon area where the bot has not been, yet, and choose Loot Pokestop...
      • Observe the bot stop collecting and begin walking directly to that pokestop with pokemon being displayed near the path as they are encountered but not collected during the walk.
      • Wait for the bot to reach and loot the destination pokestop.
      • Now this is where things are different with 169:
      • Observe that the bot will start collecting with the closest pokemon to the just-looted pokestop and continue collecting each pokemon it encountered during the walk and any new ones that show up during the collection.
      • Wait until all the pokemon that were encountered during the enqueued walk have been collected.
      WHERE IS THE BOT, NOW?
      It will be back near the starting point most likely. The OP wants the bot to be close to the destination point, not the starting point.

      Two simple fixes are:

      Don't remember any pokemon encountered during the walk, so the bot will only be collecting newly encountered pokemon near the destination after the walk has completed and not walk back along the path it just came because there are pokemon remembered along that path, which is the undesirable behavior the OP is wishing didn't happen.

      OR

      Collect any pokemon encountered during the walk immediately, as they are seen while walking, instead of merely remembering them and collecting them after the walk has completed.

      In my mind both solutions should be available to choose from the menu, the first for speed so the bot doesn't waste time collecting along the way, or the second for thoroughness because it does collect all the way.

      In each case the bot will end up at the destination specified for the enqueued walk, instead of near the beginning. And if I use the second solution, then to return to the beginning of my walk, I merely need to enqueue another walk back to the beginning.
       
      Last edited: Jan 12, 2017
    8. iCKR

      iCKR Moderator Moderator

      Joined:
      Jun 12, 2012
      Messages:
      4,270
      Likes Received:
      43
      Trophy Points:
      48

    Share This Page