• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • FlyTo behavior not restoring loot settings

    Discussion in 'Archives' started by btravis6928, May 21, 2011.

    1. btravis6928

      btravis6928 New Member

      Joined:
      Jan 15, 2010
      Messages:
      13
      Likes Received:
      0
      Trophy Points:
      0
      In the OnStart() method of the FlyTo class, all loot settings are set to false. There is a comment stating that these settings will be restored when the behavior completes but my settings are not being restored. So every time the FlyTo class is used, the bot stops gathering herbs and minerals, stops looting mobs, and never starts again. I have to go in and check the checkboxes again manually. Sometimes it's running without loot settings for a few hours before I get a chance to check on it again so that's a lot of missed loot.
       
    2. chinajade

      chinajade Well-Known Member Moderator Buddy Core Dev

      Joined:
      Jul 20, 2010
      Messages:
      17,540
      Likes Received:
      172
      Trophy Points:
      63
      This post explains a little bit about what we believe to be going on...

      The problem is much wider than FlyTo. And the problem has existed ever since the SetPullDistance and DeathKnight behaviors went in. (i.e., much earlier than FlyTo was available).

      I've tried working with Nesox to isolate the problem, as it apparently doesn't happen for everyone. He has made a change for the next drop that may make things better, but we don't know yet. I wouldn't hold my breath... we really need to make the problem consistently repeatable in order to chase it.

      cheers,
      chinajade
       
    3. btravis6928

      btravis6928 New Member

      Joined:
      Jan 15, 2010
      Messages:
      13
      Likes Received:
      0
      Trophy Points:
      0
      Thanks. I didn't realize this was already a known issue as it just started happening for me yesterday. I will keep an eye on it for a while today and see if I was just triggering the suspected gui overwrite. I'm not a c# programmer but it sounds like a simple observer pattern would fix this issue.
       
    4. btravis6928

      btravis6928 New Member

      Joined:
      Jan 15, 2010
      Messages:
      13
      Likes Received:
      0
      Trophy Points:
      0
      Just thought I would let you know that it hasn't happened again since that the day I posted this.
       

    Share This Page