It is, but don't expect wonders - That jewel is bugged. It works correctly when socketed into weapons, or as last added socetable to armor (including helms/shields) but it won't work correctly when socketed into armor/helm/shield that already has % enhanced damage.KeNnY-DK said:I was doing some nm cows to lvl my merc and i noticed a lot of jewels dropping so i picked up one (usually never do) and it had 27% ED and 13 Max dmg on it.. now i was wondering would this be worth anything?
if you still have it, you should be able to get a couple handfuls of perfect gems for it. It's not high rune territory, but it's worth much more than the 4k gold you'd get for selling itKeNnY-DK said:thanks for the input.. i was only gonna save it if it was worth trading, but i dont need it myself so itll end up as charsi food
The +max/min and +%ed jewel will never work properly when socketed into armour. Thrugg does a great job of explaining it in this thread.helvete said:It is, but don't expect wonders - That jewel is bugged. It works correctly when socketed into weapons, or as last added socetable to armor (including helms/shields) but it won't work correctly when socketed into armor/helm/shield that already has % enhanced damage.
Thrugg said:An item with existing +min/max will cause the bug on any %ed added to it.
Pre-existing %ed is not effected the same way by adding +min/max though, even though future %ed then added after the +min/max will be bugged (but just the future added stuff, the original %ed will still work in full).
Think of it like +min/max adding a barrier that stops %ed of the matching type being added on. The reverse is not true.
So, for paladin shields the bug is not an issue, because they spawn with %ed but not +min/max. You would only see the bug if you added further %ed after adding +min/max, or an ed/max jewel (because with those the game annoyingly adds the +max first then the %ed afterwards).