Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
4-13-2007 @ 2:26PM
MattRossi said...
"The warriors reference was, I assume, the fact that some tanks (not just warriors) will rush head long into the next mob rather than wait on the mana user's to let their mana regen. Some of your finer tanks will do this regardless of how hard the previous mob was. Its a potential sign that you're going to have problems with the tank since they aren't aware of their surroundings enough to realize not everyone is using a rage bar."
Maybe if the party showed the slightest idea of how to wait until the tank had established aggro, the tank wouldn't be so desperate to hold it that he had to run ahead to aggro the mob while he had enough rage to spam his threat generating abilities.
I have lost count of the number of runs I've done where the mage and rogue open up DPS the second I make contact with the enemy while the priest throws a power word: shield on me so that I take no initial damage and thus, generate almost no rage. It's maddening, and the fact that even *experienced* players still do this drives me insane. Sometimes, yeah, I'll run ahead and engage the next mob while I still have rage because, if I don't, they're just going to do it again. Mana and energy go UP the longer we wait, rage goes DOWN, and if I'm dealing with a party of aggro whores and shield-happy priests, I'm going to make THEM sweat for a while.
As for that right click nonsense, I have no idea what the hell that was. It's not like I need to, I don't know, generate rage or deal with cooldowns or even hit a damn button once in a while.
Reply