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

I need a full log for this.

[HR][/HR]

Things like that are handled by your combat routine, not the profile.
You'd have to look through your combat routine's settings and find an option.

If it's not there, then you'd probably have to hard-code the logic into it - or try a different combat routine all together.

[Hr][/Hr]

Thanks for the logs, but they don't tell me much aside from FlyTo causing your profile to break.
I need the full log.

 

I've never even wrote a profile for the other entrance, let alone would add in navigational data to this profile for it.

The only thing I could guess is that when you're leaving the dungeon, the coordinate used to leave the dungeon isn't compeltely hit due to latency or FPS inconsistencies so when your game is finished loading the bot continues to navigate to that exit coordinate which happens to be where the other entrance is located.

I could change the exit logic around a bit that should fix that.

[Hr][/Hr]

That's never been reported before.
When it happens, could you post the log your bot generates?

 

Logs should be located here:
Honorbuddy Folder / Logs / <RealmName - CharName> /

[Hr][/Hr]

Your log claims the bot is executing the vendor code for the Mammoth.
The only thing I could guess is that the ForceVendor code is broken. There's not much I can do about that.

A profile that uses Lua to sell rather than Honorbuddy's vending logic would fix the issue.
I could make one for Tol'vir medium, but I'll need to know which items you're wanting to sell.

 

I just modified the RunTo code at the end of the profile and changed it to a MyCTM that terminates when you exit the dungeon.
If it runs mindlessly into the wall near the portal then tell me.

[Azyul Cloud] Deathcharger's Reins - Endless Farm - Modified Exit

 

With the Lua sell, it could use the Mammoth to sell while inside the instance.

The profile you're using was created before the 100% dungeon completion existed (and before the stat nerf making everybody much stronger.)
So at the time, the routes and monsters that this profile kills was the most optimal.

I've re-created a newer version of Tol'vir that takes more efficient paths and kills all the bosses, but it's a Suicide Pull run.

 

These profiles are only designed to loot the mount, there isn't any Guild Bank deposit logic because there's no point.

Also, none of these profiles farm Grim Batol.
As it stands, there's only mount on this project and no mounts drop in Grim Batol.

 

I don't see the "is not able to reach" error in this log.

I looked through the profile and the MyCTM that's giving you issues is the MyCTM used when the bot is started while inside the dungeon.
Changing it from a MyCTM to an actual MoveTo code would most-likely fix your issue.

By using Find & Replace, you could replace it fairly easily.

Find:

<CustomBehavior File="MyCTM" X="-10693.63" Y="-1310.474" Z="17.69033" />​

Replace:

<MoveTo X="-10693.63" Y="-1310.474" Z="17.69033" />​

[Hr][/Hr]

There's no reliable solution to fixing it.
The logic used to replace the death hook isn't functioning properly which is an issue with the bot itself.

People have created their own alternatives, but every alternative seems to only work for 'some' people.
So there's nothing reliable enough to make public.