autoequip problem

[Croga]

I'm leveling another DK at the moment, and I found the Intellect value still not low enough. When I first did this, the DK was already 72 and switched to strength items. But now I watched it in the transition from Outland to Northrend, and again it equipped Int items.
I lowered Intellect to "-800" and now it securely does not equip INT items.

It doesn't have anything to do with the value of INT on the item. It has a lot to do with the value of STA.

Example:
STA value = 1
STR value = .8
INT value = 0

Item:
STA 100
STR 100
INT 0
Value: 180

Item:
STA 300
STR 0
INT 300
Value: 300

AutoEquip will always select the second item since the value of STA is way higher then that of the previous item.
This will happen in just about all instance where you go to the first area of the next expansion. The difference between level 80 Northrend items and level 80 Hyjal items is so big that you *will* be equipping items with the wrong main stat.
There isn't anything wrong with that pers? if the stat values are correct. A Blood DK needs STA a lot more then STR since STA can make him nigh invulnerable. The fact that the items also has INT is unfortunate but not a problem. As soon as the bot gets an item of the same iLvl with STR on it, it will automatically equip that item.

 

[tanro]

Im having the same issues with my druid equiping 1h maces when leveling as feral. Any way to set it to not equip a weapon other than staff or polearm?

 

[Croga]

Im having the same issues with my druid equiping 1h maces when leveling as feral. Any way to set it to not equip a weapon other than staff or polearm?

Go into the Settings of the addon and use the WeaponType selection box.

 

[h0n0r1]

Thanks for elaborating, Croga.

This all basically burns down to something that might be called "no-go items". Like int items for DK/retri/younameit. I didn't write down the stats of the items that were "wrongly" equipped, but it might be something like this:
Outland item, Level 68 leveling Blade's edge Mountains, chest piece: Soul Saver's Chest Plate - Item - World of Warcraft 37str, 17sta
Northrend item, level 69 leveling Borean Tundra: Chestguard of Salved Wounds - Item - World of Warcraft 53int, 33sta

Yes, the northrend item has more stamina, but to lose 37 strength is >never< ok for a dk/retri... this is what AutoEquip should count in, and it actually doesn't at the moment. But you can "cheat" it to disregard certain items by giving the unwanted stat a hilariously low value.

 

[Croga]

Yes, the northrend item has more stamina, but to lose 37 strength is >never< ok for a dk/retri... this is what AutoEquip should count in, and it actually doesn't at the moment. But you can "cheat" it to disregard certain items by giving the unwanted stat a hilariously low value.

If losing STR is never okay then STR should have a higher stat value and STA should have a lower stat value. That would solve the issue permanently.
Example:

IF
STA value = 0.1
STR value = 1
INT value = 0

THEN
Item:
STA 100
STR 100
INT 0
Value: 110

STA 300
STR 0
INT 300
Value: 30

It's all a question of giving the plugin the correct information.
I will simply allow my DK to equip the INT item since the added survivability is much more important than the small increase in DPS. If you disagree with this then you can simply tweak the value of STA and STR, you'll never need to do anything about INT at all.

 

[h0n0r1]

If losing STR is never okay then STR should have a higher stat value and STA should have a lower stat value. That would solve the issue permanently.

Nice idea, but still not good enough, because I >do< want to have good stamina values, but not at the sacrifice of strength. And to have AutoEquip compare them, you need to give the undesired an influence that is stronger than all other values. Like saying: OK, 80sta is nice, but hey, it has int, so I'm not going to take it.

Oh, and having "increased survivability" through stamina is at least questionable. Losing strength makes fights take longer, which in turn will allow mobs to do more damage to you... In the example of the two items I posted, it's surely not OK to switch to the northrend item.

 

[Croga]

Nice idea, but still not good enough, because I >do< want to have good stamina values, but not at the sacrifice of strength. And to have AutoEquip compare them, you need to give the undesired an influence that is stronger than all other values. Like saying: OK, 80sta is nice, but hey, it has int, so I'm not going to take it.

Oh, and having "increased survivability" through stamina is at least questionable. Losing strength makes fights take longer, which in turn will allow mobs to do more damage to you... In the example of the two items I posted, it's surely not OK to switch to the northrend item.

I still stand by my explanation: You can calculate the effect of STR on the duration of the fight and of STA on survivability, thus you can come to a point where STR outweighs STA. INT should never be a factor in all of this since it's not the INT on the item that influences whether or not you want to equip it.

The increased survivability of the Blood DK does not come from the extra hitpoints the STA gives but more from the extra Health regain and Shield strength on Death Strike. This is a timed, returning increase in survivability which means that enough STA will make the DK invulnerable at which point the amount of damage done is moot.

So in the end it's a simple calculation of:
A. Health of the opponent
B. DPS of the opponent
C. Amount of DPS per point of STR
D. Amount of opponent DPS negated per point of STA

C reduces the length of the fight, A increases it.
D increases the allowable length of the fight, B decreases that.

As said; INT is never a factor here. You have to find the right value of STR and STA to get the toon to equip the correct items. If you have the right values and the toon still equips INT items then the bot is, simply stated, right.

In the end it's always the choice of the bot controller of course. My theoretical explanations are nice but I personally would never go through the trouble of doing the math since it'd give me a headache So if setting INT to -9000 solves the issue then by all means do that