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

The Tempest Keep profiles (along with all of the other Outlands profiles) were built by FrostFever, a former developer.
I personally don't know anything about the code structure or the reliability of them.
But just to be sure, are you using the Questing botbase?

The current plan is to completely re-code everyone of them.
At the moment, I'm the only person working on this pack, and I'm not entirely sure when I'll be able to get around to this - but hopefully it'll be soon.

 

Hello everyone!

I've sent out a new update for every profile in this pack!
This update features a new in-game statistic mechanic. See the screenshots below:





What you see in the pictures above will appear after every dungeon run, or vendor run.


Alternatively, you may type /stats to see this:




Or, typing /stats2 will show this:





The statistics currently calculate:

- Farm Scores
- Gold-Per-Minute
- Gold-Per-Hour
- How much the items in your bag are worth.
- How much raw gold you've picked up (per dungeon run)
- How much gold you've obtained from vendoring (per vendor run)
- How much gold you've made since you've started the profile.
- How long the dungeons take.
- How long you've been running the bot.​

More features are yet to come!

And as always, these features do not / will not require any third-party software or plugins. :3​

 

Hello!

Which profile are you speaking of?

The Randomizer profile is 'considered' the safest out of all of them due to its unpredictability.
Any other randomized profile would be the second safest.

I personally don't have a recommended run-time for any of the profiles, however some people claim they run their bots 24/7.
Then again, some people say they are banned after the first day.

The last time I botted for money, I ran 5 characters - same realm - same profile for 3 days straight with no stops before there was a ban, and this was on the Halls of Lightning profile.

 

From the looks of the log, the bot got stuck right before the first boss after it cleared out the room with the spiders.
For whatever reason it was unable to navigate to the CTM coordinate. (the coordinate that makes the bot skip the boss)

It seems that the bot got stuck on something a few times before trying to navigate past the boss room, how or what it got stuck is the question.

 

Another Update?!

All profiles now enable the command: /stats once the profile is started.

Upon typing /stats, you will see this:



'This' will monitor your overall run times, dungeon run times, total gold obtained, etc..etc..

I'm planning on adding more detail, but for now basic gold/time numbers will have to do. :3​

​

 

:3
I still have a lot of plans on further detailing it out.
(GPH, average run times, Farm Score etc)

I also need to set a calculation to get the dungeon's run-time (in seconds)
Right now the code only supports Hours/Minutes. D:

There may be a bug on the code right now, still fine-tuning it.

EDIT:
Bug smashed.

On a side note, if you use /stats while the first dungeon is being ran, it will most-likely show a random negative number.
This is not an error, it's just me being lazy. :3

I'm also adding "Total Gold" on the ~Last Dungeon! and I'm adding another section for "~Current Dungeon!"​

 

Does the bot ever get to coordinate X="-338.6151" Y="-720.4265" Z="28.57711" ?
(see screenshot)

​

If it doesn't get to that coordinate, the CTM will fail.

 

Hmm, okay.
I can try adding another non-CTM MoveTo coordinate after the pull is completed.
Maybe that will 'rationalize' the bot before proceeding to that next coordinate.
I'll edit this when the update has been sent.

EDIT:
Update sent on ZIP and SVN.

One thing that -may- be causing issues is: Your character isn't killing the spiders fast enough which causes them to run into their little caves.
Honorbuddy may have navigation issues inside of those caves, so it 'Blacklists' the spiders, which that would explain why Honorbuddy is continuing without killing them.​

 

During testing, I've noticed the bot will run up to the mailbox, then walk away.
Then some times it'll walk up to it and actually mail. Whether or not it mails seems entirely random.
I believe that the issue could be within the 'ForceSetVendor' behavior.
There's a few things I may be able to try that might fix it, but it'll need to be tested.