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

Are you over level 90? If so that's why it's skipping the last boss.
The first boss is a bit tricky to work with because it patrols around the entire first room - having the bot seek out and kill him could potentially waste a lot of time depending on where he's located when the bot begins engaging it.

Adding a force kill code would be simple enough though.

[Hr][/Hr]

I pushed an update yesterday that makes it Moveto right in front of the instance portal prior to using the CTM - this would fix the error.

Due to the nature of the CTM I had setup, it would cause errors if it was switched with a RunTo/MoveTo

[Hr][/Hr]

Are you using any in-game addons? The code used to sell via the Mammoth is the same code across all profiles - and I know there's no bugs in it currently.

[Hr][/Hr]

Increase your loot distance, it'll loot Lockmaw then.

It freaking out at High Prophet Barim - does it recover from this?
If so, I think there's a Mesh issue in that area - this would need to be fixed by a core-dev (HighVoltz most-likely.)

To get it to pull more, if you have any profile experience (really none is needed since it's so simple) you'd just increase the density of the pull coordinates.

See GIF
You need to register and have one post to see spoilers!

What's happening in the GIF is: <DisableBehavior Name="Combat" /> turns off your combat routine so the bot won't fight. Then there's several RunTo coordinates that make the bot run into/aggro mobs.
Each RunTo is typically a pack of mobs - so for each RunTo you add is about 1 mob pack pull.
At the end, the <EnableBehavior /> line comes in to turn the combat back on so the bot fights.

I'd reccomend using a code editor to edit this since it'll make it about 60 times more easier.
I'm using Sublime Text: The text editor you'll fall in love with

In order to 'know' which mobs those RunTos are addressing, you'd have to go off what you know about the dungeon/profile.
Sometimes there's little comments in there that says - but most of the time I'm too lazy to add those.

[Hr][/Hr]

Not sure what would be causing that, but I'd reccomend a Mage simply because they can teleport to each dungeon instead of having to travel to it.

[Hr][/Hr]

Do you have a log of this?

[Hr][/Hr]

Are you over level 90? If so that's why it's skipping the last boss.
The first boss is a bit tricky to work with because it patrols around the entire first room - having the bot seek out and kill him could potentially waste a lot of time depending on where he's located when the bot begins engaging it.

Adding a force kill code would be simple enough though.

[Hr][/Hr]

I pushed an update yesterday that makes it Moveto right in front of the instance portal prior to using the CTM - this would fix the error.

Due to the nature of the CTM I had setup, it would cause errors if it was switched with a RunTo/MoveTo

[Hr][/Hr]

Are you using any in-game addons? The code used to sell via the Mammoth is the same code across all profiles - and I know there's no bugs in it currently.

[Hr][/Hr]

Increase your loot distance, it'll loot Lockmaw then.

It freaking out at High Prophet Barim - does it recover from this?
If so, I think there's a Mesh issue in that area - this would need to be fixed by a core-dev (HighVoltz most-likely.)

To get it to pull more, if you have any profile experience (really none is needed since it's so simple) you'd just increase the density of the pull coordinates.

See GIF
You need to register and have one post to see spoilers!

What's happening in the GIF is: <DisableBehavior Name="Combat" /> turns off your combat routine so the bot won't fight. Then there's several RunTo coordinates that make the bot run into/aggro mobs.
Each RunTo is typically a pack of mobs - so for each RunTo you add is about 1 mob pack pull.
At the end, the <EnableBehavior /> line comes in to turn the combat back on so the bot fights.

I'd reccomend using a code editor to edit this since it'll make it about 60 times more easier.
I'm using Sublime Text: The text editor you'll fall in love with

In order to 'know' which mobs those RunTos are addressing, you'd have to go off what you know about the dungeon/profile.
Sometimes there's little comments in there that says - but most of the time I'm too lazy to add those.

[Hr][/Hr]

Not sure what would be causing that, but I'd reccomend a Mage simply because they can teleport to each dungeon instead of having to travel to it.

[Hr][/Hr]

Do you have a log of this?

 

Stonecore, Grim Batol, Tol'vir, world trash farms - you could just experiement.

Death support is currently broken.

[Hr][/Hr]

Death support is currently broken and cannot be (reliably) fixed via profile.

[Hr][/Hr]

Huh.

[Hr][/Hr]

Tell me which (exact) profile this is so I can fix it.

 

The log suggests you stopped the bot mid-dungeon run and started it again.

Once the bot is started, the vendor logic is given priority over the profile logic which will cause problems because the profile logic tells the bot how to properly handle the vendor/repair (there's no vendor/repair support naturally while in a dungeon on the questing botbase.)

[Hr][/Hr]

Awesome to hear!

[Hr][/Hr]

This should've been fixed several days ago - are you using the SVN checkout?

[Hr][/Hr]

Download links should be at the top of the page - they're the blue buttons.



[Hr][/Hr]

This is more of a Singular problem and would be difficult to reliably fix it via profile.
I've already sent several fix attempts, but they don't seem to work for everybody.

For whatever reason Singular will ignore critters that attack it - which causes the bot to freeze up.
This is also an issue in Stratholme which the roaches.

[Hr][/Hr]

Awesome, lol

 

Could you post a log of this?

[Hr][/Hr]

Death support doesn't work because the function used to replace the native death logic isn't working properly.
So that affects any method of custom death support.

Some people have rigged together a mess of plugins and whatnot that seems to make it work more persistently - but there won't be a solid solution until TreeHooks.Instance.Replace() is fixed for Death_Main.

[Hr][/Hr]

This log ended with a FlyTo error saying your character can't fly in the zone you're in.

If your character can fly, and it's fasely reporting this - then you will need to report this to the Bugs section - the issue is within the FlyTo behavior and would need to be addressed by the core-devs.