SmartRes2
SmartRes2 Core
Resurrection monitor, one-button "smart" resurrections, funny random messages, and so much more!
Added with this build: a minimap button for options, and mult-spec Profiles.
Legion and Beyond
This is the 100% rewritten version for Legion and beyond. SmartRes2 is now modular, thus most of the functionality has been transferred to seperate modules. This means that it gains in power and capabilities, while also becoming even lighter on CPU and memory.
Modules
- Chat - All the self notification, funny random messages, and other chat stuff from the previous SmartRes2 builds. There is a lot more packed in here than ever before!
- Smart - Coming soon. The one button resurrection options that pick the best candidate to resurrect. The new module will prioritize roles (healer > tank > dps) rather than classes.
- Bars - Coming soon. The visual bars in pre-Legion no longer work in Legion, and needed to be rewritten. There are plans to add features to this, like themes.
Localization
Want to help translate? Then click here and localize SmartRes2 into your language. Most of the phrases you'd expect to find are in the modules, so check those out for more translating.
Bugs or Suggestions
Found something wrong, or thought of an improvement? Great, then I want to hear from you!
Aoife, reset the profile to default settings, or delete your saved variables, and tell me if it is still happening.
Just asking because it works correctly for me.
Notes: I will not be adding support for Engineering res devices unless they are added to LibResComm-1.0 ... Also, I looked at LibBars-1.0 and did not see any way to make the bars clickable. Suggestions based on those will not be implemented, sorry.
Finally!!! No errors in game, tried no-lib and embedded. Everything works afaik.
Snarl, grip, bitch, moan, etc. Testing something, and maybe Torhal is on to something about the escape codes.
I flagged ticket 43 missing translation as invalid, as the line numbers referenced have been changed, along with the translation key. I am trying to rebuild the localization for the bugged one from scratch.
Still getting the following errors
1x AceLocale-3.0: SmartRes2: Missing entry for 'Add messages to the random message output table.: Usage: %%p%% (optional) for yourself, %%t%% (manatory) for your target.: They can be in any order.': SmartRes2-r121\SmartRes2.lua:415: in function <SmartRes2\SmartRes2.lua:102> (tail call): ?: <in C code>: ? <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5> (tail call): ?: AceAddon-3.0-5:510: in function `InitializeAddon' AceAddon-3.0-5:622: in function <...s\AckisRecipeList\libs\AceAddon-3.0\AceAddon-3.0.lua:615>
Very strange. That translation is added, and still throws a missing. I'm asking Torhal for help on it, as I don't know why it doesn't work.
What I want to know is with a no-lib install, is anyone getting an error, and the multiselect folder is not installing correctly with the Curse Client? If so, I may need to hard-embed it until the addon DB gets updated.
Probably because I was silly, and added the translation AFTER the commit, and so r119 did not pick up the line.
I'm about to commit r120 which *should* be final before the next beta. I can hope, anyway.
Yes, the below error happens consistently 100% of the time at logon with r119.
1x AceLocale-3.0: SmartRes2: Missing entry for 'Add messages to the random message output table.: Usage: %%p%% (optional) for yourself, %%t%% (manatory) for your target.: They can be in any order.': SmartRes2-r119\SmartRes2.lua:441: in function <SmartRes2\SmartRes2.lua:129> (tail call): ?: <in C code>: ? <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5> (tail call): ?: AceAddon-3.0-5 (Ace3):510: in function `InitializeAddon' AceAddon-3.0-5 (Ace3):622: in function <Ace3\AceAddon-3.0\AceAddon-3.0.lua:615>
on latest build
Showed the anchor and dragged it back to the center of the screen, but resing or starting the test bars snaps it back to the top-right corner again.
I downgraded to solve my immediate problem and I just upgraded to r116 - I am glad to report that the problem is gone for me.