Ive been considering getting a Vorpal Enchant, but in talking to a guildie
that has one on, their crit severity still shows at 75%.
I know with the shadow armor proc, it shows it going over 75%. Is this a
bug with the Vorp enchant? If not, I don't see the point of it.
Post edited by archomental on
0
Comments
soulwarrior78Member, Neverwinter Beta Users, Neverwinter Hero UsersPosts: 541Arc User
edited July 2013
It works just fine, it's just that it doesn't show in your character sheet. It's a small visual bug, but the crit multiplier is there. I have a perfect vorpal and I did many tests before and after I put my vorpal in place and I went through the results with the ACT parser and it was a noticeable difference even though my character sheet was never updated past 75%.
It definitely works in general and with all ranks of Vorpal enchant. Though it may not work with Tenebrous enchantments in your gear (don't know if they fixed that bug).
It even works with healing (not really relevant unless you're Renegade and even mildly interested in such things, ofc).
It definitely works in general and with all ranks of Vorpal enchant. Though it may not work with Tenebrous enchantments in your gear (don't know if they fixed that bug).
It even works with healing (not really relevant unless you're Renegade and even mildly interested in such things, ofc).
It works with Tenebrous. I suspect it was ninja fixed with that big Balance update patch when the game came out of beta. I have 7 Greater Tenebrous and all my skills are affected by the Perfect Vorpal. I took a chance and gambled, because I knew about that bug, but it turns out they had fixed it, just never announced it.
Comments
It even works with healing (not really relevant unless you're Renegade and even mildly interested in such things, ofc).
It works with Tenebrous. I suspect it was ninja fixed with that big Balance update patch when the game came out of beta. I have 7 Greater Tenebrous and all my skills are affected by the Perfect Vorpal. I took a chance and gambled, because I knew about that bug, but it turns out they had fixed it, just never announced it.