@louis:
The problem with hit-cap is unfortunately a bit difficult to fix. It is because for simplicity i am assuming that difference between +1 stat and +0 is the same as the difference between -1 stat and +0. Some methods for a quick fix would be:
1) make it aware of any stat-caps and 0 the value if you are exceeding it
2) add a -1 value in addition to the +1 values
3) complete calculation for every item
Quote from lymphatik »
It tell me to use 2x [Runed Living Ruby] (they are red gem whereas corruptor only get yellow socket)
And by using Runed Living Ruby + Veiled Noble Topaz I get a better score, thanks to the socket bonuus.
You dont get the socket bonus with Runed Living Ruby + Veiled Noble Topaz, because like you already said that the item got only yellow sockets.
Im trying to look into you other described errors.
You can always set your profile to "Char" or "Class" instead of the global "Default", but setting the profile to char or class by default (at least for IV_DrD) would be useful. Though i couldn't commit the spell exist check yesterday.
@teedog
The "ItemValue-r43005\ItemValue.lua:796" error is fixed.
The "ItemValue-r43005\ItemValue.lua:1480" error shouldnt be possible at all, could you enable debugging and get me the chatframe output of an item that generates this error?
@Cold-Phoenix
Can't reproduce this error, looks like an invalid spellname or spellrank, what are you using?
0
I'll get some time tomorrow to fix those little other issues.
0
The problem with hit-cap is unfortunately a bit difficult to fix. It is because for simplicity i am assuming that difference between +1 stat and +0 is the same as the difference between -1 stat and +0. Some methods for a quick fix would be:
1) make it aware of any stat-caps and 0 the value if you are exceeding it
2) add a -1 value in addition to the +1 values
3) complete calculation for every item
You dont get the socket bonus with Runed Living Ruby + Veiled Noble Topaz, because like you already said that the item got only yellow sockets.
Im trying to look into you other described errors.
@shadd
Fixed.
0
ItemValue_DrDamage should now work properly with non-generic spelldamage, if not please give me the spellname.
0
0
0
The "ItemValue-r43005\ItemValue.lua:796" error is fixed.
The "ItemValue-r43005\ItemValue.lua:1480" error shouldnt be possible at all, could you enable debugging and get me the chatframe output of an item that generates this error?
@Cold-Phoenix
Can't reproduce this error, looks like an invalid spellname or spellrank, what are you using?
0
0
Sorting will be definitely possible soon.
@Astaldo
Just disable statpoints and weappoints, the group will add them together even if they are disabled.
0
0
0
Its at the moment not functionally but it will be in a few days with the multiple default jewels.
0
The main reason for the short command /iv is because /iv bj [link] (the new best jewels syntax) is just fast to type.
0
Edit: Optimized a bit
0
Just enter a spell name and the rank.
If you set Update Mode to "Saved Values" you can save your raidbuffed values f.e.
Note that all values are scaled based on the value of spelldamage (which always gets a value of 1).
Screenshot:
0