What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

FlyTo behavior not restoring loot settings

B

btravis6928

New Member
Joined
Jan 15, 2010
Messages
13
Reaction score
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.
 
btravis6928 said:
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.
Click to expand...
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
 
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.
 
Just thought I would let you know that it hasn't happened again since that the day I posted this.
 
You must log in or register to reply here.
Back
Top