AutoEquip equipping BoE's when only BoE option is disabled

[hackersrage]

Not sure where to put this, as it seems to be an issue with the core for AutoEquip.

A couple of things >

1. Didn't there used to be extensive options for controlling the slots which AutoEquip manages. I recall earlier versions of HonorBuddy having the ability somewhere to turn on/off individual slots for auto-equip as well as setting the minimum levels in a Property Grid view. Was this removed or moved ? If removed -- why ? If moved -- where is it now ?

And the problem >>

[16:57:19.698 N] [AutoEquip] Equipping item Evie's Quartz Loop (Evie's Quartz Loop - Item - World of Warcraft) instead of Cliffbreaker Seal of the Landslide (Cliffbreaker Seal - Item - World of Warcraft) (slot: Finger1) - it scored 1570.00 while the old scored 1148.00

This item was a BoE blue in my bag worth a decent sum at the auction, yet, the bot decided to automatically equip it even though my settings are as follows :

[x] Auto Equip
[ ] Equip BoE Epics
[x] Select Talents

Note, there is no option to deselect BoE's in general. The middle option being unchecked used to handle all BoE's in general.

Can someone address this please -- if filter was removed, please add it back in as this results in the loss of potential money via items.

 

[prettygreat]

Which profile are you using? Some profiles actually overwrite the settings you have.

 

[hackersrage]

Kicks, however the setting wasn't overwritten, as stopping the bot to look at the settings, you can see whatever the script set it to. These settings remained unchanged. Additionally, you can look at the begining of the script to see what plugins were initialized or what settings were changed.

I am triple-checking the script code for any overrides, however so far I have found none pertaining to equip methods. The only thing regarding auto-equip is commented out :

<!--<CustomBehavior File="UserSettings" AutoEquip="true" />-->

Line 948 in "Questing Profile Pack\WoD\[H - Quest] 90-92 Frostfire Ridge [Kick].xml"

So this is not to blame. It is most definitely a core auto-equip issue.