What's new
By:
  • 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!

HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Hi, how can i use the profile to do LK quests on my lvl 100 ? I leveled doing BGs but now i want Northrend quests done.

When I start the profile, it just do sholazar basin quests and then stops.
 
gbasp05 said:
Hi, how can i use the profile to do LK quests on my lvl 100 ? I leveled doing BGs but now i want Northrend quests done.

When I start the profile, it just do sholazar basin quests and then stops.
Click to expand...
When you load the profile, click "Settings & Tools" on Honorbuddy.

At the bottom left of the menu that appears, you should see "Override profile settings."
Check this.

Once you check that, the other checkboxes should become availible.
Scroll to the bottom and look for "Ignore Checkpoints."
Check that.

Save -> Close out the "Settings & Tools"
The bot should now do every quest in the profile when you start it.
 
Hi, during the quest "Sealing the way" in Deepholm the NPC gets attacked by hostile npc's and therefor the bot is unable to use the Rockslide Reagent since one of the criteria are "Hand the Rockslide Reagent to an Earthen Geomancer who is not in combat. ". I found the bot, next to two other very likely boters on their flying mounts just hovering over a Geomancer

As the following example:
botter.jpg


Looking forward for an update. Other than that great profile thanks alot!!!
 
EchoTiger said:
Hm, this log shows that the bot was started in Gorgrond where it quested a bit.
The bot leveled up, then went to go turn in News from Talador.

From there, it went back to Shadowmoon Valley as there are level 94 quests that lead up to questing in Talador.
It got stuck, which then you stopped the bot.

Aside from the stuck, everything seems normal.
Perhaps you thought it was doing low level quests in Shadowmoon Valley?

Theres a few level 94 quests in Shadowmoon Valley that needs to be done there before entering Talador.
Most of them being in this quest chain: http://www.wowhead.com/quest=33359
Click to expand...

That's not the whole ordeal. I believe the simple issue to make the 90-100 levelling profiles with flying is to simply make the bot dismount. As it just flies from NPC to NPC (above them) and proceeds until finally a loop is locked. But the bot never dismounts. Happened numerous times during the past days, with me overseeing the process.
 
ibreezer said:
Hi, during the quest "Sealing the way" in Deepholm the NPC gets attacked by hostile npc's and therefor the bot is unable to use the Rockslide Reagent since one of the criteria are "Hand the Rockslide Reagent to an Earthen Geomancer who is not in combat. ". I found the bot, next to two other very likely boters on their flying mounts just hovering over a Geomancer

As the following example:
botter.jpg


Looking forward for an update. Other than that great profile thanks alot!!!
Click to expand...
I'd normally ask for a log, but this seems pretty straight forward.

I'll make note of it and get it addressed as soon as possible.
Thanks for the picture.
 
Last edited:
Floxydoxymetachlorine said:
That's not the whole ordeal. I believe the simple issue to make the 90-100 levelling profiles with flying is to simply make the bot dismount. As it just flies from NPC to NPC (above them) and proceeds until finally a loop is locked. But the bot never dismounts. Happened numerous times during the past days, with me overseeing the process.
Click to expand...
Yes, efforts have been made by Kick to ensure at any point that it's needed - the bot dismounts.

There should be very few, if any areas in which the bot isn't dismounting as they may have been overlooked and not noted by our testers.
In order to fully address the issue, I'll need to know which quest, or objective the bot is not dismounting on so that I have a reference point to start at in your log.

I'll typically look at the end of the log since most of the time that's where the issues are occurring since the player stops the bot at that point.
However with your log, what I had seen was what I had noted in my original reply. Unfortunately nothing along the lines of the bot not dismounting stood out.

Anywho, as I said if you could please note any Quests names or Objective in which the bot has these dismount errors at so that I can check it out in the profile code - that would be awesome.
Thanks!
 
Last edited:
I can't find an option to use flight on my Horde characters in the WoD section of the guide.

Is it not developed yet, or did I mess something up?
 
Threadsoffate said:
I can't find an option to use flight on my Horde characters in the WoD section of the guide.

Is it not developed yet, or did I mess something up?
Click to expand...
Yea, Kick is still working on it.
I believe he had a lack of Horde characters at 90, so he couldn't properly develop it as soon as he could with the Alliance profiles.
 
Thank you for the quick fixing. Next problem is [H] Frostfire Ridge questing. Character goes to 2-nd floor of the Bladespire fortress and stops there awaiting for some quest npc :
Moving to Type: QuestPickUp

Here is the log:
 

Attachments

Hi there,

my Bot has some Heirlooms from 1-60 not upgraded. Now he wont change them for better gear in end BC or Wotlk. What could be wrong?

Auto Equip is enabled.
 
No, its broke for me too. I just started doing some manually with enyo to wait out a fix. Something broke, but not sure what lol.
 
This thing is still refusing to dismount from the flying mount, even with those updated profiles. I won't supply a log as it is full with

Moving to Type: Hotspot, Loc: <2926.325, 5010.67, 127.3834>
Moving to Type: Hotspot, Loc: <2926.325, 5010.67, 127.3834>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>

And goes on to eternity without doing anything. Is there anything on my end or is this a general issue?

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.424, 6024.365, 49.17593>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.171, 6024.642, 49.45882>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.902, 6024.465, 49.54044>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.421, 6024.615, 49.01724>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.497, 6024.597, 49.04932>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.927, 6024.983, 50.00352>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.76, 6024.87, 48.91304>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.199, 6024.322, 49.00395>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.206, 6024.282, 49.01587>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.582, 6024.888, 49.29138>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.352, 6024.893, 49.55091>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.854, 6024.959, 48.87989>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.784, 6025.028, 48.87572>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.2, 6024.397, 50.0909>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.356, 6024.521, 48.94878>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.135, 6024.678, 48.89618>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>

Oh, I'm sorry. Is this insufficient? Here's some more.

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2726.605, 5704.759, 85.71466>
Moving to Type: Hotspot, Loc: <2811.271, 5754.532, 90.98794>
Moving to Type: Hotspot, Loc: <2783.55, 5692.445, 85.65032>
Moving to Type: Hotspot, Loc: <2761.681, 5618.69, 86.04646>
Moving to Type: Hotspot, Loc: <2716.613, 5625.422, 88.26562>
Moving to Type: Hotspot, Loc: <2702.979, 5550.479, 88.41249>
Moving to Type: Hotspot, Loc: <2721.371, 5472.794, 99.17016>
Moving to Type: Hotspot, Loc: <2755.879, 5394.927, 117.3385>
Moving to Type: Hotspot, Loc: <2785.449, 5360.32, 118.8884>
Moving to Type: Hotspot, Loc: <2849.596, 5357.24, 118.5712>
Moving to Type: Hotspot, Loc: <2846.38, 5302.166, 123.8683>
Moving to Type: Hotspot, Loc: <2900.007, 5242.285, 116.2983>
Moving to Type: Hotspot, Loc: <2954.56, 5183.399, 111.0894>
Moving to Type: Hotspot, Loc: <2954.56, 5183.399, 111.0894>
Moving to Type: Hotspot, Loc: <3014.012, 5172.357, 101.1443>
Moving to Type: Hotspot, Loc: <3098.241, 5156.848, 92.0237>
Moving to Type: Hotspot, Loc: <3172.032, 5205.877, 93.50629>
Moving to Type: Hotspot, Loc: <3169.912, 5258.139, 89.92815>
Moving to Type: Hotspot, Loc: <3129.201, 5309.274, 98.47749>
Moving to Type: Hotspot, Loc: <3072.982, 5380.131, 109.4613>
Moving to Type: Hotspot, Loc: <3056.907, 5425.474, 103.4558>
Moving to Type: Hotspot, Loc: <3130.74, 5413.056, 95.5283>
Moving to Type: Hotspot, Loc: <3184.658, 5397.152, 86.64282>
Moving to Type: Hotspot, Loc: <3257.004, 5424.119, 72.75983>
Moving to Type: Hotspot, Loc: <3259.656, 5471.813, 63.45286>
Moving to Type: Hotspot, Loc: <3249.029, 5518.512, 65.22405>
Moving to Type: Hotspot, Loc: <3260.874, 5569.234, 62.07134>
Moving to Type: Hotspot, Loc: <3257.699, 5609.503, 55.03576>
Moving to Type: Hotspot, Loc: <3257.699, 5609.503, 55.03576>
Moving to Type: Hotspot, Loc: <3245.988, 5696.226, 49.96549>
Moving to Type: Hotspot, Loc: <3240.659, 5731.763, 51.53965>
Moving to Type: Hotspot, Loc: <3214.625, 5774.634, 58.72001>
Moving to Type: Hotspot, Loc: <3123.666, 5820.219, 83.79382>
Moving to Type: Hotspot, Loc: <3041.414, 5836.446, 86.92217>
 
Last edited:
Floxydoxymetachlorine said:
This thing is still refusing to dismount from the flying mount, even with those updated profiles. I won't supply a log as it is full with

Moving to Type: Hotspot, Loc: <2926.325, 5010.67, 127.3834>
Moving to Type: Hotspot, Loc: <2926.325, 5010.67, 127.3834>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>

And goes on to eternity without doing anything. Is there anything on my end or is this a general issue?

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.424, 6024.365, 49.17593>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.171, 6024.642, 49.45882>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.902, 6024.465, 49.54044>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.421, 6024.615, 49.01724>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.497, 6024.597, 49.04932>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.927, 6024.983, 50.00352>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.76, 6024.87, 48.91304>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.199, 6024.322, 49.00395>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.206, 6024.282, 49.01587>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.582, 6024.888, 49.29138>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.352, 6024.893, 49.55091>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.854, 6024.959, 48.87989>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2301.784, 6025.028, 48.87572>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.2, 6024.397, 50.0909>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.356, 6024.521, 48.94878>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
We are stuck! (<2302.135, 6024.678, 48.89618>)
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>

Oh, I'm sorry. Is this insufficient? Here's some more.

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2726.605, 5704.759, 85.71466>
Moving to Type: Hotspot, Loc: <2811.271, 5754.532, 90.98794>
Moving to Type: Hotspot, Loc: <2783.55, 5692.445, 85.65032>
Moving to Type: Hotspot, Loc: <2761.681, 5618.69, 86.04646>
Moving to Type: Hotspot, Loc: <2716.613, 5625.422, 88.26562>
Moving to Type: Hotspot, Loc: <2702.979, 5550.479, 88.41249>
Moving to Type: Hotspot, Loc: <2721.371, 5472.794, 99.17016>
Moving to Type: Hotspot, Loc: <2755.879, 5394.927, 117.3385>
Moving to Type: Hotspot, Loc: <2785.449, 5360.32, 118.8884>
Moving to Type: Hotspot, Loc: <2849.596, 5357.24, 118.5712>
Moving to Type: Hotspot, Loc: <2846.38, 5302.166, 123.8683>
Moving to Type: Hotspot, Loc: <2900.007, 5242.285, 116.2983>
Moving to Type: Hotspot, Loc: <2954.56, 5183.399, 111.0894>
Moving to Type: Hotspot, Loc: <2954.56, 5183.399, 111.0894>
Moving to Type: Hotspot, Loc: <3014.012, 5172.357, 101.1443>
Moving to Type: Hotspot, Loc: <3098.241, 5156.848, 92.0237>
Moving to Type: Hotspot, Loc: <3172.032, 5205.877, 93.50629>
Moving to Type: Hotspot, Loc: <3169.912, 5258.139, 89.92815>
Moving to Type: Hotspot, Loc: <3129.201, 5309.274, 98.47749>
Moving to Type: Hotspot, Loc: <3072.982, 5380.131, 109.4613>
Moving to Type: Hotspot, Loc: <3056.907, 5425.474, 103.4558>
Moving to Type: Hotspot, Loc: <3130.74, 5413.056, 95.5283>
Moving to Type: Hotspot, Loc: <3184.658, 5397.152, 86.64282>
Moving to Type: Hotspot, Loc: <3257.004, 5424.119, 72.75983>
Moving to Type: Hotspot, Loc: <3259.656, 5471.813, 63.45286>
Moving to Type: Hotspot, Loc: <3249.029, 5518.512, 65.22405>
Moving to Type: Hotspot, Loc: <3260.874, 5569.234, 62.07134>
Moving to Type: Hotspot, Loc: <3257.699, 5609.503, 55.03576>
Moving to Type: Hotspot, Loc: <3257.699, 5609.503, 55.03576>
Moving to Type: Hotspot, Loc: <3245.988, 5696.226, 49.96549>
Moving to Type: Hotspot, Loc: <3240.659, 5731.763, 51.53965>
Moving to Type: Hotspot, Loc: <3214.625, 5774.634, 58.72001>
Moving to Type: Hotspot, Loc: <3123.666, 5820.219, 83.79382>
Moving to Type: Hotspot, Loc: <3041.414, 5836.446, 86.92217>
Click to expand...

Mine does the exact same thing, but not on all quests. Only on some... but enough that the profiles are essentially worthless :/
 
I have noticed a problem with this pack in Durotar which makes it stuck for hours. This quest http://www.wowhead.com/quest=25194/unbidden-visitors which requires you to spank some Striders until they flee from Durotar to Barrens is impossible to do if you have your heirlooms on as the bot will one shot the mobs. I left the bot on for 3 hours to level a new rogue and majority of the time it was stuck at level 12, killing those striders. This would be better if the bot would take the weapons off and just hit the striders with bare fists.

Edit 1: And I have also noticed that the bot has problems with mounting. I don't have logs but when I use auto loader to level my mage it doesn't mount at all even though it has the heirloom mount and riding skill learned. Also Desolace seems to be broken as the bot picks most quests but ends only half of them. Would list the quests but when I noticed this the bot had already abandoned the completed quests and it was changing zone.
 
Last edited:
is there any plans in the Draenor profiles, to allow us to select the buildings the bot chooses up front, or have ones fixed to be selected, so we don't need to be there to select the options?
 
Last edited:
wh1t3r said:
Thank you for the quick fixing. Next problem is [H] Frostfire Ridge questing. Character goes to 2-nd floor of the Bladespire fortress and stops there awaiting for some quest npc :
Moving to Type: QuestPickUp

Here is the log:
Click to expand...
I don't see that the bot had issues from attempting to pickp a quest.
Instead, it seems that your character got stuck on something. Is this the correct log?

If so, could you move away from the objects which is causing the character to be stuck then re-start the bot?
 
bseen said:
Hi there,

my Bot has some Heirlooms from 1-60 not upgraded. Now he wont change them for better gear in end BC or Wotlk. What could be wrong?

Auto Equip is enabled.
Click to expand...
Its been a while, but I do recall the bot replacing heirlooms for my level 90-100 testers who hadn't had the level 100 heirloom upgrades.
So the bot should do it naturally.

I also remember there being a specific setting that said "Replace Heirlooms?" but I can't find it anymore.
It must have been a configuration setting for Auto Equip back when it was a plugin.

May I ask what combat routine are you using?
 
medecine said:
WOD Profile dont work ATM. I'm not the only one to have this problem.

https://www.thebuddyforum.com/honor...port/228801-kicks-1-100-norm.html#post2072238
https://www.thebuddyforum.com/honor...g-leveling-profiles-90-100-a.html#post2072245

Need help
Click to expand...
frostfire said:
No, its broke for me too. I just started doing some manually with enyo to wait out a fix. Something broke, but not sure what lol.
Click to expand...
Floxydoxymetachlorine said:
This thing is still refusing to dismount from the flying mount, even with those updated profiles. I won't supply a log as it is full with

Moving to Type: Hotspot, Loc: <2926.325, 5010.67, 127.3834>
--snip--
Moving to Type: Hotspot, Loc: <3160.308, 4798.587, 124.7593>

And goes on to eternity without doing anything. Is there anything on my end or is this a general issue?

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>
--snip--
Moving to Type: Hotspot, Loc: <2302.134, 6024.682, 48.89665>

Oh, I'm sorry. Is this insufficient? Here's some more.

Mounting: Snowy Gryphon
Moving to Type: Hotspot, Loc: <2726.605, 5704.759, 85.71466>
--snip--
Moving to Type: Hotspot, Loc: <3041.414, 5836.446, 86.92217>
Click to expand...
frostfire said:
Mine does the exact same thing, but not on all quests. Only on some... but enough that the profiles are essentially worthless :/
Click to expand...
I've looked further into the error given all the information you guys have been reporting and I've been able to figure up some persistences.
However it seems this could actually be an error within the bot itself, not the profiles - I've yet to fully confirm this though.

The quests that the Hotspots are breaking on (or the bot sitting over NPCs) are using the <Objective/> based-tag instead of using actual quest behaviors.
The <Objective/> logic should be making the player dismount when needed as there's no attribute to tell it to within the profile, however as you guys have pointed out - it's not.

I'll discuss this a bit with the other guys to see if we can figure up what's going on and hopefully get a fix for it as soon as possible.
Thanks for all the information everybody!
 
You must log in or register to reply here.
Back
Top