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

Hmm, I'll check the coordinate, shouldn't take much to fix.

[hr][/hr]

Did this issue occur before you updated the bot?
Both of your logs are outputting the same error which seems to be an issue with Singular.

[hr][/hr]

If I'm not mistaken, Ragefire Chasm is already on the profile pack.
It's one of our older profiles, so I'm not entirely sure how reliable it is. But I believe it requires a QuestBehavior from our folder to work.

 

I'll have to do some researching.

Does the issues occur when the bot is inside of the dungeon? Can you explain in detail exactly what's happening?

 

Pro tip:
Combat isn't handled through the profile.
The issues you're having is a fault in your own configuration, not the profile.

Are you using Singular?

We've tested these profiles more than enough to know that the code works optimally or else we wouldn't release it.
With the recent bot update, it should be common sense to know that things will change or break.

I'm sorry that you can't get the profile to work, but don't bash the pack just because it doesn't work for you.
Instead, post a log so I can properly assist you.

 

No worries.

Just remember, a profile is nothing but a instruction sheet that tells the bot what to do.
How the bot actually "does" it, is completely dependent on the user-configuration.

If there's an error that's not a stuck-spot error, then it's most likely your CombatRoutine or a Plugin interfering.

I'm sending a tester to execute that profile as we speak to ensure that it's optimal for the newest bot release.

 

No, I haven't really messed with the bot much after over 44 of my hand-level 90s were banned.

Still retaliating from that.

However, the tester I just sent is having issues not attacking mobs inside of the instance.
After looking into the bot's "Change Log" for this newest patch, there was a LOT of changes to the pulling system.
No doubt the issue lies within there.

I'll do a bit of research to see if I can figure out exactly what's going on.

 

*IMPORTANT*​

The new bot update has broken a lot of our code because the developers of the bot have decided to change the way UserSettings are controlled.

If your bot is running through packs of mobs without attacking, this is why..

Instead of controlling the distance at which the bot pulls mobs, we now control the distance at which the bot TARGETS+ENGAGES mobs....
So if a spell caster shoots you at 30 yards away, and the <TargetDistance> code is set to 20 yards, the bot will never fight it because the bot is out of the targeting range...

With a LOT of our farming profiles, we typically set the PullDistance to 1, this way the bot can run past mobs to get to the priority mob faster.
But now that PullDistance is now TargetDistance, the bot won't fight mobs back since mobs can attack at 5-10 yards away on melee ranges.

The solution would be to set the targeting distance to above 40 in all of our profiles, but this would mean that the bot will no longer be able to sneak past mob packs which will be an issue in our mount farm dungeons and Transmog farms.

 

For now, yes. The issue has been reported to the developers.

 

Yep.

 

Hmm, I'll take a quick peak at the code.
It may be because the behavior we used has become dated and needs to be updated to the newer behavior.