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

It's hard to pinpoint exactly what's causing the issues since it's over such a broad execution.

However, in situations like this - it's better to start out with a completely fresh install of the bot itself.
Also make sure any in-game addons are completely disabled as they could potentially interfere with the bot's behavior.

After all that's done, try running the bot again.
The first time it starts acting up - stop the bot immediately and get the log.

That log will have a better example of what may be causing you issues.

 

There's no checkpoint system in the Draenor profiles, so it shouldn't have skipped Shadowmoon Valley if all the quests there weren't complete.
You may want to try manually loading the Shadowmoon Valley profile instead of using any auto-loaders.

It looks like it's trying to pick up the quest Growing Wood from the NPC Glirin.

If that NPC isn't there, there's a chance that your Cache could be corrupted.
On the front page of this thread - there's the "Question and Answer" link, which on there it describes what the cache corruption is, and how to identify it.
eg: If a quest or NPC isn't visible, there's a chance it could be a cache corruption (or a breadcrumb quest was completed manually that the profiles doesn't support.)

This Wiki article here describes cache corruption in further detail, and how to 'uncorrupt' it:

Honorbuddy:HelpDesk:Cache corruption problems​

 

Do you perhaps have a log of this?
I believe when Kick originally wrote these profiles, there were spots where there was a lack of quests - which as an immediate solution Kick resorted to adding mob-grind logics to farm out some experience.

This only occurs in the 12-58 level range, and should be fairly rare.
From what I can remember, there's only two occurrences of this for the Alliance profiles.

It's on my to-do list (after Legion release) to go back and remove the grind areas and replace them with more quests.
That way this can be avoided.

 

I'm not sure which quest "The quest" is, or which quests you're referring to in which you're having issues with so I'll need a log or more information regarding this.

There hasn't really been any changes to the 58-70 range of profiles. Here's the commit list: Horde 58-70 Questing Commits
Any changes that have been made were general bug fixes which wouldn't be causing these issues you're listing.

The order in which quests are picked up and completed is never changed unless there's an absolute reason for them to be.
The existing order that they're in now is the order they've been since they were originally created.
So if the bot is skipping quests, or isn't doing the quests in the proper order - then you may have a cache corruption.

None of my testers have noted any issues in the 58-70 range either, however it has been a while since I've had a batch of Horde testers go completely through from 1 to 100.
I'll launch a batch of them to see what they discover
Assuming these issues are not just a issues on your end caused by cache corruptions (or whatever else) - then Blizzard would've had to of changed something in a patch.

 

I'll mark it down, should be an easy fix without requiring a log.
Thanks for the report!

 

There are no flying specific profiles here.
The profiles on the pack support both ground and flying - and are actually tested moreso with ground-based testers.

When flying support was added, it was done so in a manner that it doesn't effect the ground logic at all.
The flying logic just acts as an invisible layer of code for people who do have flying for Draenor.

I'll check out the stuckspot to see what's going on there.

 

Without a log or any other information - I can't really diagnose what's causing the bot to die on that mob.

All I can gather is what I had to Google, which Tower Warden seems to be an NPC in the southern barrens - so you must be Horde correct?
Why the bot would be going to that location while you being a level 13 isn't something anyone has reported before, so I have no information that could help you.

Do you have a log of it going to this location and dying?
If so, I can read it to see what invoked the bot to go to that location.

 

I'll need a log to see what's going on.
Things like this could be caused by a number of things - addons, low framerate, Blizzard changing mob Ids, etc.

If you're wanting to run questing 1 to 100, then I'd recommend using a relogger.
A relogger will relog you back into the game if the bot messes up or if you get disconnected.