[A-Quest]Townlong Steppes(88-89)

Now the bot how start to jump of the big wall and dies aswell before going to "Ben" hehe, but here you go.

 

Cava, I just used this profile and it worked very well. Exception of a few stucks, a restart fixed it, but most of it was flawless. Great work.


I have no problems to report.

 

Quest: Pick a Yak

Toon try to target a Yak and needs to use the Rope. But always i get the Information in WoW that the Target is tapped. I tryed Singular + Superbad as CC.

edit: ok looks like there was 1 Yak with the Problem, so its an ingame bug. Maybe its possible to get something like, if it doesnt work after 3 trys blacklist, or go on to the next one?

 

thanks for that , i need run again over that map, will check that part again

 

thats a great ideia, but its bot side, with profile cant force bot to (blacklist mobs/objects after X tries) or if i can i dont know, please report your idea to devs maybe they listen and improve bot

 

Cava your 85-90 profile was extremely good. Thank you for your hard time and work put into this. I haven't seen this quality of a questing profile since kickzz. Good job. I vouch for a sticky on this one.

 

doesnt work at all, all it does is go to the flightmaster then it stops there and does nothing

 

cant reproduce that, tested 3 times all 3 times bot finished quest

 

must be an CC issue, tested and killed nice and well

 

Fixed at next revision

Forced him to move without combat, hope that fix it
Fixed a next revision

Fixed all at revision 128

Thanks for reporting

 

same problem again, runs back to start

Hi,
same problem again on a new character.
Doesn't matter where i stand in townlong steppes. i just keeps wanting to go back to the start camp and talk to an NPC which is not there, (quest already done).

Im 88 and over half.

It has done all the quests so far until i stop bot and cointinue another day. then it wants to go back to the start area, sets Hearthstone there, sells shit, and stands next to the camp fire, where the starter-npc was.


closed wow, cleared cache, delivered the quests completed (none) and started the bot.
View attachment 6416 2012-11-05 23.57.txt

This happens to every character i try to level.

 

please clean cache one more time and upload the log u got after that,(i dont know why, but some times doesnt work at first time( the clean cache thing)

 

It seems there need to be some kind of wait timer when you are supposed to "lightly nudge Ruther". It takes so long that the bot interrupts and restarts.

 

Why wont it use Flying mount when I'm level 90?

 

I had the same problem as Elyo:

Bot was getting stuck on the rocks where you help the guy with the spear in his side and have to go up the hill to kill the mage.
Stopped bot and quested a bit myself (up to Gao-Ran)
Got lazy and wanted to bot it again.
Started it up, it went back to Longying, set hearth, repaired, and ran to campfire to where Taran Zhu should have been.
Cleaned cache and restarted 5 times.
Eventually got irritated and just deleted quest order up to where I was in the file. (Worked obviously, but doesn't help you at all to maybe diagnose my problem)

Attaching my log of before I went in though after the last clean/restart.

 

I thought I'd give it a try since I had a couple characters stuck at 88 and none of the Kun-Lai profiles worked correctly. Even with following the directions as specified and the cache cleaned (multiple times with re-downloads) the profile seems to just go backwards. Started it at the Fire Camp in Townlong Steppes and came back after I went to grab a drink to find myself wandering around in The Jade Forest.

This isn't really a bad thing because it IS still questing which is nice, all that means is Achievements. I can only assume it will eventually catch up to where it needs to be and move on from there. All in all; I'll re-post/edit later tonight to log its progress.

 

There is a syntax error in [A-Quest]TownlongSteppes(WL)(88-89)[Cava].xml line 906.

 

yes my bad today morning i was still sleeping when fixed script, and missed one ">"

will fix that after work

 

Fixed at revision 163

Thanks for reporting