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

If you add this:
<CustomBehavior File="RunMacro" Macro="/cast Hearthstone" />

The bot will Hearth at whatever part of the code you put it in.

 

By default, the bot should not sell cloths, and will sell them.
Usually it takes a plugin to make it do that.

What plugins are you using? And what profile are you running?

 

That entirely depends on which profile you're running.
There's over 120+ profiles on the pack, and everyone of them are different. Only some of them do heroic->normal runs.

Since I don't know which profile "the profile" is, all I can tell you is this:

• None of the standard Instance Grinding Profiles are coded to do heroic->normal runs.
• Some of the Transmog Profiles are coded to do heroic->normal runs to get gear from the different difficulties.
• [DD] profiles will only do heroic->normal runs if you choose the Heroic run-type. This transitional code hasn't been tested extensively yet.
• None of the Farm Profiles currently do heroic->normal runs since they have no reason to change difficulty.

With that said, I'm assuming you're using one of the two [DD] profiles, either Grim Batol or Lightning Halls?
I can't give you a proper solution/response unless you tell me which profile is giving you the assumed issue. ;P

 

If the bot disconnects and Honorbuddy doesn't shut down/stop, the bot will continue where it left off when you log back in.
If the bot crashes/stops, then it won't.

The only way I could possibly make a fix for this is: Have the bot use the Hearthstone if it's inside the instance when the profile is first started.
That way if the bot crashes and ARelog starts it again, it will detect that the player is in the dungeon - then Hearthstone out - then continue regular code.

[hr][/hr]

Unfortunately every profile on the pack suffers from the same issue when it comes to dying in the instance.
The bot naturally does not know how to handle death while in an instance. And us trying to make a solution for it is extremely tricky.

When the bot loads a profile, it's pretty much like a train on a track. Each code wrap is a new track.
The bot reads the code as it's shown in the profile without stopping. It doesn't look up, down, left or right, it just goes forward on the track.
So when it loads into the dungeon, it's going on that dungeon code at full speed, when the character dies and resurrects, it's still trying to execute the next coordinate in the dungeon code. That's why it just stands there,

Our problem is "kicking the train off the tracks" so when the bot dies so it will execute the 'navigate back to dungeon track'/code.
Now the issue with this is, even if we get this working - the bot will practically restart the dungeon navigation, meaning it's not going to continue where it died, it's going to re-navigate each pull coordinate from the start.

Like I said before, the bot only goes forward in profile code.
One way to make it look up, down, left, or right is to use CustomBehaviors or Plugins.
Unfortunately we'll probably have to end up making some sort of CustomBehavior to fix the death issues unless the Honorbuddy dev. team implements some sort of option in the API.

 

Lemme guess, at the part where the statues come to life and attack/spam fear on you? Lol

 

How about this.
Instead of Hearthing, we just make it walk out of the instance, then restart the normal [DD] profile code?

It would save a lot more time if your Hearth is in... Stormwind or somewhere else.
Also it would be a more global solution to other people who are using the profile.