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

Code:

[11:51:53.868 N] INACTIVITY TIMER TRIPPED! LOGGING OUT!
[11:51:53.884 Q] Bot stopping! Reason: Main window is closing

Your bot stopped itself.
I believe there's something in the Settings & Tools that lets you determine if this happens or not.

[HR][/HR]

Its been suggested multiple times and considered.
It'll be added, but I cannot tell you when.

At the moment I'm busy with other projects.

 

The quest behavior used for this location was broken as of 6.0.2.
The behavior is ran with for the Chess event.
If you were to remove any lines regarding the behavior/chess event, it would fix itself.

CTRL+F for File="Chess"
For any line that has chess in it, remove the entire line.

[Hr][/Hr]

I couldn't guess - maybe the "Loot Mobs" is unchecked in your Settings & Tools.
Else, I need to know which profile you're using, and a full unedited log.

 

The Botanica > Gundrak.

It waits because you can't run more than 10 dungeons per hour.
If you go over this, then you'll get locked out.

Yes, it's safe to use /stats /stats2.
Just as safe as it would be to use Recount to output damage information.

[HR][/HR]

In your log.
But you didn't post it.

[HR][/HR]

I'll edit this post with an attached profile once I get time.
You can't configure the bots to repair from the guild bank, you'd have to instead hard-code it into the profile.

[HR][/HR]

If I get time.
I doubt I will be able to anytime soon though.

[HR][/HR]

Don't double post.
If you have a new issue to add, then edit your existing post.

[HR][/HR]

Due to bad meshing in that location, extra navigation support has to be added into the profile.
When the vendor routine starts, a range detection line should be seeing if you had just left the instance or not, if so - it should be forcing the bot to walk out the other side.

The only thing I could guess is that the range detection isn't working for you - which it is for my testers so I can't figure out what's going on there.
The code could be a bit more fine-tuned.

[HR][/HR]

It depends on which profile you're using.
If you're using the normal profile (non- Sell All, etc), then just add it to your protected items file, which it should be already.

[HR][/HR]

That Singular line has nothing to do with the bridge not activating.
I'll need a full log please.

Alternatively, try turning your TPS down in the 'Settings & Tools.'

[HR][/HR]

The Botanica > Gundrak.
Information regarding this is already posted on the orignal post.

[HR][/HR]

You'd have to redesign the entire exiting code and add a whole new block of code for hearthing.
Would be better discussed over Skype.

[HR][/HR]

Most SK profiles are dependant on your realm's economy.
So I couldn't give you a estimate.

SK-Sra'vess is still one of my personal favorites.

[HR][/HR]

I can't guess what the issue is.
I'll need a log for when the bot crashed.

[HR][/HR]

I don't see the point.
The GPH for the majority of MoP dungeons is horrible - even with the Potion of Luck.

[HR][/HR]

What race is your character?

[HR][/HR]

It depends on what you're farming.
Feral Druids = Dungeon Farming
Beast Master Hunters = Enviromental Mob Farming. (SK Profiles.)

[HR][/HR]

That Singular line has nothing to do with the bridge not activating.
I'll need a full log please.

Alternatively, try turning your TPS down in the 'Settings & Tools.'

[HR][/HR]

It looks to me like your Singular is messing up.
It's doing nothing but spamming the log with "EnsureMovementStoppedWithinMelee."

I couldn't tell you why it's doing that, perhaps a bad configuration in your settings.

[HR][/HR]

The Botanica > Gundrak.

[Hr][/Hr]

I need more information than that..
Which profile are you using? Which combat routine?
Perhaps a log.

[HR][/HR]

Tell me which exact Pit of Saron profile it is.
And maybe post a log.

[HR][/HR]

Because other combat routines have constant issues while running dungeons on the questing botbase.
Singular is the only reliable combat routine for this kind of stuff.

That, and I don't feel like dealing with problems caused by a faulty combat routine.
I know Singular works.

[HR][/HR]

The UserSettings warning means nothing.

The mailing issue sounds like a fault in the vendor logic.
The bot is failing to consider the mailbox provided in the profile and instead is just looping code.
Post a full log and I'll be able to look more into it.

 

I think there was a profile for it, but it may be broke since it's so old.
I doubt I'll be able to get around to making a new one soon. Busy working on other projects.

 

It's a technical issue on your end somewhere.
The only thing I could suggest is use a completely fresh version of the bot.

[HR][/HR]

What specialization are you using?

[HR][/HR]

Unfortunately it does not.
The data is saved 'on RAM' - once you disconnect or log out of the game the variables used to store the numbers will wipe.
However, I'll need to do some Lua research - but there may be ways to dump the data into a text document.

The code itself is very simplistic and doesn't have a lot of flexibility.
Even going into the negatives (start the bot and lose 1 gold) will mess it up.

 

Since Laj is up on the pedistal, to avoid navigation issues - the bot pulls him at a distance using a class-based spell.
Failures in the cast/spell would be: Bot not targetting Laj (translation issues), casted spell is no longer in the game, out of range, not properly facing hi.

I've been meaning to revise the pull method on him, but I haven't had the time.
Perhaps the easiest solution would be to make the bot walk up to him for an auto-aggro, then walk away from the pedistal.

 

Glad to see it's working out well for you. ^^

[HR][/HR]

This issue has been around for ages.
It's not a profile issue, but a bot issue.

Could you post a log?

[HR][/HR]

This should do it:
<Blacklist>
<Mob Name="Name" Id="123456" Flags="Combat" />
</Blacklist>

I haven't checked the documentation, but I believe you can blacklist by GUID if you don't want the bot to ignore all of the mobs with that ID.

[HR][/HR]

Yes, it's normal.
Just ignore it.