Co-ordinated Party and Raid Wipe Recovery, Evolved
IMPORTANT NEWS!
- The latest alpha build of SmartRes2 removed the macro command for public use. It is still in the code, but only for developers. It will stay that way until a fix is found as to why the command is not working.
- The latest alpha supports Brazilian Portuguese, or at least as much that has been translated as of this writing.
- Feel free to try out the latest alpha at this link, but be warned, it may not work correctly. If you find bugs, please report them in the tracker, which is linked below!! DO NOT report bugs into the comment section. Thank you.
- UPDATED: Mass Resurrection guild perk has been rewritten in the r200 alpha build. It may be buggy, as I can't test it. There is an open ticket already if you have bugs to report.
What's Changed From the Original SmartRes
- Intelligent resurrections. The original picked dead characters at random. See the Q & A
- NEW: Written with Ace3 rather than Ace2, SmartRes2 is faster, lighter, and more responsive than the original. This also ensures longevity for the code
- NEW: Random messages to chat
- NEW: Add or remove your own random messages
- NEW: 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
- NEW: Set the maximum amount of displayed bars
- NEW: Notify in chat when someone is casting a collision (red bar)
- NEW: on 4.x clients, SmartRes2 supports viewing Mass Resurrection casts
- NEW: Non-CTRA spells are detected, including Engineering devices. As far as I know, this is the only res monitor to, well, monitor those devices. The Guessed Resses covers both Engineering devices and casters without a res monitor addon
- NEW: Uses the Interface.. Addons pane for the options. Also has a LibDataBroker plugin
Features
- 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)
- 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
- Smaller, lighter, and more responsive than the original SmartRes
- Detects all forms of resurrection spells
- Backwards compatible with oRA2, SmartRes, CTRA, and all other resurrection monitors
Official Forum Thread
Bugs and Suggestions
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 ressed by someone else, whose cast will land sooner. Blue bars happen when a healer tries to res a target who has been ressed, and has not accepted the first res. The colours are user changeable.
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
- Priests
- Paladins
- Druids and Shamans
- Mages and Warlocks
- 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: Why don't you support Raise Ally, the Death Knight spell?
A: Because it is an instant cast spell, and thus, there is no point to having it in an addon that shows bars.
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 when dealing with you the player or someone using LibResComm-1.0. The feature to see other players' casts who do not have LibResComm is on by default (guessed resses) but can be toggled off.
Q: How do I get more textures, borders, and fonts for the bars?
A: Sharedmedia and SharedMedia-Blizzard and SharedMediaAdditionalFonts and SharedMedia: Renaitre
All links updated and verified as of December 9, 2011.
Q: What? US English?? But I understand other languages. Can I help?
A: YES!! Go here and help contribute.
Known Issues
- 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!
- 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 see their bars, but their target may or may not be accurate. A list of LRC-1.0 compatible addons can be found here.
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.
Facts
- Date created
- Jul 09, 2009
- Categories
- Last update
- Dec 13, 2011
- Development stage
- Release
- Language
- deDE
- enUS
- esES
- esMX
- frFR
- koKR
- ptBR
- ruRU
- zhCN
- zhTW
- License
- All Rights Reserved
- Curse link
- SmartRes2
- Downloads
- 233,171
- Recent files
- A: r202 for 4.3 Dec 13, 2011
- A: r201 for 4.3 Dec 13, 2011
- A: r200 for 4.3 Dec 13, 2011
- A: r199 for 4.3 Dec 09, 2011
- R: Release 1.3.1 for 4.2 Dec 02, 2011
Relationships
- Tool used
- LibDataBroker-1.1
- Embedded library
- Ace3
- AceGUI-3.0-SharedMediaWidgets
- CallbackHandler-1.0
- LibAboutPanel
- LibBars-1.0
- LibResComm-1.0
- LibSharedMedia-3.0
- LibStub
- Reply
- #61
Aoife Jul 01, 2011 at 11:03 UTC - 0 likes@tednik: Go
yes, i replaced that file with the revision - no more error! :) Thanks!
~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
Aoife
Divine Alliance of Mok'Nathal
- Reply
- #60
tednik Jul 01, 2011 at 07:26 UTC - 0 likeshttp://www.wowace.com/addons/librescomm-1-0/files/57-r79/
REVISON 79 removes the error
- Reply
- #59
Aoife Jun 30, 2011 at 12:28 UTC - 0 likesIn 4.2.0, error on log in is being generated by this addon because of an error with LibResComm-1.0 (where a ticket has been opened).
- Reply
- #58
myrroddin Feb 06, 2011 at 04:11 UTC - 0 likesAkmaud, I read your ticket, and declined, with an explanation. You can read the particulars here.
- Reply
- #57
joshwill80 Dec 26, 2010 at 04:03 UTC - 0 likesI have only had a very small amount of time to test it, but it seems that the alpha has fixed the errors. Thanks!
- Reply
- #56
myrroddin Dec 24, 2010 at 00:29 UTC - 0 likesDoes the latest alpha fix your issues, Josh?
- Reply
- #55
myrroddin Dec 22, 2010 at 23:52 UTC - 0 likesYep, it is Google Chrome displaying the code as one big long line, rather than nicely formatted.
- Reply
- #54
joshwill80 Dec 19, 2010 at 21:36 UTC - 0 likesHm, it is from BugGrabber. I pasted it as code on here. Perhaps your browser is not displaying it correctly? Anyway, I will make a ticket and just paste the errors as text.
- Reply
- #53
myrroddin Dec 19, 2010 at 01:22 UTC - 0 likesJosh, it is great you posted the error, but the format is useless to me. Please install BugGrabber and BugSack or Swatter, capture the error, and post it into the ticket tracker.
- Reply
- #52
joshwill80 Dec 15, 2010 at 03:29 UTC - 0 likesSmartRes2 spams me with errors, sometimes when I res, and others times when other people do. I'm wondering if it is because I have the res bars hidden. Anyway, the exact errors: