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

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

The quest Nithogg's Tribute in Stormheim...

I've now ran the quest on several characters and every time, my character sits and humps a wall trying to get to the first eagle sitting on the ridge as you start to do the quest. The profile should either blacklist that mob if you're melee or move around the corner to pull it.
 
Hello :) Just a little question, is there a eta for the suramar Profile? Or maybe a progress in %?^^ Thx for this awesome work!
 
86-87 Valley of the Four Winds

Quest: Mothallus.

Doesn't click the Bait. Just stands there saying 'no viable mob in area'.

Quest: Weed War.

Fails to start killing weeds after gossipping. Just keeps trying to interact after you've taken quest and then blacklists the quest giver. Endless Loop.
 
Last edited:
The profiles for 90-100 do not require flying at all.
In fact, they were built purely with ground navigation logic.

The flight logic that was added after-the-fact is simply "layered" in and has no affect on the original ground navigation.
If you're having issues with movement, then this is due to HB3's new navigation system.

The profiles are slowly being adapted to fully support the new navigation tolerances of HB3.


Okay. I wonder if anyone else is having the same problem? Because I can't get any of the questing at level 90 started.
 
Fungal Monstrosities - Quest - World of Warcraft

Hotspots as requested:

<Hotspot X="1527.462" Y="1524.288" Z="178.3621" />
<Hotspot X="1444.134" Y="1592.393" Z="177.5591" />
<Hotspot X="1455.303" Y="1673.809" Z="172.3485" />
<Hotspot X="1518.57" Y="1692.583" Z="176.8697" />
<Hotspot X="1640.301" Y="1662.732" Z="175.7053" />
<Hotspot X="1683.646" Y="1664.097" Z="177.1491" />
<Hotspot X="1752.549" Y="1702.644" Z="176.6763" />
<Hotspot X="1723.799" Y="1762.623" Z="180.8929" />
<Hotspot X="1846.493" Y="1709.516" Z="182.3249" />
<Hotspot X="1839.98" Y="1625.453" Z="176.846" />
<Hotspot X="1778.28" Y="1537.556" Z="172.8718" />
<Hotspot X="1723.733" Y="1457.36" Z="172.353" />
<Hotspot X="1709.737" Y="1459.365" Z="173.985" />
<Hotspot X="1642.244" Y="1480.794" Z="178.1248" />
 
100-110 doesn't pick up gold, stands still alot what should i do to fix, or is this regular.
 
90-91 Horde

Intro Quests for WOD.

Doesn't actually kill a mob to pick up 'iron horde missive'. Just tries to use dead bodies and then auto attacks the living mobs. Needs to be looked at.

Once missive in inventory after manual intervention there quests run fine.
 
Profile: [Fly][H - Quest] 92-94 Gorgrond [Kick] (may also affect Alliance profile, but I cannot confirm)

The Pickup location for Heart of the Fen - Quest - World of Warcraft seems to be wrong, I noticed the bot was stopped for a long time waiting for the quest giver to appear.

Code:
<PickUp Nav="Fly" QuestName="Heart of the Fen" QuestId="35040" GiverName="Grulkor" GiverId="81241" X="6213.181" Y="389.1927" Z="4.079291"/>

After wandering around for a bit, I found him at the below location;

Code:
<Hotspot X="6184.795" Y="248.6012" Z="0.2534941" />
I would have to confirm that he moved myself.
It's not likely that Blizzard moves NPCs randomly like this - and the profile has worked up until now.

I've got this marked down and will check it out soon -
Thanks for the report!
 
I've had this bugged on 3 different characters. Same Gun - Same bug. Same fix each time (move gun and it fires away fine)

I'f I can get some time today after work I'll grab those Hotspots for the Deepholm quest for you.
Alright, thanks!
If you could get the coordinate of the 'working' cannon that'd be helpful as well.
If not, I'll look into getting a tester out there eventually.
 
Ashenvale 20-25

Keeping the Fires Burning.

Whatever Changes were made to kill the hydras- the bot now gets stuck in the water without any way of navigating out.

Log attached (at the end)
I don't see any evidence of the quest "Keep the Fires Burning (13890)" in this log.

However, at the end it seemed that you had connectivity issues to the Buddy servers.
Perhaps that was causing your navigation issues?
 
The quest Nithogg's Tribute in Stormheim...

I've now ran the quest on several characters and every time, my character sits and humps a wall trying to get to the first eagle sitting on the ridge as you start to do the quest. The profile should either blacklist that mob if you're melee or move around the corner to pull it.
That's a job for the combat routine you're using.
It shouldn't be trying to engage mobs that it can't.

But - I can hard-code something in that tells the combat routine "no."
I'll look into getting this in soon.
 
Hello :) Just a little question, is there a eta for the suramar Profile? Or maybe a progress in %?^^ Thx for this awesome work!
There's not, sorry.
Suramar is bottom priority right now as I'm still working on both Singular and Artifact Profiles.
 
86-87 Valley of the Four Winds

Quest: Mothallus.

Doesn't click the Bait. Just stands there saying 'no viable mob in area'.

Quest: Weed War.

Fails to start killing weeds after gossipping. Just keeps trying to interact after you've taken quest and then blacklists the quest giver. Endless Loop.
For Mothalius, I can't tell which mob it's looking for without a log.
I'm going to assume it's looking for the moth itself and the interaction with the bait failed but the bot didn't notice it.
I've adjusted the logic here to loop in case of the "Bait Interact" fail.

For the Weed War quest, I don't see anything on the profile code that would be causing it to fail.
However, I can add termination to the interaction logic if the weed mobs are detected around the player - this should prevent it from looping.

Thanks for the reports!
 
Okay. I wonder if anyone else is having the same problem? Because I can't get any of the questing at level 90 started.
I've not had any other reports regarding navigation issues in the 90-100 range, so I'm not sure.

Now that the Legion profiles are starting to 'calm down' - I'm going to start up some 1-100 testers again, so hopefully I can weed out any issues I run across.
 
Fungal Monstrosities - Quest - World of Warcraft

Hotspots as requested:

<Hotspot X="1527.462" Y="1524.288" Z="178.3621" />
<Hotspot X="1444.134" Y="1592.393" Z="177.5591" />
<Hotspot X="1455.303" Y="1673.809" Z="172.3485" />
<Hotspot X="1518.57" Y="1692.583" Z="176.8697" />
<Hotspot X="1640.301" Y="1662.732" Z="175.7053" />
<Hotspot X="1683.646" Y="1664.097" Z="177.1491" />
<Hotspot X="1752.549" Y="1702.644" Z="176.6763" />
<Hotspot X="1723.799" Y="1762.623" Z="180.8929" />
<Hotspot X="1846.493" Y="1709.516" Z="182.3249" />
<Hotspot X="1839.98" Y="1625.453" Z="176.846" />
<Hotspot X="1778.28" Y="1537.556" Z="172.8718" />
<Hotspot X="1723.733" Y="1457.36" Z="172.353" />
<Hotspot X="1709.737" Y="1459.365" Z="173.985" />
<Hotspot X="1642.244" Y="1480.794" Z="178.1248" />
Added!
The old objective logic has been removed and replaced with the new KUC logic.
Thanks!
 
100-110 doesn't pick up gold, stands still alot what should i do to fix, or is this regular.
Pick up gold? You mean loot mobs?
If so, - the profile doesn't handle looting mobs.

Make sure "Loot Mobs" is turned on in your settings and make sure you have auto-loot turned on in your WoW settings.

Also, it standing still - I'll need a log to see why it's doing this.
This isn't normal.
 
90-91 Horde

Intro Quests for WOD.

Doesn't actually kill a mob to pick up 'iron horde missive'. Just tries to use dead bodies and then auto attacks the living mobs. Needs to be looked at.

Once missive in inventory after manual intervention there quests run fine.
For some reason the Horde version has a completely different logic here than Alliance even though they're the exact quests.
The Horde version has a line that's telling it to interact with the dead orcs.

I've swapped the Horde code out, which should fix it.
 
Moonrest Gardens - Dragonblight.

Horde 68-80

Still isn't looting the corpses and opening bags for 'Moonrest Plans'

Rifle the Bodies - Quest - World of Warcraft

Once looted manually bot continues fine. Log attached. This has happened on 4 toons now.
Weird - somehow the fix I made here never made it into the SVN.
I've committed it just now.

Hopefully this will fix it - if it doesn't, please tell me as I currently don't have testers for this quest.
 
Back
Top