# Tankadin WeakAuras Strings: 5.1 update

Many of you noticed that a few of the elements of my WeakAuras setup broke with 5.1.  Blizzard made a change to the return values of UnitBuff, which was throwing off the Vengeance display.  And the Sacred Shield and Bastion of Glory indicators were intermittently breaking.  The Vengeance aura was pretty easy to fix, at which point I started trying to reproduce the SS/BoG bugs… and couldn’t.  After a few days of monitoring, I was stumped – either the error in the Vengeance text was also causing the SS/BoG errors, or else it was something far more subtle and hard to reproduce.

However, I got confirmation on twitter from Kelerei that he saw the same behavior once he fixed the Vengeance aura.  So at this point, I’m going to assume the SS/BoG bugs were indirect errors and are fixed (either that, or a new version of WeakAuras fixed them).

In the meantime, I’ve also made a few minor additions.  I frequently found myself wanting to know how long was left on the cooldown for Light’s Hammer, so I added cooldown trackers for all three L90 talents (in the same place as their “available” icon was, on the priority row).  I also added a cooldown icon/tracker for Devotion Aura to the “cooldowns” row.

Below are the updated strings.  I haven’t made a new video since not much has changed; if you want to see what they look like, check the YouTube video in the 5.0.5 post.

Priority Row:

Cooldown Row:

Again, if you have trouble importing, make sure you delete the first two empty lines that WordPress seems to insert for no apparent reason when you copy.

This entry was posted in Tanking, Theck's Pounding Headaches and tagged , , , , , , , . Bookmark the permalink.

### 15 Responses to Tankadin WeakAuras Strings: 5.1 update

1. Peregwyn says:

Thank you for posting your Weak Aura Strings. I do try to make some myself, but yours are great for me to start from or model for my other classes.

2. Kevin Ballard says:

Assuming the Vengeance aura was throwing lua errors, that would definitely have caused the intermittent failure of other auras. This is because the lua error interrupts WeakAura’s processing of a given event, so any other auras that should have been updated for that event (but were being processed after the Vengeance aura) would have been skipped.

• Kelerei says:

It was. (: Blizzard added an extra value to the UnitBuff() return value, which meant that the value we should have been reading for how much Vengeance we have shifted one position to the right. The value that the old trigger was reading was a boolean instead of an integer, and so it threw an “invalid cast” LUA error.

• Kevin Ballard says:

Sorry for the long delay…

Anyway, I’m familiar with the error. It seems Sunnier’s brewmaster weakauras strings used the exact same Vengeance aura, so I ran into the problem myself on the update. I wonder if there’s actually any benefit to your modification that uses GetSpellInfo() to fetch the name, instead of hardcoding it? I’m guessing there’s a possibility of localization issues without that? Although of course this is a bit off-topic. Anyway, a future-proof version of the aura would actually use local value = tonumber(select(15, UnitAura(“player”, vengeanceSpellName))) or 0 instead of the existing assignment. This would still break the vengeance aura if an update added yet another parameter, but it would avoid the lua error that stopped other auras from working.

3. Zaephod says:

Thank you, Theck, for these, I look forward to trying them when I get home. I’d been tweaking the breaking auras for a while trying to get them working, and adding some analogs to the ret strings. I also made a vengeance tracker aura that worked by just putting the value on its icon, not doing any digit reduction.

These auras have really helped me be better at managing my cooldowns, and I greatly appreciate them and all you do for the tankadin community.

/salute

4. Fumetsu says:

Thank you for this Theck! You inspired me to be a better tankadin : )
These strings are awesome!

These are amazing! Thanks, Theck.

6. sh420 says:

Oh buggery – just when I’d thought I’d finished messing about with wa….. Thank you Theck for this tho – totally invaluable for any (decent!) tank

7. Bajanu says:

Hello there!

I seem to have a problem with the strings. The game gives me this error: “No data for Avenger’s Shield 2″. Do you guys know what the problem might be?

• Theck says:

Haven’t seen that message, but a guess: did you have an aura called “Avenger’s Shield” before importing mine? If so it would rename one of them, which could break things.

8. Zai says:

Cannot even get it remotley to work, it completley crashes my whole weak auras. I just copy-paste the priority string, import, then clean the window and import the cd string?

• Theck says:

That should be all there is to it. You may need to delete some empty lines at the beginning after pasting if WeakAuras says it can’t understand the string – that’s an odd quirk of WordPress code boxes that I haven’t figured out how to suppress. I’ve never seen it crash WA, but I’ll test it again next time I log on.

9. John says:

I just found this and the setup is awesome! Thanks for doing the work. One request – I’m looking to also add a line to track the 15 seconds of increased block from the new 2-set bonus. Have you found a setup that includes that?

• Theck says:

No, because the last time I checked, the buff was hidden from the UI (i.e. for some reason, it’s bugged and isn’t granting a visible buff we can track).