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!

Bellefeegore said:
hello !

I'd just like to know if there's any chance of having an update about Hallow's end profile, as it doesn't work (to pick candies in inns ^^ )

i got this message :



[Singular] Your Level 110 Blood Elf Havoc Demon Hunter Build is
[Singular] ... running the Questing bot in Les Pitons-du-Tonnerre
[Singular] ... Zone: Kalimdor using my SOLO Behaviors alone
[HallowsEnd_CandyBuckets-16340%(fatal)] QuestId(12396) is for faction group Alliance, your FactionGroup is Horde.
Bot stopping! Reason: Fatal error in quest behavior, or profile.


edit : when i try this on an alliance char, it says taht, then stops :

[HallowsEnd_CandyBuckets-16340%(info)] Pursuing Candy Bucket: "Hurlevent, quartier commerçant"
[HallowsEnd_CandyBuckets-16340%(warning)] Waiting for 20 seconds for CandyBucket(190048) to appear at "Hurlevent, quartier commerçant"
[HallowsEnd_CandyBuckets-16340%(fatal)] Unable to locate CandyBucket(190048) at "Hurlevent, quartier commerçant"
thank you !

(i have picked this one already one year ago)

thanks !
Click to expand...
Only the actual 1-110 questing profiles are being worked on at the moment, sorry.
The special event profiles aren't of priority at all.

You can try using the "version 1" of them to see if they do any better.
 
Lockwood said:
Blood DK Artifact Quest

Stage 7 - After freeing Minerva we should have a wait timer for 15s. The bot charges ahead mounted ahead of the 2 npcs and gets owned by 7 mobs.

Wait timer would allow NPCs to assist.
Click to expand...
I believe my testers have encountered this as well.
I'll look into getting a timer added in - thanks for the report!
 
tsukasadt said:
The ones through WotLK I confirmed between Druid and Warrior with no addons. The Cata ones are from my Druid. I'm planning on taking my Warrior through them next week. Trying to keep it to a casual leveling. ^^'
Click to expand...
Alrighty, thanks for the update - class can definitely affect how some of these bugs happened.
 
v0nsild said:
Could you implement the bot delivers all qs before leaving a zone, instead of just abandoning them all?

I stopped the bot and started it later, and I lost 7 completed quests that just needed turning in.
Click to expand...
This could be possible - but would be a lot of work.

TurnIn code for each quest would have to be added to the profile -
and to add code I'll need to know what quests your player currently as, which is impossible for me to know ahead of time.
 
wallyworld said:
View attachment 214712

I thought it was trying to run up to grab the grapple launcher for some reason, but that's not the case.
Click to expand...
The combat routine you're using is spamming so much useless data into the log, it makes it almost impossible to find anything actually useful.
It's an absolute mess. Not your fault of course :P

The only thing I see in this log is the bot was waiting 60seconds after attempting to leave Helheim - which then you stopped the bot.
I'll run some testers through again to see if they have any weird movement with this quest.
 
AbbyBaby said:
firstly this questing works great ^^
i'm not sure where to ask this but under plugins.. anti drown auto turns on even after i manually turn it off..
i'd like to keep it off.. can someone give me any tips?
ty
Click to expand...
The profiles turn them on.
You would have to remove the code from the profiles to prevent this.

PHP: 
<CustomBehavior File="EnablePlugin" Names="Anti Drown" />

If you search for that specific text in the profiles, you can see where it's turned on.
Just remove this.
 
Morx said:
Quest is definitely bugged. Bot says it's trying to turn it in, but it keeps pathing through the field of ettins and dying. The worst part is then I manually put my character right next to the guy turn in NPC, and he doesn't turn it in, but runs out of the cave, and straight to a particular etin, tries to kill it, but as I'm a Mage, and not Hunter/Warlock, I die, and this process repeats causing a death loop.

Logs attached.

Edit: Manually turn the quest in, and start the bot up again. Still says:

Goal: Turning in Quest - The Path of Huln (The Path of Huln - Quest - World of Warcraft) : To - Spiritwalker Ebonhorn : ID - 99153 [Ref: "Turnin" @line 703]

However, this has already been done, so now it's sounding like a Cache issue that I need to clear out.

Edit2: It kept saying that step of the quest because it wanted to get back to town to repair. After it did this, the step progressed to picking up the next quest like normal. The pathing logic in this area is terrible though as it runs through etins constantly, which are elites and not easy to kill.
Click to expand...
That doesn't seem like a bug - just an unlucky series of events.

Right now blackspots don't work in the bot, and the work-around Avoidance logic to make the bot avoid the Ettins was previously causing people to run off the mountain, so it was removed.
So in terms of keeping the bot from going near the Ettins - there's not a solution. Not at least until Blackspots are working.

I can turn off repairing and vendoring prior to this quest being executed - but that would most-likely cause even more issues.
The only thing I could think is to have the bot force-vendor prior to doing any of this quest. That way it doesn't stray off the intended questing path and run into Ettins.
 
wallyworld said:
Here's another log from a completely different character that exhibited the exact same issue as I've reported with log...This is now the 4th character that this has happened on:

View attachment 214772

Here is the hotspot that is being moved to that causes the issue:

<Hotspot X="3045.282" Y="3367.531" Z="546.4993" />

And removing that hotspot fixes the issue.

I'm not sure if this log shows it or it was my previous log, but if the Graymane quest fails to start the scenario on the boat on the start of Stormheim(not HB's fault, it's a known wow bug), the character flies out into the middle of the ocean and dies from fatigue. I've had this happen twice now. I caught it this time and flew back to the boat, abandoned the quest and re-started the scenario. I dunno if there's a way to check if the scenario starts, but it definitely shouldn't fly out into the ocean just to get rez sickness.
Click to expand...
Alright, I'll investigate this hotspot with my testers.

In terms of the WoW bug - I've seen this personally as well.
There's code to have it loop if it fails to enter the scenario, but it seems the detection is a bit bad - I'll look into improving it.

Thanks for the update!
 
Morx said:
Bot isn't interacting with ground targets and instead is just trying to kill mobs to complete objective. Objective would complete much faster if it would interact with Hexxing Fetish. The bot says in the "Info" tab that it will interact with them, but it does not.

Goal: InteractWith-Intera: In Progress (no associated quest)
Interacting with Hexxing Fetish, MobId(94153), Vilewing Hexer, Cursed Elderhorn, Cursed Prowler
[Ref: "[N-Quest] Highmountain [Echo] ($Rev: 5831 $)" @line 1446]

Unable to attach log. Going to try again after I post this to try and edit one in. Thank you.
Click to expand...
It could be because the InteractWith logic is confusing itself. This seems to be a new issue as of HB3.

Before - it properly identify a "enemy" and a "friendly" - and would engage or interact accordingly.
Now, it seems to only want to kill stuff, and since the Hexxing Fetish objects are "friendly" - it's not engaging(interacting with) them for this fact.

I'm working on a work around for this.
 
daemon9 said:
Using this profile I find my toon just stopped at a questgiver and HB has stopped. Here's a log:
Click to expand...
It's because you're using the "autoturnin" addon.

That addon will absolutely break questing as it turns in quests faster than the bot's logic can realize the quest is no longer in the player's quest log.
Which when this happens, the bot shuts down because it thinks the turn in code failed.

Disable this addon then try again.
I'd personally also recommend disabling all addons as they could also potentially conflict with the bot.
 
Bot is getting stuck on trying to accept quest 9792, A message to Telaar


This is 100% only bot usage, so I am not sure why it is getting stuck.
View attachment 8136 2016-10-21 06.04.txt

Edit: Figured it out, I did not have neutral or higher reputation with the Kurenai faction, not sure if profile can be updated to do the 3 quests he offers (which gives you neutral) or just remove the quest entirely.
 
Last edited:
EchoTiger said:
No.

There's only one file in there named [Fly] - and it's just a single profile that compiles all the profiles up.
All the other profiles in there are ground.

If you read "Getting Started" on that thread it clearly says:
It's recommended that you start with the 'Frostfire Ridge' profile, the profiles will then load by themselves after that.​
Click to expand...


Did you ever try them on a ground mount? Lots of treasure locations are not reachable, because there is no path to the node and you have to do jumps on your mount this profile isn't capable to do, so it's all just theoretical, but practically it does not work.
Example? See log, neverending story of missing the spot, waiting for 60 sec, retrying, failing, ...
 

Attachments

Last edited:
EchoTiger said:
That doesn't seem like a bug - just an unlucky series of events.

Right now blackspots don't work in the bot, and the work-around Avoidance logic to make the bot avoid the Ettins was previously causing people to run off the mountain, so it was removed.
So in terms of keeping the bot from going near the Ettins - there's not a solution. Not at least until Blackspots are working.

I can turn off repairing and vendoring prior to this quest being executed - but that would most-likely cause even more issues.
The only thing I could think is to have the bot force-vendor prior to doing any of this quest. That way it doesn't stray off the intended questing path and run into Ettins.
Click to expand...
I tend to agree with you that it was a bad set of events. The mesh navigation in the area seems a little off. At one point the bot ran all the way out of the bottom of the cave, towards the little town, but gets caught and dismounts to try and fight an ettin. Bad choice for anyone but a healer, tank, or warlock/hunter, hehe. So I pause and then manually get myself outta trouble. Then turn it back on, and where it goes next is directly on a spawn point of an Ettin. Not sure why it wanted to go specifically there. :(

But again, I got past it, and all is well. I have no doubt the whole thing was exasperated by the fact I was a squishy mage dying all the time. lol
 
Questing/mount adn etc

Is there a way to put the bot to automatically do all the quests, even after level 110? And take mounts and so on?

If it is possibile, how do i do that?

thx
 
You must log in or register to reply here.
Back
Top