Originally Posted by pindle
I've been searching this thread for the reasoning behind this, but been unsuccesfull so far. I know KM is better used on HB due to the already higher critrate on FS and its nerf this patch, but shouldn't it be added to always use up the proc before casting the next Obliterate to prevent the effect from overwriting itself? Is it more beneficial waiting with the HB until you do have KM up, even if there's a chance you'll be overwriting it therefor losing one HB cast?
|
You are thinking the wrong way.
You have to let go of the idea that every rime proc is an increase in dps because it does damage.
We are limited in GCD.
Imagine that during a given time period you can only do 6 attacks. Would you waste one of those attacks on an attack that does 2000 damage, or do you use that for an attack that does 6000 damage.
It is not that rime itself is bad. It's simply that in the limted timeframe we have, there are stronger attacks.
As for my rotation. At first I tried to stick to a set rotation, since I figured that was easier to get to know the spec with. But in the end I personally found it easier to just go by the priority system.
In my mind it basically goes like this:
- Any runes available for use? No: FS / Yes: next step
- If frost/unholy/death runes: Diseases up? Yes: Obliterate / No: IT+PS (with diseases up i usually check if they fall off before a next set of UF runes become available)
- If blood runes: Bloodstrike if no other runes available
- If Rime Proc is up: KM up? Yes: HB / No: Ignore
NOTE: This isn't a priority list from top down, this is more of a checklist, i consider all options each GCD basically
This isn't a strict priority list as much as a checklist I make for myself each second. I rate Diseases highest, then Rime+KM, then rune attacks and last RP dump (which i weave into my other attacks). I usually let KM "handle itself", it usually goes to the RP dumps anyway, unless I have an available Freezing Fog proc. However sometimes i intervene a bit by weaving in an early FS to avoid IT from stealing KM, but only if that doesn't mess things up.