Kaz No, it doesn't look like it. It's just been running on it's own as a fresh 90 start. How do I fix that?
The 'InteractWith' you're stuck on is the bot trying to obtain "Kaz the Shrieker" as a follower - but it seems that Kaz isn't at the spot your bot is standing? Hmm, here's an edit with Kaz taken out. I'll need to confirm if this is an issue or not on one of my testers: View attachment [Fly][H - Quest] 92-94 Gorgrond [Kick].xml
I tried your modified on and this is what I got. Guid:0x1C39788B804FC5000000070000673640 Can not turn in quest Tangleheart (ID: 35707) because I don't have it in my quest log! Bot stopping! Reason: Could not create current in quest bot! You're right, it's just standing in one place - it'll defend itself but I can't seem to get it going.
Do you have that quest in your quest log? If so, is it complete? You may have a cache corruption error.
Dont know if this bug is already submitted, but on the quest Gardul venomshiv in spires of arak, the bot goes Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting: Mounting:
Hmh, that's not an issue caused with the profile. It looks like the mount hook broke. Did it work after you stopped/started the bot?
nope, had to manually deliver the quest, this is a common problem everytime i lvl , not a big deal but if i go to sleep it will just stuck and loop there forever. it mountsup, dismounts, then mounts again etc etc. gotta look pretty awesome hehe
Oh and one more, the sun touched cache at Apexis Excavation zone in arak, the bot won't mount flying, just attemtping to jump to the Cache forever, this is also a point where i always find the bot disconnected SMW went around 99% perfectly Gorgrond went perfectly 100% Good job on that! Talrador Went around 97% Not bad that either! Arak has 1-5 lesser bugs that will hinder from 100% completion Nagrand i know usually stucks by the Saber den grottos thingy trying to get to certain points but overall arouuuund 95% auto Overall very happy with the profile! I would tho be VERY happy if you inserted an option to chose what Outpostes to build so we dont have to manually be there as it happends, i think it would contribute to less monitoring and making it overall easier to get through the zones
The whole addition of flying to WoD is pretty nice but often when the quest involves going into caves or building the pathing is completely off. The first Ogron you have to kill for the horde garrison chain to get level 1 my guy flew on top of the the cave and got stuck, the same thing happened to the next Ogron in that chain. I've notice a number of other issues. Is this something that could be fixed by deleting the meshes? Also, I notice a lot that my guy will keep flying around the mobs it wants to attack but not fly down and actually attack it. Fortunately I only bot when I am at my computer doing work so I notice it pretty quick but it's pretty obvious. This is while using singular so it could be with them but I don't know enough about the questing code to know if there is something to force attacks or not. Last quest, is there any way to just turn flying off if the optimization is where it's going to be?
I tried that, it still flew around. I haven't really tested it out much yet but I turned it on and monitoring.
It has been an issue with the navigation logic where "go into cave" has always had weird issues. For these quests, we usually force the bot to use its ground mount. Same with the second issue you reported. The questing botbase uses <Objective/> and <Objective/> has a lot of issues with not dismounting from flying mounts. It's mostly an internal error, but can be handled on a profile level. Usually our testers comb over the profiles and we weede these issues out. Its been a while since we've ran any Horde testers though - so I'll see about dispatching a few to get all that cleaned up. There's no way to actually turn off flying through the settings I don't believe. You can try this plugin Pookthetook made which tricks the bot into thinking it can't fly. View attachment Grounded.zip Thanks for the awareness!
Thanks for the prompt response EchoTiger, hopefully some of the kinks can be ironed out without much problem. As for turning on ground mount farming in bot config it doesn't seem to force ground mount only. If I feel like it's needed I'll do that addon to force ground mount since most of the time it runs well outside of some of the really obvious situations. As for the mount/dismount thing someone posted earlier, I ran into that at the scenario at the end of frostfire and when stopping the bot and mounting up you can't fly in that area at all.
Was a ground mount, and was during rev4352, uncommenting line 1111 seemed to fix it for me, wish I could tell you why, tried it on a whim and it worked
Hmh. The InteractWith was commented out because Honorbuddy's navigation logic should know how to handle the portal without the InteractWith. Leaving the InteractWith was posing as a problem since it would conflict with the navigation jumplink. I don't see why it would've just looped for you. I don't suppose you still have a log of it?
This is alliance not horde, Alliance is the big thing on US hehe. but it does happend on both factions, horde version is far more bugged than the alliance when it comes to overall WoD questing tho
The problematic quest begins at line 80762 Line 80963 is the first wait timer (i dont EXACTLY remember what happened but I think she went through the portal, and bot sat there about 20yd from the portal during wait timer, and then abandoned, but don't take my word for this) The First abandon is line 80996 Line 121754 is when I realized what was happening (ain't I observant?) and stopped the bot, CTRL+F "Dropping In" on the profile, found the commented line and uncommented it Line 121853 starting bot after doing that i THINK because im too lazy to corpse run Line 121946 started the bot with the modified profile Line 122266 picking up the quest Line 122729 is it turning in the quest Sorry if this wasn't any help =/ View attachment DROPPING IN.zip
The questing profiles shouldn't be trying to loot Sun-Touched Cache. Which profile was you using? Glad to see it's mostly working out for you - although to fix the errors (like the Saber Den Grotto one) - I'll need a log so I can see what's going on. It has been requested in the past to add an option to choose which outpost the bot picks. But implementing a way to allow the user to choose which has been the tricky part. There's no easy way of doing this. By default, the profile will choose one after 5minutes.
I'll be bringing up some more characters too on the newer revisions so I'll be able to let you know if it's still a problem if that log doesn't help at all