SmartRes2

Res Bars settings

Co-ordinated Party and Raid Wipe Recovery, evolved

Features

  • An intelligent auto res key. Press the button and start ressing based certain criteria. See the Q & A
  • No more "unknown" or blank target names when you click on a corpse with the cursor to res
  • Random resurrection messages to chat. This can be disabled
  • Highly configurable res bars. Move, change the texture, and more
  • Disables itself during combat, saving resources
  • Detects Revive, Resurrection, Ancestral Spirit, and Redemption, and shows you who is casting on whom
  • Optional support for Rebirth, the Druid in-combat res spell
  • Any character class can use SmartRes2 to see the res bars. However, only ressers have keybindings to cast
  • Uses the Interface... AddOns configuration screen
  • Plugs into any LibDataBroker-1.1 display
  • Smaller, lighter, and more responsive than the original SmartRes
  • Fully compatible with any LibResComm-1.0 using addon, including HealInc and oRA3
  • Backwards compatible with the original SmartRes and oRA2
  • Optionally inform another resser they are casting a duplicate res spell on a player being ressed or waiting to accept

There's still more! But you have to use SmartRes2 to find out about the other features!!

Official forum thread

Ticket Tracker

Questions and Answers

Q: How do I get to the options?

A: The slash commands are /sr or /smartres; you can also do /sr cast or /smartres cast for you macro lovers. There is an LDB launcher and you can use the Interface/Addons panel as well.

Q: Why rewrite the original SmartRes?

A: The original SmartRes has been around a long time. It uses outdated libraries that aren't being patched anymore; the code is a confusing mess; Blizzard introduced some nice APIs that made things easier; Ace3 and libraries that are Ace3 compatible are smaller, more lightweight, and use less CPU and memory; SmartRes had become buggy (wasn't disabling itself in combat, non-ressers couldn't see the res bars, occasionally conflicted with oRA2, and other miscellaneous faults and irritants)

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

A: For several reasons, chiefly but not limited to

  • 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 ressed, in range, and visable plus resses in the following, intelligent order
  1. Priests
  2. Paladins
  3. Druids and Shamans
  4. other Mana using classes
  5. everybody else

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: You said in the Known Issues that the Blizzard events don't accurately return a target, but the original SmartRes does. Um, what?

A: Actually, the original SmartRes fakes it, sometimes with the wrong information. While it is possible to be accurate about your own target, getting other players targets is not; the original SmartRes guessed for other players. SmartRes2 is 100% accurate, because it is only concerned with you, the player. To see other players' casts, they need LibResComm-1.0 or an addon that uses LRC.

Q: How do I get more textures for the bars?

A: SharedMedia and SharedMedia-Blizzard

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

A: YES!! Go here and help contribute. You even get credit directly in the addon!!

Known Issues

  1. There is a bug in Blizzard's code that sometimes prevents addons from opening straight to their category. 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. The UNIT_SPELLCAST_xxx Blizzard events return a caster, but not an accurate target for other players than yourself. If players in your group do not have LibResComm-1.0 or an addon that uses that lib, you will not see their bars. A list of LRC-1.0 compatible addons can be found here.
  3. In the current Alpha, SmartRes2 keeps trying to res the same target until they accept the resurrection. This should be fixed soon.

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.

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

  • 9 comments
  • Avatar of myrroddin myrroddin Thu, 21 Jan 2010 12:14:06

    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 joshwill80 joshwill80 Thu, 21 Jan 2010 09:56:37

    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 Wed, 20 Jan 2010 05:42:23

    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 Thu, 14 Jan 2010 00:10:25

    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.

  • Avatar of angel100780 angel100780 Wed, 13 Jan 2010 12:57:21

    I tried it out but there is one thing im missing. A field in wich i can write my one personal rezz message. There is a possibility to put random message on but none to write one personal down wich is can use if i like permanently for any chanel or so. Is it possible to add something like that?

    Last edited on 13 Jan 2010 by angel100780
  • Avatar of myrroddin myrroddin Tue, 12 Jan 2010 04:40:06

    Oh, in that case...

  • Avatar of joshwill80 joshwill80 Mon, 11 Jan 2010 15:47:43

    I did not mean turning the addon off all together. I still want to be able to res with the key bindings and announce it, I just don't want to see any res bars. The original SmartRes had an option to enable/disable just the bars, was hoping to see it makes it's way into SmartRes2 also.

  • Avatar of myrroddin myrroddin Mon, 11 Jan 2010 06:03:25

    Thank you for letting me know about the bars not staying in place. I'll work on that during the week, when I'm not sick.

    Completely hiding the bars, as in turning the addon off altogether? I can do that; just let me fix the code first for the stuff currently "not working as intended."

  • Avatar of joshwill80 joshwill80 Sun, 10 Jan 2010 04:21:40

    Hello,

    Tested r61 out and I noticed there is no option to completely hide the bars. Would like to see that option, as I just don't need them on my screen.

    Also a small bug report, the bars would not stay where I positioned them. When reloading the UI, they kept defaulting back to the middle of the screen.

    Great addon, looking forward to using when it gets an official release.

  • 9 comments

How to notify people who res the same target as someone else

  1. clickable collision bars that spam whispers to the silly player:

  2. toggleable spam whispers:

  3. announce to Party, Raid or other channel (more spam) about the silly player:

  4. blacklist the offending resser so they never get resses:

  5. create a list of bad ressers and send it to the Party/Raid leader:

  6. some combination(s) of the above:

  7. other:

  1. Results
  2. 5 comments

Facts

Date created
09 Jul 2009
Categories
Last update
03 Feb 2010
Development stage
Alpha
Language
  • deDE
  • enUS
  • esES
  • esMX
  • frFR
  • koKR
  • ruRU
  • zhCN
  • zhTW
License
All Rights Reserved
Recent files
  • A: r81 for 3.3.0 on 03 Feb 2010
  • A: r80 for 3.3.0 on 03 Feb 2010
  • A: r79 for 3.3.0 on 01 Feb 2010
  • A: r78 for 3.3.0 on 21 Jan 2010
  • A: r77 for 3.3.0 on 21 Jan 2010

Authors