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

Whenever I walk to a FP it stops....

Zeo80

New Member
Joined
Oct 21, 2010
Messages
61
Reaction score
0
Code:
Moving to Type: Fly, R: Use, Light's Hope Chapel, Eastern Plaguelands
Could not find vendor: '' blacklisting!

Untill I manually click the FM-NPC and then it goes further.

Code:
TaxiMap is opened! Updating known nodes list.
Taking flight path to Light's Hope Chapel, Eastern Plaguelands

And the buglog:
Code:
Cleared POI - Reason Took Flight Path
Cleared POI

What is going on?
 
there is a bug on flight paths on latest Hb
should be fixed on next release
 
This bug still exists. When is it going to be fixed?

if you are getting this after a wow dc/relog is something that cant be fixed

you have to close/resart both wow and Hb in that case
 
No. Happens with freshly restarted wow and hb. Seems to happen in Stormwind only as far as I can see. Had it on 3 bots, all have been launched in Stormwind, none took the flightmaster until i manually clicked him.
 
Reproduced the issue. It really seems it just concerns the Stormwind flightmaster (haven't tried Ironforge as my profile didn't led me there). Log attached.
 

Attachments

After the profile took me to Ironforge, same happened there. Outside the main cities interacting with flightmasters seem to work properly.
 
Well, you're lucky the npc gets blacklisted at least. There are a lot of flight points where I just get stuck (plus the problem you've reported with the blacklisting).

"Learning new flight path"

Eventhough I've turnt Learn new Flight Paths off in Hb and in the profiles. :( This is extremely annoying considering I'm trying to level 6 toons and am almost not home at all. It's absolutely essential for a bot and imho should get priority over pretty much anything else.

Funnily enough, when I have both Learn new Flight Paths and Use FLight Paths turned off, the bot will stell talk to flight masters and do the "updating known node list" thing. This might help you when it comes to fixing the issue, eventhough I strongly doubt that's gonna happen anytime soon.
 
Last edited:
Back
Top