[5.2] Release 5.5.0 Test Bars

Co-ordinated Party and Raid Wipe Recovery, Evolved

September 25, 2014

All files committed to the repository, starting with r314, will only work with Warlords of Draenor. Due to changes in Blizzard's API, r314 onward will not be backwards compatible with Mists of Pandaria. The link to the WoD alpha builds are found via WowAce or WowInterface, and are slightly different than the release links.

Official Forum Thread

Official Forum Thread

Use your Curse user name and password

Bugs and Suggestions

These go here on the project page. Bugs especially, as they spam the comment section. It would be especially awesome if, when reporting bugs, you had BugGrabber and BugSack, or Swatter (part of Auctioneer).


People can send me donations if they so choose. Every little bit helps pay for my World of Warcraft subscription. Send whatever you can or want, but do not feel obligated.

  • PayPal: [email protected]
  • Pledgie:

New Features

  • Bars will now show up for people who have been resurrected, but not accepted the cast. These are new bars, unlocked by default. You can lock them via the SmartRes2 Options in the new tab.
  • SmartRes2 made the switch from LibResComm to LibResInfo, which means no longer forcing everybody to use LRC/SR2/CTRA –– data is pulled from the Combat Log instead.
  • A message will be printed for yourself when someone's resurrection cast has expired and they can be raised again.
  • Using the Mass Resurrection Key will not cast Mass Resurrection if someone else's cast will end before yours.
  • The Mass Resurrection Key verifies other players can be Mass Resurrected, and will tell you if there are people that can't (ie: have the RECENTLY_MASS_RESURRECTED debuff).
  • You have the option to use a Mass Resurrection message.
  • Mass Resurrection has its own coloured bar and text
  • Every spell and item that can be used to raise dead players is supported, even instant cast ones. Please be aware that instant cast spells are instant, and as such have bars that fire and end faster than you can see. Further, Engineering devices do not guarantee success with their use.
  • SmartRes2 does not guess at other players's casts or item use anymore. It knows, it knows....
  • Try the new Test Bars. They now have 100% extra cool and funky! /sr test or /smartres test

Bug Fixes include, but are not limited to:

  • The Auto Res Key works again
  • Mass Resurrection Key is hidden if you do not know Mass Resurrection
  • Macro commands work (see below for examples) and they are Smart
  • Custom and Random Messages no longer have obtuse or confusing syntax (mouse over the fields to see new instructions)
  • Users will not lose existing Random Messages –– they have been converted internally to the new syntax. However, if you used the Custom Message, that has been reset out of forced necessity
  • Bars are correctly locked into place regardless of enabling or disabling SmartRes2
  • Fixed chat output, including supporting Instance
  • Hopefully fixed user settings for bar height, width, and scale

Example Smart Macros

These duplicate the functionality of the Auto Res Key and Mass Resurrection Key, respectively. Rename Resurrection in the first macro according to your class spell (Ancestral Spirit, Resuscitate, etc).

Class spell macro (Priest)
#showtooltip Resurrection
/click SmartRes2Button
Guild Perk Mass Resurrection
#showtooltip Mass Resurrection
/click SR2MassResButton


  • Intelligent resurrections. See the Q & A
  • Random messages to chat
  • Add or remove your own random messages
  • Three coloured bars. Green means one caster, one target. Red means more than one caster on same target. Blue is when someone has been ressed, but has not yet accepted the res, and a caster tries to res again. The colours are changeable
  • Set the maximum amount of displayed bars
  • Notify in chat when someone is casting a collision (red bar)
  • SmartRes2 supports viewing Mass Resurrection casts
  • All known spells and devices that can resurrect are detected, including Engineering devices. As far as I know, this is the only res monitor to, well, monitor those devices.
  • No more "unknown" or blank target names when you click on a corpse with the cursor to res
  • Highly configurable res bars. Move, change the texture, recolour, alter scale, height, and width, plus more
  • Disables itself during combat, saving resources (unless you have Rebirth detection on)
  • Shows you who is casting on whom and how long it will take to land
  • Optionally show bars in combat for spells that can resurrect in combat (instant cast spells will show and hide far too fast for you to see)
  • Any character class can use SmartRes2 to see the res bars. However, only ressers have keybindings to cast
  • Backwards compatible with all other resurrection monitors

Questions and Answers

Q: How do I get to the options?

A: The slash commands are /sr or /smartres There is an LDB launcher and you can use the Interface/Addons panel as well.

Q: What do the different coloured bars mean?

A: Green bars are good resses; they aren't duplicates or collisions with other healers' casts. Red bars occur when a healer casts on a target already being resurrected by someone else, whose cast will land sooner. Blue bars happen when a healer tries to res a target who has been resurrected, and has not accepted the first res. The colours are user changeable.

Q: Why SmartRes2, and not a simple macro for ressing?

A: For several reasons, chiefly but not limited to

  • The smart macros listed above are smarter than any basic macro, and have all the SmartRes2 features
  • Because macros cannot tell you the name of released (ghost) characters, and SmartRes2 can
  • Macros cannot tell you how long it will take for the res to land on the target, and keep track ticking down
  • SmartRes2 shows you the other out of combat resses being cast by the rest of your Party or Raid
  • SmartRes2 has an auto res key, which when pressed, resses characters not already being resurrected, in range, and visible plus resses in the following, intelligent order
  1. Healing classes (Priests, Monks, Paladins, Shamans, Druids)
  2. Mages and Warlocks because they consume Mana after being resurrected to summon pets, buff, etc
  3. Death Knights and Warriors (hey, need some tanking classes just in case)
  4. Rogues and Hunters

Q: How come the auto res and manual res keys don't do anything for battle resses? They aren't working!

A: There are no keybindings for battle resses, and there never will be. Think of it like this: the main tank dies, but you also have a dead Shadow Priest. If I turned on the keybindings during combat, SmartRes2 would always res the Shadow Priest. It is better to pick your res target during combat. The bars are only there to show you which Druid is casting on which target, that's all.

Q: How do I get more textures, borders, and fonts for the bars?

A: Sharedmedia and SharedMedia-Blizzard and SharedMediaAdditionalFonts and SharedMedia: Renaitre and NEW SharedMedia_ClassicalFonts

All links updated and verified as of May 29, 2013.

Q: What? US English?? But I understand other languages. Can I help?

A: YES!! Go here and help contribute. Need Italian please!!

Known Issues

  1. There is a bug in Blizzard's code that sometimes prevents addons from opening straight to their category in the Interface.. Addons pane. Not all users are affected, and there is no fix within the addon itself. However, if you sometimes get SmartRes2 to open properly when typing /sr or /smartres or clicking the LDB launcher, and sometimes it doesn't open properly, you can install this addon which will fix the issue. Do not install this addon unless you are affected by the bug!
  2. Warcraft does not allow you to cast on targets whom are out of Line of Sight. If you cannot resurrect someone, then move until you can. There is no way to detect if a target is in Line of Sight; a target either is, or isn't.
  3. If a target dies and gets resurrected rapidly in a short amount of time, it delays their Accept button for resurrection casts. There is no way to detect what another player's delay timer is, and in some cases you will see a message saying that their timer has expired, they can be raised again, yet their Accept button has only not lit up. This is an edge case, as most players will not die that rapidly unless they are doing it on purpose (fall testing, for example).
  4. The Combat Log has a very long range, but is limited to within the same instance. If someone begins casting while you are outside of the instance, you will not see bars, nor will you see them if you zone into the instance mid-cast.


SmartRes2 is a complete rewrite of SmartRes by Maia, Kyahx, Poull, and Myrroddin. This new version is fully Ace3, supporting new, updated libraries and new Blizzard APIs. Many people have contributed or helped test SmartRes2, and I thank each and every one of you!

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of xevilgrin xevilgrin Mar 14, 2010 at 12:54 UTC - 0 likes

    thx for let me knowing about this

    hmmmmmmm... dunno( i have no clue about programming ;-) ) just an idea.... maybe the de/de client just doesn't support %s rather than %p /%t !?!

    cheerz from Germany


    evil regards

    <..... EvilGrin .....>

  • Avatar of myrroddin myrroddin Mar 14, 2010 at 10:25 UTC - 0 likes

    xevilgrin, I haven't been able to duplicate your ticket, as it works correctly for me in enUS. I'm still checking.

    Just wanted to give you an update.

    Oh, and ckeurk, thank you for fixing lots of the frFR. :)

  • Avatar of xevilgrin xevilgrin Mar 13, 2010 at 07:57 UTC - 0 likes


    if you're able to tell myrroddin that the french translation is horrible ;-) so it seems like your able to understand french and this is quite perfect cauz he doesn't (just as me) ...and heres the workaround!!! ... feel free to correct it via the translation tool right up here at the menu topbar under the button localization...

    i guess a "cool" way to show "respect" to the author

    Last edited Mar 13, 2010 by xevilgrin
  • Avatar of PodVibe PodVibe Mar 07, 2010 at 08:49 UTC - 0 likes

    No myrroddin, I rectify problem ;)


  • Avatar of myrroddin myrroddin Mar 07, 2010 at 02:28 UTC - 0 likes

    ckeurk the only way to stop his translations is to delete his translations. Would you like me to do so?

  • Avatar of PodVibe PodVibe Mar 06, 2010 at 11:53 UTC - 0 likes

    translation by mattbnr (french) is really not good at all
    please stop

  • Avatar of myrroddin myrroddin Jan 21, 2010 at 12:14 UTC - 0 likes

    If there are bugs in the original SmartRes, I will not be fixing them, as SmartRes2 is very close to its first Beta version.

    The two addons use different versions of Ace to create keybindings. SR uses Ace2 with DewDropLib for the dropdown menus, and SR2 uses Ace3. I can force SR2 to clear any bindings before it binds new ones, but that seems unnecessary, as it defaults to having no keybindings until the user sets them, and they are parented to the frame "SmartRes2Button". I am quite certain the the main UI will warn you if you try to set a key or key combos that are already bound, stating that the key or combo is already in use. That may be true only for Blizz keybindings; I will double check in game.

  • Avatar of Daemys Daemys Jan 21, 2010 at 09:56 UTC - 0 likes

    I'm using the original SmartRes until this one at least goes beta. The auto res key in the original seems to only work sometimes for me, other times it is completely broken and does not even give chat feedback. Reloading the UI sometimes fixes it.

    I was wondering if the problem might be because of the way SmartRes and SmartRes2 uses keybindings. Wouldn't it work better if you added a SmartRes2 section to the default Blizz keybindings, the way other addons do, instead of setting the keybindings in the interface options? The current way of setting keybindings in SmartRes does not unbind already used keys, which could cause conflicts I would think.

  • Avatar of psychohamster psychohamster Jan 20, 2010 at 05:42 UTC - 0 likes

    I've found the error for random messages and found a fix for you.

    line #697 should read msg = self.db.profile.randChatTbl[math.random(#self.db.profile.randChatTbl)]

    and your table should look like this

    randChatTbl = { this is here for eventual support for users to add or remove their own random messages "%%p%% is bringing %%t%% back to life!", "%%p%% performs a series of lewd acts on %%t%%'s still warm corpse." }

    of course with a lot more messages added in

    But with these changes I have random messages working great. (Basically you were referencing a random number from the index rather than the table itself.

  • Avatar of myrroddin myrroddin Jan 14, 2010 at 00:10 UTC - 0 likes

    I will be adding the ability to create your own res message, but I want to get what is in there working first.

    I am aware the random messages are printing their table number rather than the message itself; I am looking into that.