RBM2 provides a powerful base for status bars. What does this actually mean? It can track your cooldowns, buffs, debuffs, and just about everything else you can think of. RBM2 currently has modules that provide similar information as NECB, DoTimer and other cooldown/spell tracks, but gives the power of customization to you.
RBM2 is extremely customizable, allowing you to change textures, locations, anchors, or you can just leave it at the defaults and it's ready to go. You have the ability to make any number of frames that you want, have bars travel from one frame to another depending on time remaining or percentage of time remaining, all with different styles. You can also setup sound events that will alert you when certain bars are almost over.
Additionally RBM2 has support for BossModules, and by default comes with a plugin that optionally converts BigWigs bars into the RBM2 system.
RBM2 is lightweight and unintrusive, it promises not to bog down your game.
there are several issues like bigwigs-bars, new trinkets and stuff, no forum whatsoever is active :(
would be a shame, rbm was an excellent mod :|
is there any problem with bigwigs and RBM2? I get errors like this:
[2009/05/17 01:16:03-2019-x1]: RBM2_BigWigs-2.0 r5564\BigWigs.lua:84: attempt to call method 'BarColor' (a nil value)
BigWigs_SSC-2.0\Hydross.lua:319: in function <Interface\AddOns\BigWigs_SSC\Hydross.lua:313>
<in C code>: ?
AceEvent-2.0-91091 (AtlasLootFu):298: in function `TriggerEvent'
AceEvent-2.0-91091 (AtlasLootFu):910: in function <...ddOns\AtlasLootFu\Libs\AceEvent-2.0\AceEvent-2.0.lua:903>
---
This stacks up xtimes with other errors from Bigwigs vs. RBM2. How can i fix it?
Any idea how I can get the spell back to the list? I want to use the addon with my warlock, and seeing the life tap buff is rather important with the new 3.1 glyph.
I'm in my last two weeks of this semester, and along with Ulduar coming out I haven't had might time to spend on RBM2 lately. ;(
My options for the debuffwatch and cooldownwatch is also different from the screenshot you have provided(the one titled "setting up DeBuffWatch"), it only has the enabled tickbox, nothing else.
Seems that having the Library part of Prat 3.0 addon(doesn't matter if you use alpha or release version of prat 3.0) enabled, checking the boxes doesn't work. Works fine otherwise.
Interface\AddOns\RBM2_CooldownWatch\Config.lua:37: attempt to index global 'icons' (a nil value)
Count: 19
Call Stack:
(tail call): ?
Interface\AddOns\RBM2_CooldownWatch\Config.lua:37: in function `member'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:247: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:195>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:997: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:979>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1601: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1432: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1412>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...ddOns\AckisRecipeList\libs\AceGUI-3.0\AceGUI-3.0.lua:304: in function `Fire'
...on\Libs\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:150: in function `SelectTab'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1547: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1432: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1412>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...ddOns\AckisRecipeList\libs\AceGUI-3.0\AceGUI-3.0.lua:304: in function `Fire'
...on\Libs\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:150: in function `SelectTab'
...on\Libs\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:79: in function <...on\Libs\AceGUI-3.0\widgets\AceGUIWidget-TabGroup.lua:77>
After the error comes, I can see the letters in the cooldowns section but nothing in the box below the letters.
De|Buff Watch2 -> Auras crashes WoW and I have to reboot computer.
Neither of these happen when I only run RBM2, but they are only activated by RBM2. I tried manually installing the newest version of all libraries used by RBM2, but both problems stayed. Is there something specific loaded when I click the Auras submenu? I could try disabling all the addons that use the same library as the one loaded by it and try to figure out the exact reason.
Still received one error message when messing around in the config; I was trying to setup a custom group "Debuffs" to show all debuffs on me, and at some point(I failed to notice when) I got the following:
Interface\AddOns\RBM2_Config\Config.lua:870: attempt to index field '?' (a nil value)
Count: 1
Call Stack:
(tail call): ?
Interface\AddOns\RBM2_Config\Config.lua:870: in function `member'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:247: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:195>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:369: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:342>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1039: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1035>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1511: in function `FeedGroup'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1432: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1412>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...ddOns\AckisRecipeList\libs\AceGUI-3.0\AceGUI-3.0.lua:305: in function `Fire'
...t\libs\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:458: in function `SetSelected'
...t\libs\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:93: in function <...t\libs\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:89>
Not sure if related, but the "Custom actions" of my "Debuffs" frame is empty, the "Long bars" and "short bars" show it normally. EU-servers going down soon so testing the exact point for the error tomorrow if needed.