Skip to Content
2-02-2012 @ 4:11PM
That doesn't make sense though, cause Vengeance shouldn't have anything to do with Seal of Truth proccing like crazy (and by crazy, I mean several hundred procs per second). That was the main source of the crazy dps. I can understand if some ret paladins using Devo aura suddenly stacking Vengeance for damage taken due to a bug and ALL their abilities doing more damage due to the AP buff, but this is different. Unless getting Vengeance somehow procced SoT each time the Vengeance stack changed (which in itself is ridiculous), I don't see how they intertwine.
2-02-2012 @ 4:17PM
Didn't they put a new bench in Stormwind once and it ended up bugging the Illidan fight in Outland? (This may be an urban legend, but I always thought it was kind of funny.) Flap your wings, little butterfly . . . . .
What it looks like in the combat logs is that the damage caused by Seals of Command, which is procced by Seal of Truth, was then instantly proccing Seal of Truth again, over and over and over. Their vengeance fix accidentally changed how Command damage was treated by the proc system.
2-02-2012 @ 4:31PM
They didn't say vengance did it. They said the coding was part of a the fix to vengance. As far as I know ret Pally don't get vengance only Tanks do. The coding was for the Pally in general and somehow it affected the Seal of Truth Proc that all Pallys get.I just wish i had switch to ret spec for a bit last night. I almost always play solely as prot.
2-02-2012 @ 4:37PM
Recursion error maybe ?
2-02-2012 @ 5:00PM
A guy I knew once updated his sound card drivers and lost his Internet connection. Sometimes wires just get crossed in odd ways.
2-02-2012 @ 5:12PM
I don't believe its that farfetched of a connection. The code for figuring out when to trigger the extra damage from Seals of Command and when to apply Vengeance to tanks is likely similar in implementation, as they both trigger ("Proc") off certain events. That certain events can still trigger Vengeance even if an exception for player-generated trigger events is in place indicates that the code behind such must be very clunky indeed.Better their developers have to look through that mess of code then me.
2-02-2012 @ 7:18PM
"Better their developers have to look through that mess of code then me."Amen to that!I don't know how many times I have thought "Oh, that bug has absolutely nothing to do with my small fix to the code as it is totally unrelated." only to be proved totally wrong after a lengthy session of debugging. One small fix here affects a part there, which turns a flag up at some other part, which in turn... and finally it causes the bug in some _totally_ unrelated place.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.