Hi Calm,
Gonna address 2 things here:
1) Dragon Roar in dummy testing:
If you're doing 3 mil dmg tests, with roughly 15k dps, you're standing there for 3 minutes something - which should give you 4 dragon roars every time - on the table above you have 8 - which tells me you quite possibly were standing too close to the lower lvl dummies, explaining the burst in dps from that ability.
2) Rage-capping and priorities:
Delaying BT because you're high on rage, is not logic atm. Yes, rage management and "not-rage-capping" WAS a huge part of fury, but since you don't have an off-gcd dumb anymore, that has sorta changed. Here's the reason why:
- When you don't delay BT, you can fit 2x BTs into an enrage window due to blizzard extending that window.
- BT proc's your Bloodsurge and RBs, which are both more DPE and DPR than hardcast-WS.
- Having a filled ragebar will enable you to hardcast WS more often when unlucky with procs, thus reducing empty GCDs.
- BT on CD increases the enrage uptime, the value of mastery and your avg. DPE efficiency.
NOTE: the need for BT on CD will likely decrease IF gear allows you to once again reach near-cap crit scenarios (this is some time down the road atm). But the importance of your enrage uptime will increase with your gear, as both WPdmg, Mastery and AP will have an amplified effect from it
As an example, I'm able to keep around 94% enrage uptime on butcher atm. I do delay it sometimes tho, but here's the rules I follow
1) Execute on SD
2) RB if 2 stacks banked (not applicable sub 20%)
3) BT
4) Execute sub 20%
5) WS proc'ed
6) RB
7) WS hardcast
If anyone wanna dispute this reasoning, I'd be happy to debate the topic, as I find the general perception of rage-management (WS-hardcast vs BT on CD) misleading.
/Falken