Anybody else have their portals seemingly stop working? Use it on Sha usually, and noticed last Thursday it just wouldn't port me after a couple times (think after returning from one of the side mini bosses).
You could do this prepatch.- Threatening Presence can now be toggled on/off with a left click in the spell book.
This change was mentioned prepatch so it's documented just not in the notes.- Grimoire of Sacrifice cooldown reduced to 30s.
Last edited by Harsesis; 2012-12-02 at 05:19 AM.
If this one works its a BIG one, I was soloing nax and pet was about to die out of reflex taunted the boss, it worked. Only tried it on instructor, but i can assure you my taunted taunted the boss.
I Will test this out in this weeks raid and see if it works. RL prob gonna be mad at me tho.
Okay, tested Chaos Bolt!
With 4988 haste, which is what I happened to have on my gear at the moment, without 5% haste buff from being in a raid, but with the 1% goblin bonus (deal with it), that ends up at 12.85% haste.
On a dummy I concluded that in a situation you would have 12.85% haste in, you can safely cast 3 Chaos Bolts in a row. A Chaos Bolt DoT has 3 ticks on it, when casting 4 in a row, only 11 will go through, thus being DPS loss.
With Bloodlust up, or when running with more haste including raidbuffs (still not 100% sure on current stat prio for GoSac, gonna be simming my own char in a bit), the number of safe Chaos Bolts will probably drop back to 2, casting a single spell between the second and the third will make the third perfectly safe though. If for some reason you're running with lust up, with a haste build, haste trinket, and with backdraft stacks affecting the second cast, it might not even be safe to cast 2 in a row, but we're talking extremes here obviously.
Damage of the DoT seems to be about 8% of your initial Chaos Bolt per tick like the talent would suggest, with the first tick being a second after impact, and the last tick being 3 seconds after impact (minus haste of course).
On a different topic, the GCD of Havoc seems to have been removed/lowered to .5 seconds or less, and I'm pretty sure that was not the case during 5.0 (correct me if wrong).
Before you could cast FnB:conflagrate even when you have 0 charges of it, so you could cast 3 conflagrates in a row (conf-conf-FnB:conf), now you can't do it anymore (i'm not sure since when this change is on live, and i'm almost 100% sure that isn't documented)