Threat racing on bosses

[Gruscovac]

As a pali tank in my previous guild (back in BC) there was one lesson I learned very early that saved 4000 million headaches down the line.

If you are having a threat race on a boss that's a good thing.... as long as:

A) you are all standing infront of the boss not on OPPOSITE SIDES, I mean seriously.
B) You DO NOT, EVER, AT ALL, FOR ANY REASON (except tank death) use taunt.... EVER. Especially not if you're suffering the stupidity of point A)
C) if you need to move the boss the you work as a TEAM to make it happen....

anything else is greedy selfish grand-standing...

this from the bloke who DIDN'T die this time round.

[Easypeasy]

Sometimes I use a Shield Bash, Revenge, Devastate, Taunt rotation because although being a completly different key and graphic I mistake Taunt for Devastate.

I'm currently working on a fix trialling a new macro:
/Cast Taunt
/Cast Devastate


4 billion headaches ouch


Cheers
EP

[Epimethius]

Threat racing on a boss is fine, but taunting off of another tank when the fight mechanics do not require it just causes undue stress.  From a paladin perspective, it is not as damaging to our threat as it used to be (we have Shield of Righteouseness and Hammer of the Righteous now) but it is still annoying.

When the raid leader / tank leader assigns a tank for the fight and then someone goes "into business for themselves" and just decides that they will be MT is makes things hard.  The healers are set up to heal the assigned tank, not you.  not to mention the fact that tanks are usually assigned for a reason.  You may not be the best tank for the job.  Tanks have been homogenised a lot, there are still small differences.  While everyone can AOE tank, some classes have a slightly easier time than others.  While everyone can soak Hateful Strikes, druids have the healthpool to do that much more easily.