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

Okay.

One more question though: When it goes AFK, where does it stand?

 

You must edit the file: "Protected Items.xml" inside of your Honorbuddy folder.

For each entry you remove from the "Protected Items.xml" file, the bot will sell that item.

Example:
If you remove <Item Name="Frostweave Cloth" Id="33470" /> the bot will then sell that item.

 

I'm on mobile right now, so I can't manage my attachments.
Once I get back home I'll resend them.

Here they are:
View attachment KaelThas.cs
View attachment Chess.cs ​

 

I'll check the profile when I get back home.

[HR][/HR]

There's no Hellfire Ramparts profile in this pack.
You're posting on the wrong thread.

Not only that, I didn't code that profile.
It was created by FrostFever and age has most-likely taken its toll on the profile.
As stated on the thread that this profile is featured in, a lot of profiles in that pack are old, and most of the code in them are no longer reliable.
These profiles are still in the process of being re-built.

 

Right before the bot enters, switch it over to Heroic.

 

Removing the Frostweave from the Protected Items list will cause the bot to sell them.
Did that fix your issue?

 

Hello everyone!

I'm currently in the process of restoring / rebuilding some of the older profiles that have been "broken - by - time".
Some of the focuses will be:

- Rebuilding all of the Outlands profiles + creating multi-pull versions of them
- Molten Core
- Eastern Kingdoms + Kalimdor
- Some of the older Northerend profiles.
- Re-introducing / re-building the old Quest Behaviors (if needed.)
- Re-building the transmog farms.​

This process will take place over the next few weeks, depending on how long the building+testing process will take.​

"What do you mean by 'Re-Build?'"

Since the creation of the older profiles in this pack, 'we have' discovered new methods of code handling, mob pulling, vendoring methods, and more.
Most of the older profiles suffer from minor and major issues because they are built using the our older methods.
Some of the issues our new code addresses that our old didn't are:

- Bot trying to vendor while in dungeon, causing it to bug out.
- Bot not entering / exiting the dungeon properly. + No failsafe to detect if bot didn't enter/ exit properly.
- Vendor routine not working all together.
- Lack of failsafes - no error handling if something goes wrong.
- No universal navigation. - bot has to be started in specific places.
- Terrible path handling. - too many coordinates used in the profile causing chunky/slow navigation
- Plus more.​

 

It used one of our older behaviors.
I'll have to run some testers out to the raid to see what all is exactly wrong, but it could be added to the list.

If you want to try it, here's the behaviors it requires:

View attachment Chess.cs ​

This behavior is for automating the "Chess" event with Medivh.

EDIT:
I'm working on the profile as we speak.
Currently, I've just fixed a few issues in the pre-quest routine.
Working on the actual run now.

EDIT 2:
I've sent out a SVN update that fixes a lot of issues.
(see R.682 for details)
Right before I finished testing the profile, my network went out, so I wasn't able to run a complete finalization test.
However, I'm confident that it should operate just fine.
Once my networks come back online, I'll send out a couple of testers to ensure reliability of the profile.​