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

Thanks for the donation!
Glad to it's working out for you!^^

 

I could also change the global values to slow it down a bit for everyone - that way the issue is avoided for everyone.

 

Try this one:

​

View attachment [N] Lost City of the Tol'vir - (x1).xml

 

Ops, looks like I forgot to add the ProtectedItems array to the profile.

Under <QuestOrder> add this:

PHP:

<CustomBehavior File="Misc\RunLua" Lua="ProtectedItems = {'notset'}" />
<!-- Protect items by ID or name.  Separate items by a comma.  Example:   {'1234', 'Glyph', 'Leather', 'ffa335ee'}
This will protect item ID 1234,  any item with Glyph in the name, and any item with Leather in the name.  ffa335ee is the Hex for purple, so all purple items will be protected.
You can also protect by rarity.
ff9d9d9d = Grey
ffffffff = White
ff1eff00 = Green
ff0070dd = Blue
ffa335ee = Purple
-->

Then you can pretty much follow as it says.
Use the array to protect items by Name/ID/etc

 

Hmm, the code sniffs itemLink and itemString.
So anything those two functions return - you can protect by.

See the Wiki here:

itemString
itemLink​

After a quick look, I don't believe there's anything there that returns whether or not the item is binded or not.
The only function in the API I was able to find that does detect bind status is GetLootRollItemInfo

Unfortunately, this isn't used in DynSell. : /

 

DynSell(); operates on WoW-API Lua.
WoWItem.IsSoulbound is HB-API.

You could technically parse between them, but at that point we'd be modifying the DynSell(); code.
Which then we would just add GetLootRollItemInfo.

 

DynSell is pulled remotely, so I could technically make updates to it in real-time to include GetLootRollItemInfo.
But at the moment there's plans to get DynSell() off Lua and onto C#.

So any updates to the current DynSell() are only made if absolutely needed.

 

Singular (your combat routine) seems to be behaving very strangely.
I believe it was updated recently, so the error it's reporting is a bit new to me.

I normally wouldn't suggest using any other combat routine aisde from Singualr, but could you perhaps try a different one?