[Azyul Project] Dungeon Farming, Gold Farming, Mount Farming, Transmog Farming, and more!

Set Honorbuddy to the "Questing" botbase, click "Load Profile" and then select which one you want to run.
Just like any other profile.

[HR][/HR]

All existing dungeons are planned on being re-built, and any non-existent ones will eventually be created.
It's just a matter of time - and I don't have any estimates. xD

Right now my main focus is the Optimized Gold Farm profiles.

 

The bot was traveling from Gundrak to The Nexus and Wintergrasp happens to be between those two instances.
If Wintergrasp is active, you'll instantly get dismounted (without a parachute) and you'll fall to your death.
A "great" system Blizzard has in place for a dead battleground that shouldn't exist anymore.

I've had to pay thousands of gold in repair bills thanks to this.

Anyway -
Naturally, the bot would be able to get back to your corpse, but usually when you die near Wintergrasp, your corpse ends up in the mountains - which makes it impossible to get to. So at this point, the bot just gives up, or attempts doing something else.

[HR][/HR]

Hmm, I noticed a mistype in an entry and sent out a fix for it. Try the latest SVN update.

 

I sent an update a while ago - could you try it?
SVN only.

 

Yep, but there was literately an update made to the profile a few minutes before you posted that should address the issue. xD

Just right click the folder you SVN'd and click "SVN Update"

 

This has already been reported mutliple times, and as stated previously - is not an error with the profile.
The latest 746 version of the bot messed up the mailing routine - and there's nothing I can do about it.

The core developers are aware of the issue, and are working on it.

[HR][/HR]

As posted on the Solution Center - the Questing botbase doesn't have death support while inside of a dungeon.
The bot will but out if it dies at any point in a dungeon.
If the bot is running out to the middle of the sea, then there's a good chance that it's dying in the dungeon.

Some dungeons have experimental death support, but it's considered in the alpha stage.

[HR][/HR]

Given the game client and Honorbuddy's constant inconsistency - it would actually still be a better idea to add a force-pull code on the boss.

If you look - at any time there's a major boss pull in my profiles, I've set it to that the bot runs directly through the boss and a few meters behind it instead of running directly on top of it. This way a pull is almost always guaranteed.

But like I said - sometimes it won't.
If you have slightly latency during the pull, the game client won't register aggro.

On the list of 'to-do' is to add a force pull for every boss in every profile.
Right now the only bosses that have it are bosses that patrol (like Commander Sarannis.)

[HR][/HR]

The bot should be detecting if you have the vendor mount or not.
If it's continuing without using it, then it's the bot's fault.
What settings are you using on the AM menu?

[HR][/HR]

It looks like your bot entered the dungeon - then for whatever reason left it.
After leaving it, it continued the dungeon code - which made it go across the game map.

Why it left - I don't know.
How long does it typically take for your game to load an instance?

 

I'll need to run a tester on it - although my testers have never ran across a problem.
It'll need to be investigated.

 

I just never got around to making it