do you have a toon that can test it once I make the changes? thats the bigest setback im having is only 2 lvl 85s to test with.
I have several 85's spread over multiple accounts, so yes I could load up another and give it a go. A couple other issues I ran into from the follow up quests after those are as follows: Twinspire Keep - While killing the mobs for this quest it ran up the stairs towards the named mobs on the balcony above. It killed one I'm assuming because it attacked first. Then it jumped down to the area below where the imps were and killed a few more, then it was running into the wall. Not sure if I just glitched there or if something else was going on. I did the rest of the quests in this area by hand just in case (Fractured Forces, Unfair Trade, Smoke before Fire). Onward and Inward - After killing the named in the building, it turns the quest in outside, then mounts up to run back to town, instead of taking the chopper back. Again, not sure if anything can be done for that, just a minor annoyance if you are going for efficiency.
The changes are updated to the SVN, all exept the chopper, if you know how to use HB to get the objectID then i can add it but both my toons are past the quest and i cant find it on wowhead. please test those quest asap and let me know how they work
Will check those out tomorrow hopefully If I have time, got school work in the morning to fish and a mid-term to prepare for. Got a few more to report on before turning in for the night. 1. On the quest Kung Din, when there is an onscreen prompt to use fight for your life, the bot doesn't use it. It sits there until it times out and goes back to normal attacking. 2. Road Rations - Stalled out a lot due to trouble generating paths for the turtles that were underwater. 3. Family Heirlooms & Elder's Instruments - In the case of efficiency I recommend having the profile pick up both quests first as they are in the same area. Currently it picks up Family Herilooms, goes and completes it, comes and turns in in, and then does the same for Elder's Instruments. 4. Potency, Hue, Body - Potency and Hue work perfectly. Body on the other hand had some issues, it could of also been because of prime time in a crowded area. But once it got to one hotspot it just sat there until the alligators spawned. Rather than continuously patrol the hotspots for them. One would spawn near, it would go kill, then go back to the previous spot, making it look a bit bottish, so I ended up finishing this one manually and calling it a night.
Got to Temple of the Jade Serpent accepted quests when in and stopped...wouldnt move..I manually completed then it Keeps saying "Can not turn in quest They Call Him... Stormstout (ID: 32019) because I don't have it in my quest log! (Or do I: False" Is this the end? Cause im still only 85 and that quest is a Lvl 87 quest
Thats as far as I have gotten, you should have made it to 86 at least, I made it to 87 with all rested xp
great profile ! exept some buggs whit the quest at the serpent temple otherwise it great and easy to use !
Its odd, i'm dual boxing with a lock and pally, the lock picked up the quests just fine and went off to kill stuff, the pally is still standing at the first quest giver clicking on the guy.
I dont have the Quest IDs but the 4 in Jade Forest with SI-7 where the Bot tells me to continue after u do the out of body sections. I turned the Bot off and did them and after I turned the Bot back on it just wants to talk to Sully. Can you please help me walk threw how to make it work again. BTW: So far my mage has gone threw flawlessly! Figured it out...
this is a problem with HB when it checks to see if the quest is complete, the profile is coded to only get the quest if its not completed.
My bot stuck at repair and selling vendor it kept saying Moving to Type: Sell, Name: Jadori Ironeye. Any suggest? Im newb anyway, thanks
without quest log i realy dont know whats the problem, where you are and why cant the bot find the vendor upload log please
check my second post at main thread and clean cache for now, just close bot clean cache and restart probably will fix