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

According to your log, it's questing just fine.
It loaded into the Stormheim profile, then started moving to complete quest A Murky Fate

PHP:

[20:26:21.145 D] Goal: InteractWith-Intera: "Ein unwürdiges Schicksal" (http://wowhead.com/quest=40120)
Interacting by using Qualmende Fackel on MobId(98577)
    [Ref: "[N-Quest] Stormheim [Echo] ($Rev: 5754 $)" @line 1690]
[20:26:21.780 V] Planned a path from <3713.338, 3923.062, 911.0286> to <2882.382, 416.4601, 15.81335> (3713.2 yards)
  1: Move to Stonehoof Watch, Highmountain   (<3891.95, 3500.18, 800.7321>)
  2: Fly to Valdisdall, Stormheim            (<3205.59, 1515.58, 181.1967>)
  3: Move to end                             (<2882.382, 416.4601, 15.81335>)

 

Added.
Thanks for helping!

 

You're posting this on the wrong thread.
This isn't the "Evergreen farm" thread.

 

As you noted, this quest pickup is outside of Stormwind - but you're starting the bot in Broken Isles, Dalaran.
If you move your character to the Eastern Kingdoms continent, it will work.

However,
The rogue artifact quests are still being worked on.
Due to the stealth mechanics, they are very complex and have a very high chance of breaking since the bot isn't designed perfectly to handle stealing around mobs in tight spaces.

At the moment, I can only recommend doing these quests manually.

 

This is noted to be fixed.
I'll possibly get around to it today if I can get a tester to that quest.

 

It seems that at one point, you moved the character manually.

The quest the bot wants to do is up in a mountain that can't be navigated by the bot.
Naturally - the profile makes the bot interact with an NPC to get up this mountain.

If you move the character off the mountain and start the bot, it will result in the error you're getting.

I'll look into adding logic that'll make the bot go back up the mountain if this occurs.
But in the mean time you'll need to go this NPC: Vethir and talk to him to request a flight back up the mountain.

 

I've replaced this quest with better logic in the latest update that should hopefully fix that issue.
Thanks for the report!

 

I can't tell what's going on without a log unfortunately.
The only thing I can suggest is for you to use "Auto-Loader v2" as it is typically good at handling navigation to the correct locations.

 

The Restoration Shaman profile hasn't been tested yet.
Mainly due to Honorbuddy no longer supporting navigation in the Vashj'ir swimming zone.

I can fix the issues in the healing scenario, but the quests up until the healing scenario will be very tricky unless I CTM it all.

 

Should be fixed on all sources.
I went to sleep before being able to test the changes.

 

I've not been able to replicate the Unbearable quest issue you reported on my testers, but I will indeed look into figuring out what's going on there.

For the Pop Quiz quest, the results seem to be different for everybody.
FPS, Latency, TPS, etc - all have a factor in how this quest will be performed.

Personally, I've never had an issue with it on my testers - they usually complete the quest at the same pace as a human.

However,
I'm currently looking into a better solution for handling this quest instead of using a chunk of CTMs.
Hopefully I'll be able to find a way to detect the trigger objects which determine if the user has drawn the lines or not.

 

Do a fresh install of your bot.
This isn't a profile issue - it's an issue with the bot.

 

This issue has already been fixed.
Thanks for the awareness though!

 

Don't double post issues.
I have to manually investigate the issue twice which is a major time waste.

I've replied to your first report here:
https://www.thebuddyforum.com/honor...pack-lvl-1-110-a-post2316185.html#post2316185

 

I'll have to investigate the Fungal Monstrosities issue - it's no doubt due to the use of bad logic here.
I'd make the fix now, but I don't have the hotspots the bot should be farming in.

For the staff quest, yes - currently there's three hotspots here for whatever reason.
I've removed it to just one hotspot, hopefully that will be enough for the bot to detect him in.

 

Thanks for the report, but I can't just magically know what's causing this issue.
Please post a log so I can investigate what's happening.

Alternatively - don't load any profiles after the bot has started questing.
If you're stopping the bot while it's questing and reloading back to any of the auto-loaders, it will load back to your class hall stuff.

Load the questing profile for which zone your bot is currently in, and start the bot.

 

There is currently an issue where in some rare cases, InteractWith won't click the gossip options properly.

In the profile code, it looks like the logic should be endlessly looping for as long as the current stage number is 4.
So if you let it run, it should've looped back and interacted with him again.

 

Some issues don't occur for some people.
I'll personally run a tester through a profile and it be flawless - but someone else do it and they run across a bug every 5minutes.

For this specific issue, have you noticed it bugged on multiple characters?
Or was it bugged for just the one character.