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

If it's not depositing / selling properly, then it's typically caused by you not having the quest behaviors copied over.
The tab depositing issue has been noted (and fixed) - but the fix was never deployed to the profiles since Blizzard raised the cap of cloth to 200.


Protecting the items depends: If you're using a modified sell profile (like Sell All) or if you're just using a normal profile.
My Sell All profiles use a custom-wrote selling code that completely ignores Honorbuddy's rules.
The main purpose of these is for convience - it allows users to load and start the profile for suicide botting without having to modify the bot's settings.




If you're using a "Sell All" profile - then you'll have to protect the items with using an array.

Example, add this under <QuestOrder> in the profile:

PHP:

<CustomBehavior File="Misc\RunLua" Lua="ProtectedItems = {'Cloth', '1234', 'ff0070dd'}" />

With the above example, any item containing the word Cloth will be protected.
Also, any item with the item ID 1234 will also be protected.
And, any blue rarity item will be protected given that ff0070dd is the hex color for blue items in WoW.

All of these options (plus more) can be used, and must be separated by a , along with ' ' wrapped around the word.​

If you're using a normal profile, then there's multiple ways of protecting an item.

One option would be to protect the items on a profile-level. This will only protect the item for the specific profile you're running.
To add items to this, open the profile with a text/code editor and look for <ProtectedItems>
Here you would add a list of items you want to protect along with the item name and ID/entry.

An example:

PHP:

<ProtectedItems>
    <Item Name="Headdress of Alacrity" Entry="27466" />
    <Item Name="Mana-Sphere Shoulderpads" Entry="28374" />
</ProtectedItems>

The second option would be to protect the items on a global-level.
This simply means the items will always be protected regardless of which profile/botbase you're running.
In your Honorbuddy folder you should see a file naned "Protected Items.xml"
This works the same way as the profile-level example above, just add your entries to the file.​

​

​

 

An easier route to depositing items would be to just use the "UseItem" quest behavior.
Since selling/depositing an item is the same as 'using' it - it should work fine.

Replace that mess with:

PHP:

<CustomBehavior File="UseItem" ItemId="21877" NumOfTimes="500" WaitTime="250" TerminateWhen="!HasItem(21877)" />

NumOfTimes will make the code run 500 times. WaitTime will make it wait 250 milliseconds inbetween deposits. And TerminateWhen will make it terminate when you run out of the item.
Copy this line for every item you want to deposit, and replace the two 21877 numbers with the item ID you're wanting to deposit.


You can get the ID numbers from WoWhead.
Simply go to WoWhead, search the item - and look at the URL.
At the end of the URL will be the item ID.
ex:
http://www.wowhead.com/item=21887


Example of depositing two different items:

PHP:

<CustomBehavior File="UseItem" ItemId="21877" NumOfTimes="500" WaitTime="250" TerminateWhen="!HasItem(21877)" />
<CustomBehavior File="UseItem" ItemId="21887" NumOfTimes="500" WaitTime="250" TerminateWhen="!HasItem(21887)" />

This would deposit Netherweave Cloth (21877) and Knothide Leather (21887).

 

Thank you for the details.

So, it pulls Ick - but as it runs to pull more mobs it runs out combat-radius causing Ick to de-aggro?
If that's the case, it should be a fairly easy fix - like you said just enable the combat when it reaches Ick.

 

Alright, I'll check the profile code and see if it's something that can be blindly changed without causing errors.
If it is, an update should be up in about 10 minutes.

If not, I'll need to go out and field-test it.

Edit:
Doesn't seem like the bosses were commented properly when the profile was made.
But I think I found where it pulls Ick - from the looks of it the profile is actually meant to stop when it pulls him.
The true error seems to be that the bot is ignoring the "combat enable" line - which is an issue in other profiles as well.
I'll add in a wait timer that'll make the bot wait so it has more time to consider activating combat.

I'm sending a tester out to ensure that this coordinate is where Ick is pulled.​

Edit 2:
I sent a fix to the SVN.
I'm not entirely sure if it'll fix the problem or not - but it should.
I've ran a tester on the dungeon but it seemed to stop at Ick even without the fix. So it's a bit hard for me to debug.​

 

This is a known issue, unfortunately the quest behavior used to control that fight is broken.
I'll need to look an alternative until it's fixed. Not sure when I'll be able to do this - but it's on the bug tracker.

[Hr][/Hr]

Alright, awesome!

 

Known bug, there's no live fix at the moment.
Use a lesser pull desnity if your character can't handle the heavier aggro pulls.

 

Have you copied the quest behaviors over?

 

It works fine, but you still haven't answered my question.
Have you copied over the Azyul Quest Behaviors to your Honorbuddy installation?
If you fail to then things such as the stats command and universal navigation will not work.