Almost 50% off all flight masters are bugging out now.

This is just a log from one of many many many.

Acting:
Runs to the Flight master, going to train in orgrimmar (ally has problems to) does not open the flight master window but blacklist the vendor, turning around to run to orgrummar runns 150 yards unblacklists the vendor and turns back, and does this over and over again and again and this is with a fresh HB installation.

View attachment 28147

 

I saw that a few days ago... was in Hellfire Penn and the toon kept running up to the FM and opening the window (which did open), running away only to stop, run back and repeat. Since I was working with a grinding profile that I knew was literally just 'out of the gate', I just got my toon mounted, and flew him out and restarted the profile... worked fine after that. I've seen many other times where the FM simply wasn't working so I had to open up the profile and finger out where he was trying to get to and resetart the profile there. I'm at work so I can't post a log... but next time I see this at home, I'll drop one in as well.

 

Wow... *hits head with telephone book*, why didn't I think of doing that???

Thanks Tony!

 

Lol. Tony your responses make me laugh a little every time I see one. Short, but the info of what and why are there. Literally perfect.

 

SAdly that was another problem when he was standing still at FP spamming him, this is another issue, he can not find Flight master, so the only way to do it must be to disable "Use flight paths"

The problem is this. "[18:39:21:425] Could not find vendor: '' blacklisting!"

 

Screw flight masters. Besides mounts are cheap and you get them really early now. I remember trying to save up5k for my flying 280. It was ridiculous, and literally an achievement. Now it's handed out like candy.
Blizzard is making the game too easy.

 

Well after reading my logs it all seemed to be when it was "Flying to trainer" so i disable train new skills, kicks profile does this anyway old habit to have that enabled, it does seem to have fixed the problem as well.