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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[A-Quest]The Jade Forest(85-86)

And I think that you have the wrong coords for the quest giver "Outcast Sprite"
The correct position of the mob/questgiver is:
<Vendor Name="Outcast Sprite" Entry="55438" Type="Questgiver" X="2491.445" Y="-1946.844" Z="217.6123" />
but the profile tells my char to go to:
"<X=2532,707, Y=-1972,565, >= 217,012>"

It seems to have some trouble with "Back to nature" also.
[/COLOR]

sorry cant find the problem

bot does:
<TurnIn QuestName="Ritual Artifacts"
<TurnIn QuestName="Vessels of the Spirit"
<TurnIn QuestName="The Wayward Dead"
<PickUp QuestName="Back to Nature"
<PickUp QuestName="A Humble Offering"

all to same mob, if when u are using profile bot didnt picked up Back to Nature, probably u got some minor bug
 
The bot gets stuck on picking up the quest "Critical Condition". It picks it up fine but it keeps talking to Mishka to pick it up again, over and over in an infinite loop.

Edit: Actually gets stuck doing the same thing with the majority of the quest givers. If you do the quests you get stuck on manually you're able to get past the quest giver, but only to get stuck on the next one. Then again, whats the point of a bot if you're doing all the quests manually anyway haha. Joking aside, this is a great profile aside from getting stuck on accepting quests, if that can be fixed this profile would be flawless.
 
Last edited:
I noticed that it will sometimes try and accept a quest from a questgiver that would only become available after the quest you have already completed, for example, is turned in to the NPC beside the NPC from which it is trying to accept the quest.
 
Not a bad profile. Will give ya any problems I encounter later. Again much thanks for the time you put into this profile.
 
i got a whole 1 quest completed before it freaked out:

[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469


Mesh problem?
 
The bot gets stuck on picking up the quest "Critical Condition". It picks it up fine but it keeps talking to Mishka to pick it up again, over and over in an infinite loop.

Edit: Actually gets stuck doing the same thing with the majority of the quest givers. If you do the quests you get stuck on manually you're able to get past the quest giver, but only to get stuck on the next one. Then again, whats the point of a bot if you're doing all the quests manually anyway haha. Joking aside, this is a great profile aside from getting stuck on accepting quests, if that can be fixed this profile would be flawless.
reading your post and im thinking its more a bot bug than profile problem, did u try shut down both wow and bot and restart again? or even an bot fresh install?
 
I noticed that it will sometimes try and accept a quest from a questgiver that would only become available after the quest you have already completed, for example, is turned in to the NPC beside the NPC from which it is trying to accept the quest.

yes you are right there are a big issue with that , i didnt so far reported that bug cause i already reported a few bugs and no1 is fixed, probably dev have urgent things to do before they start fixing reported bugs.
let me try explain that bug , for example this run (bot need pick-up 2 quests and turn-in that 2 quests:

accept quest n? 1
accept quest n? 2
turn-in quest n?1
turn-in quest n?2

if u hit start and dont interrupt bot will do that without errors but if u do this:
accept quest n? 1
accept quest n? 2
stop bot here
turn-in quest n?1
turn-in quest n?2

you stoped bot after he put code turn-in quest n? 1, at this moment bot have in memory hes turning in quest number 1, if u start bot again bot will only turn-in quest number 2 ( for bot he already finished the (turn-in quest n?1 part), and you are now with problems, you need manualy turn in

hope , u understand whant i mean with my poor english :)

bot bug
 
i got a whole 1 quest completed before it freaked out:

[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469
[InteractWith-v249(debug) @line 787]: Sky Admiral Rogers
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
[CanCast] Battle Shout 6673
[CanCast] Commanding Shout 469


Mesh problem?
Could not generate path from {-7880.691, 1275.26, 358.4821} to {-7879.8, 1279.516, 358.4774} (time used: 0 milliseconds) @ FindStartPoly
yes its a mesh problem

but at this moment must be fixed, which profile revision do u have?
fixed that at revision 40 (i hope)
 
Where in SW do I start it?
when you char enter SW he will auto accept the first quest and bot will start
if for some reson bot didnt started, just leave SW delete kings quest and anter SW again
 
need to increase the pull distance on: "To bridge earth and sky" aswell.
if it is set to 1, the bot doesn ot seem to attack the mobs.
[/COLOR]

Fixed at revision 42

Thanks for reporting
 
I don't know if it's the new fail release of the bot or if it's these crap profiles but nothing works, It says it starts in SW which is doesn't it won't even pick up a single quest, just stands there like a moron.

Edit: Got profile working, bot kept resetting what kind of bot I wanted to use.
 
Last edited:
Quest: Pei-Back
The bot is supposed to righclick the characters body, asap when it gets ripped out of the body.
[/COLOR]

that thing can only be done with quest behavior we need wait till one dev make one for that quest, till that day there is only this solution,nuke, nuke and nuke harder :)
 
Quest Name: The Great Banquet, Speak with Elder Cloudfall. The bot runs to Elder Cloudfall, then moves to Xiao and tries to interact without doing the dialog or completing elder cloudfall bit. This happened on both my Characters. I manually completed on the first run through. The 2nd run through I tried abandoning the quest. This time through the bot interacted correctly for the first part of the Elder Cloudfall bit however did not complete the quest before running to Xiao.

Full log in the Zip file, stopped the bot while it was happening so it will be right at the bottom.

fixed at revision 43

Thanks for reporting
 
Have a problem. it keeps talking to the same guy to accept te quest. Even when He just accepted it.. Is it a glitch in HB?
 
Have a problem. it keeps talking to the same guy to accept te quest. Even when He just accepted it.. Is it a glitch in HB?

nothing i can if you dont explain a little more, wich quest? can u help showing the log?
 
Just ran my Demo Warlock through and this worked great. Thanks for all the work that went into it.

The only problem I had was with the quest, The Seal is Broken. The dialog popped up telling me I had to help the bot, I hit ok, and he proceeded to run and jump off the cliff killing me.

Keep up the great work Cav :)
 
Hi Cava,

when do you have the next part on the way to 90 for testing? The Jade Forest profile ist working great no bugs no problems. Now i am 86 an can?t go on :-(
 
Just ran my Demo Warlock through and this worked great. Thanks for all the work that went into it.

The only problem I had was with the quest, The Seal is Broken. The dialog popped up telling me I had to help the bot, I hit ok, and he proceeded to run and jump off the cliff killing me.

Keep up the great work Cav :)
Will check that asap
Thanks for reporting
 
Hi Cava,

when do you have the next part on the way to 90 for testing? The Jade Forest profile ist working great no bugs no problems. Now i am 86 an can?t go on :-(
ready post before :)
still have bugs, right now have 2 more bugs to fix then will start 86-> 87 part (today i hope) so later night will release the first part to you all start using and report bugs

i always try do this profiles bugfree but im human and always fail with strange things and places
 
Back
Top