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

Gotta be that CTM coordinate. I'll poke around at it sometime today.

[hr][/hr]

Awesome! Glad everything worked out for you. :3

[hr][/hr]

Yep, some profiles require the behaviors to work and some don't.
Anytime it says "Unable to parse While behavior" or anytime the bot just stops, it's because of a missing behavior.

 

That profile is Frostfever's territory.
Frostfever hasn't been active in the project since August 2nd since he became a father.
Normally he would've debugged all those issues out.
When he was active, he created almost all of the Outlands dungeons/raids in less than a month. None of which have really went through heavy testing.


Thanks for your report though, I'll add some notes.

[hr][/hr]

You'd just have to add a code in the profile to switch the dungeon to Heroic before starting.

Or, you also may be able to just switch to Heroic before the bot enters the instance and it'll do it.
However, any heroic bosses won't be killed unless they're in the path of the normal run.

 

Added a Lite-Gold Run option to Grim Batol's Detection Diamond.
To activate it, during Detection Diamond execution - walk backward.
The previous gold run is still available, and is now considered "Heavy Gold Run."

The lite gold-run will run the same exact coordinates of the Heavy run, except it pulls smaller mob packs.
This run has been tested and completed by a iLvl 453/461 Mistweaver Monk and a 459/462 Guardian Druid.

The mobs around Khardros' Anvil are still harder than they should be... but I've added a code that will help the bot kill them more sufficiently.
However.. it's still a suicide run if you aren't geared enough considering the boss' unpredictable patrol path walks past the mobs.

Guardian Druid seems to be the best at running the dungeon..
Decent damage, and high suitability. Even with the worst of all pulls (Khardros pull + Gronn Brute pull) it survived fine.

 

Things like this are completely unpredictable and aren't always as global as you think. 7/10 the issue is specific to your configurations, that's why profile developers typically ask for a log, that way we can see how the code is being executed on a technical level rather than a visual level.
I've ran at least 14 testers through that profile, all different classes - factions - mount speeds and none have been able to emulate any sort of issue while navigating.

Skipping mobs that are out of the way, attack mobs in the way: Normal run pulls intentionally skip mob packs, it's designed to run the dungeon how a typical dungeon group would.
At least a optimized run would, Grim Batol is still undergoing tweaks considering every run-type was coded in less than an hour.


As far as Singular combat optimization - I know what you mean.
My geared Monk that was botted wasn't able to even come close to 10% the efficiency of my under-geared Monk that was human controlled.
Singular is a VERY choppy combat behavior. The only reason we recommend it for our profiles is it's one of the only behaviors (that I know of) that not only supports every class, but is able to navigate while in a dungeon properly.
I was able to Tweak my Singular's code a bit for Monks so that it spams Spinning Crane Kick at 2 or higher mob pulls while rotating small healing spells / cooldown buffs. It did increase the efficiency, but not to human-ability.

For now, with the limitations of Singular - the Grim Batol run won't be the instance-of-choice for demanding gold farmers.
However, once our gear standards rise so to will the ability and profits.

 

I didn't "get you wrong" at all.
I was just agreeing with you by giving my own experience as an example while adding a few little details to go along with it.
It's no mystery that the bot .. as you say .. "underperforms" while running this dungeon but like I said, there's nothing we can do about that aside from modifying a little bit of Singular's code and waiting for Blizzard to "simplify" the game further as they tend to overdo..

That's a CTM error. In order to get the bot to jump off the edge, the bot has to be told to go to a specific coordinate that's mid-air off the ledges.
However, it can be a hit-or-miss situation because when the bot jumps off the edge, it could easily overshoot the coordinate causing the bot to never finish its navigation to it.
Speed increases/decreases can cause this more frequently. But at the same time.. it can be completely natural given the millions of variables.
So, given that - when the bot is teleported back to the beginning of the instance, navigation fails because the bot still wants to navigate to that coordinate - which it obviously cannot anymore.

I'm looking into fixing this - after I get some sleep.

 

You may want to consider buying the bot... Or at least hiding the fact that you're using a modified version before submitting your log.
The BlaSOD (black screen of death) happens when the bot forcibly navigates directly up from it's current position - while spinning.
This happens rarely, but can easily be fixed.

 

The Transmogrify profiles are already designed-by-default to only loot the mobs that drop the pieces of the set.

Also,
<CustomBehavior File="UserSettings" LootMobs="False" />
<CustomBehavior File="UserSettings" LootMobs="True" />
Is all that's needed when handling loot settings.

Anywho.. I'll see if I can schedule this profile into development soon.
Thanks for the recommendation. ^^


EDIT:
This profile is now in development. It should be completed soon.

EDIT2:
Profile complete.

 

Delete your "Quest Behaviors" folder located in the root of your Honorbuddy folder.
After you do that, copy a new Quest Behavior folder from a fresh Honorbuddy download.

 

Blizzard limits the amount of instances you can do. Which is five instances per hour.
If you do the math, that's -about- one instance every 12 minutes and 30 seconds.
If you pass this 12 minute 30 second limitation, you'll hit the instance overload.
Which simply means you cannot enter the instance until the overload is cleared.

The code that you're seeing is ensuring that you do not hit the overload limit by waiting the excess time out before leaving the dungeon.

This is more-less a safety feature.

1) If your character didn't wait, and did hit the overload. Then the character would mindlessly run in to the instance, hitting the overload over and over. And if anyone sees that.. they could easily assume you're a bot.
2) PvP servers. If the character gets locked out of the instance, that's an easy target for opposing factions.​

We could code the profiles so it doesn't wait if the item was obtained, that way the travel time to the next instance could clear the overload, but it's usually just an easier solution just to make the bot wait regardless.