Jul 21st 2010 2:43AM "First is a talk between two leaders of the Horde on the direction things have been going. The second is from an upcoming raid boss taunting the players as well as revealing his greatest triumph. Yeah, that's vague, but I'm trying to leave spoilers out from before break."
So very vague, considering that the names of all three are IN THE TITLE OF THE POST.
Jul 10th 2010 7:19PM Absolutely. Strafe-run out from sindragosa, and you can shock and mw5lb while running out. At worst you need to turn a few degrees while running, making a SLIGHT dog's leg.
I play on Aussie lag (250-400ms) and can still make it out of the blast in time just fine doing this.
Feb 6th 2010 6:53PM I'm an enhance who runs 10-man, and on any given fight I may or may not have misery/imp-FF for the extra bonus.
The magic number for horde hit cap in this case is 446.
Here's a macro I use when i'm trying on gear. It shows where I am in my hit and expertise caps (but it ignores passive weapon bonuses to expertise like orcs' axe/fist bonus)
/script DEFAULT_CHAT_FRAME:AddMessage("Hit ="..GetCombatRating(8).."/446 ("..446-GetCombatRating(8)..")")
/script DEFAULT_CHAT_FRAME:AddMessage("Expertise ="..GetCombatRating(24).."/140 ("..140-GetCombatRating(24)..")")
a sample result on a perfectly capped toon for your spec numbers above would show:
Hit = 367/446 (79)
Expertise = 140/140 (0)
ie: you're 79 points short of the 446 point spell hit cap, and exactly on the expertise cap.
Nov 23rd 2009 4:22PM The kitten must go Down Under!
Jul 29th 2009 6:34PM As a hybrid class, I want to know where my 40-slot "Dry-Cleaning Bag" is.
I'd GLADLY give up a bag slot for a bag to stow my multiple sets of situational gear in.
Damn DPS classes have it too good :)
Nov 11th 2008 10:23PM RE : "Could someone "in the know" please explain to me, why on maintenance day was the code for the mail system even touched. "
Such a long story. I've worked as the database lead developer for an MMO. No that MMO is not still running. Yes we had issues at launch and before. Yes they could have been prevented. No, they were not for incompetence.
In short, imagine, just imagine where you live for a second. Imagine that your house, or apartment, or your mom's basement, or whatever is being turned into a three-story building. Only it's happening while you're still living there.
So the builders come in, they jack up the roof and build another level above you, they also lift up the current building and build another level below you. They hook up all the plumbing, electrics, gas, heat, cooling, lighting, DSL, phone, curtains, carpeting, blah-de-blah-de-blah.
That's what it feels like to do a big upgrade to a system. The closet where you keep your work clothes isn't "touched", but maybe there's a sewage leak from the new bathroom upstairs (maybe it was due to a faulty part, maybe the plumber dropped his wrench on the porcelain and broke it, who knows what went wrong). The "what went wrong" is fairly irrelevant. You can bet that your work clothes are pretty much gone, even though the builders weren't even touching your closet.
Of course, being professionals, they have a backup from before they started, so they have two options.
One. go back to where they were before they started and try again.
Two. manually search through the copy of the house they made and dig out the copy they made of your work clothes, then they take out the old closet, clean up the mess and put things back the way they found them.
*THAT* is what is going on right now for the poor engineers at blizzard. Things go wrong no matter how much testing you do. You fix, you learn, you get it right next time. Then something else goes wrong next time :)