Archive for the 'raidleading' Category

Addon of the week: RaidBuffStatus

First off: I wondered why I didn’t get one disconnect in the 2 raids I did yesterday.  For the past few weeks this has been the standard I was getting used to (ok, not really).

I was always blaming my addon mania for this, as I figured a few of them were probably fighting over who got to place their useless information in some unread tooltip first.

But this morning I got the joyful message from my internet provider that they secretly upped my internet speed!

Now, I can hardly believe that the lack of speed was causing the problems before (8Mbit should be more than enough, right?), but I wouldn’t be surprised if those sudden DC’s were caused by them tweaking their routers.

Still, I’m keeping my fingers crossed. It could just be temporary luck and my addons could still be plotting a huge chain-DC on my next run, right after I see the message: “Mainspecs, roll on [Trauma]“.

However, a faster internet connection for the same price is never a bad thing 🙂

And I think I already payed my due’s to murphy.. because to be absolutely safe, I decided to updated my router firmware as they suggested. Having my router protected as good as possible, this caused some undocumented updating problems: my password got reset, which not only caused me to not be able to access my router, and internet until I figured out how to reset it to factory default. It also resulted in me losing all the configurations which I meticulously tweaked over time. It took me 2 hours to get everything back as it was *sigh*

But I’m back in business, like everyone’s favorite VH boss would say.

Anyway, enough screen clutter, on to the addon of the week:


This addon came to replace my previously used BigBrother a while back, and it’s a must have if you’re perfectionist like me.

Unlike the name suggests, this addon does more than just check the status of buffs in the raid. However, that is one of its main purposes.

Who would want it?

Raidleaders mostly of course, but anyone with a sense of responsibility will like it very much. For tanks this can also be very useful. Even in PvP this is useful for the deathwarnings and the CC breaks.

Why would you want it?

To “spy” on everyone and quickly notice if they ate their plate clean, took their (right) medication.. I mean, have their (correct) food buffs and flasks/elixirs, buffs, aura’s, presences, or stances, but also who’s been slacking in giving the rest buffs (yes, I’m looking at you, slackadins!) and who is n0t even inside the instance yet even (regular slackers).

These are not it’s only functions.

For tanks it has the special function of showing interesting information about taunts used, and breaking CC’s. It can give text and sound feedback when your taunt fails, or when someone else taunts your target. When someone else taunts your target, it also recognizes if this is a tank or a non-tank. For example: if a hunter grabs your aggro, it will explicitly mention that it’s not a tank that taunted your target.

The options for taunt warnings are many, like you can see in this configuration screen, there’s not a single kind of taunt not covered. It’s close to too much information, but you can choose what you wanna see and what not, that’s the good thing.

For those that aren’t raidleading or tanking, it’s still useful besides spying on others. It can be configured just to show your buffs, and helps you buffing the right people by simple clicking your buffs in the main overview. CC breaks are also good to know if you’re a CC capable class. If you’re a dps druid it’s also interesting to get deathwarnings too, so you can quickly battleress f.e.

The operation

The main overview screen looks like this if you’ve got it full option:

This page shows the overview of all the information you can get about the current raid. It might look confusing, but once you know the reason for the way this is ordered, it’s get much easier to use.

The screen is split into 4 parts.

First part, the top row of buttons shows basic “readiness” problems, like people not in the same zone, people AFK, low durability, having useless aura’s, people using low level consumables or ammo, or people who are dead… Personally I think 2 things in this list don’t really belong there, but you can all change that.

The second part is a list of bars that show the health of the raid. Average health of tanks, average mana of healers, etc. Personally I only care about healer mana, and healers/tanks alive, but you can choose what you want to see from the configuration menu.

The third part is a grid of all the standard buffs, kings, mark ot wild, fortitude, seals, presences, etc.

The fourth and last part are the buffs that you would use for progression raids, and are interesting if you really want the best from your raid. These are basically consumable buffs like foodbuffs, elixirs/flasks, stuff you wouldn’t use in heroics f.e.

The buffs have colors on them, these colors say something important about the buffs too:

  • Yellow means that somebody in the raid is missing this buff
  • Red means that somebody in the raid is missing a buff you’re responsible for
  • Blue means that you’re missing a buff that someone else is (or could be) responsible for.

You can configure click actions on these buttons. By default they are this:

  • Left click turns checking for the particular buff on and off
  • Right click buffs people if you’re capable of buffing it
  • Shift-Left click reports this to the raid chat (if you’ve got the authority to do so)
  • Ctrl-Left click whispers the buffers about what they forgot.

There are also 4 buttons. The scan button on top refreshes everything, nothing spectacular. The bottom 3 buttons are only usable if you have raidleader or assist status, and can be used to report to the raid about the missing buffs (if you don’t have this status, it can report to yourself only, but that’s a bit senseless, as you have the overview in front of you). The Trash and Boss button do basically the same, except that the Trash button ignores the fourth part of buffs. The Boss button shows everything. The R button is simply a readycheck.

Sometimes it’s a shame that it only allows you to report to the raid as leader/assist, especially in pugs. You can however always make it whisper to the responsible people what they’re forgot to do.


I forgot two windows that pop up if you press the little two arrows on top of the addon.

The left one gives an overview of your group, showing what specs and abilities the players have. Very useful to quickly see who are the tanks, healers, melee, and ranged dps, and what they bring to the raid in abilities.

The right one let’s you configure which buffs you consider a buff, or a warning, and which ones you want to show, or report. This basically configures the RBS display. Here you can change the buffs that you think are wrongly placed, or are just not interesting to you. Those slacking buffs that were wrongly placed in my opinion can be replaced or removed here.

The options

The latest versions comes pre-configured for three options. Just press the button and the configuration will be adjusted to your role:

Personally I would’ve liked to see the “tank” option too. but it’s not hard to configure that manually.

Manual configuration is simple btw, even though there are lots of options.

Consumable options configures whether you’re ok with lower level consumables or not.

Reporting configures to whom you want to report the information, and how.

Raid Status Bars show what bars you want so see in the bars overview.

Mouse buttons configures the click combinations you can use

Tank/CC/Misdirect/Death Warnings (see pictures at the begin of this post) configure if you want these warnings, and if they should be audial, visual, both or even reported to the raid.

Food announce can automatically throw a raidwarning when a fishfeast or any other interesting buff source is dropped. You can configure it to whisper people when these items are about to time out too if they still haven’t used this. I like this option a lot, because especially fish-feasts are easy to miss.

The other options are quite self-explanatory or just small operational options.

…And finally

I think it’s a very useful tool. As tank I love the taunt warnings, the misdirect/cc warnings. Simple functions like who is still not in the zone is great for summoning people to their raid, you don’t need to have them all ask for it.

The authors claim it’s lightweight, but it’s still a pretty big addon (1.2 MB). Processor usage seems to be low though, and that’s most important with wow being such a CPU hungry game.

Oh, I haven’t tested this yet, but if you would like to be able to use the reporting function even if you’re not a leader, the following “hack” should fix that *evil grin*

Open the Core.lua file in the RaidBuffStatus addon folder, and add this to the end of it:

function IsRaidLeader()
    return true

Good luck raiding!

P.S. Funny picture of the day

…after he dropped from his mount into the depths 😉

Updates: I completely forgot to write about 2 very interesting views. Weaved it in the middle of the story. I also got a new DC again *sigh*, though I can’t complain, because a wow bug caused me to be able to do the weekly raid twice, how nice!

Another update: I discovered the proof reading option in wordpress, which pointed out quite a few mistakes. I was actually a bit shocked by the amount of errors it found. English isn’t my native language, but I still thought I had a better grasp of it. Guess I can use it’s help. It’s not unusual for me to revise a post a few times after I updated it (I’ve got a mild form of dyslexia, which makes me put words in the wrong order sometimes, or simply skip them), but this one needed it badly a few times. My apologies for the bad English I used before, I hope this will improve it a little in future posts.


Lead, follow or get out of the way

There’s no right choice for me when it comes to (PuG) raiding. The thought of raidleading one stresses me out, so I rather avoid that. I do know I’m quite capable of doing it if I have to, because I have done so before, but it only works well for me when I’ve got the correct kind of group. That means: a bunch of proactive people that can communicate normally. I’ll even settle with just no obnoxious types that go kicking and screaming whenever something is not 100% equivalent to what they’re used to, whether it’s no better, or even worse. The type that constantly challenges decisions and can even go as far as deliberately sabotaging an attempt to show they are right. I always manage to get at least one of those on my raid. Kicking them is no option unless I can prove it, otherwise it only seems that he was right, making me look bad.

Not raidleading however, usually forces me into that role. I won’t go kicking and screaming, but when I’m not raidleading I almost always end up in some seemingly clueless group, and the raidleader just doesn’t care, treating everything as if it was tank & spank. I feel forced to explain some important details in those situation, so I could just as well have been the raidleader.

Today I had a good example of this.

The new weekly raid was Ignis the furnace master, a fight I can almost dream. First I went pugging on my restoration shaman. The nice thing about healing is that you can keep yourself completely in the background if you want to, but you’re also that important to the group that your decisions matter. I chose to stay in the background this time for reasons mentioned above. The raidleader was therefor of course, the AFK kind, and let us just do whatever we thought was best. FL went down with ease, so the group wasn’t all new, luckily. The trash before Ignis wasn’t a problem either, but that’s tank and spank with just a little environmental awareness required, so nobody should have problems with that. At Ignis, the raidleader spoke, finally: “go when ready”. One of the tanks charged in and started kiting the boss all over the place. The other one instinctively picked up the adds, but for some reason ran into a far corner with them and stayed there, with me having to make the decision of either running up and solo healing him, or healing the rest of the raid and hope for him to realize his weird choice. He still had my earth shield so I chose the last.

When he started to ask for healing I figured a tiny hint couldn’t hurt. I didn’t want to leave the rest up to my only (effective) colleague healer and also didn’t feel like making the group wipe while I was well aware of the problem, just because I chose to stay in the background. I still left the other tank running in oddly shaped circles with Ignis though. And nobody was still saying anything about that either.

He went down alright, and with the gear people have these days it’s not a big deal of course. The Ignis tank then decided to say it was actually his first time doing this, and wondered if his kiting was ok. Bit late, but at least he cared.

Ok, second run, now on my paladin tank.

I wasn’t planning on raidleading again, but as tank I kinda feel required to take at least a leading role. When we entered Ulduar somebody immediately started a discussion whether or not to try a hard mode FL. I don’t know why anyone would want that these days, and there’s also the risk of wiping, which inevitably causes people to leave, so the answer was no. Nevertheless, he, or somebody else already turned on the towers. So much for that decision. I ended up solo nuking some of the towers, because the pro-hardmode fans were charging straight to FL, while others were just following the ones in front of them. Luckily I got help from the official raidleader, so towers down eventually.

FL down, no big deal, onto Ignis.

Now, I had not met the entire group in person yet, I knew one healer, but that was it. And people started saying “gogogo”. Not fine with me, because I got some rules of my own:

  • Tanks need to be marked. Simply because I want to know where my fellow tank is at and I’m not pulling if he’s not ready. (Note: my ui doesn’t show raid health in numbers, so I can’t see who’s tank quickly).
  • Healers need to be ready. One priest was afk, and those first mobs require some AOE healing, and I didn’t know yet if he was one of the healers.
  • Tanks need to know their target/role.

I stated this, result: small bit of commotion. Not much, but still.

We got marked, I got assist. I changed the tank mark from the druid healer to the DK tank, which I figured out myself by then then was the other tank. We cleared the trash.

At Ignis. We chose nuke tactic (In my book, that’s tank & spank ignis in the water, OT just holds all adds and should be able to do so till the boss goes down), but when some people started to explain that choice as kiting him in a square, and adds nuked in the water first, I got the idea they had a whole other definition of “nuke tactic”. All I could type was “hold on!”, but the ADHD hunter already pulled the boss misdirected to someone in the raid (but definitely not me or the other tank). I quickly grabbed the boss, and just figured I’d do the square kiting thing, if that was the way they understood it. As tank that’s just more fun to do anyway, it’s the classic way, and even if we don’t nuke the adds, it’s really not any different to the water thing except for melee having to use their legs, and tank doing more *yay*.


Apparently another part of the raid did understand “nuke tactic” as tank&spank in the water, and they now reacted as if I was pulling Ignis into their own front yard, and was putting their cat, grandma, and home entertainment system into his slagpot. At those moments I feel like telling them to shut it and calm down, but I just pulled Ignis into the water. It was their choice now.

But I mean, previous group was running for their lives when the tank realized that if you don’t tank Ignis away from the raid, the raid will run away from Ignis, and was quite happy with that way of doing it. Where was the commotion then? It will remain a mystery I guess.

Well, they might have been to busy saving their own ass to also plea the thank for better aiming. I should remember that one 😉

July 2018
« May