Maybe in PvP, I fail to see how doing it manually would be of any benefit at all in PvE content though. The increased critical strike bonus would have the same effect whether you stack it with other cooldowns or not. The only thing that would matter for a constant fight would be to ensure it's always cast on CD. That being said, it's not hard to cast yourself, it would just be nice to not need to.
To all testers: Code: Dunatank's Warrior CC v2.1 BT Alpha TEST will most likely be finished by tonight. This version will feature: Pull sequence (Charge/Heroic Throw) Interrupt at the end of casts Leaving out some Fury abilities if Colossus Smash CD < 5 sec & rage < 90 No useage of Inner Rage when Heroic Strike or Cleave are currently on CD (-> would be a dps loss, as we would waste 1 HS/CL)
he doesn't love me anymore, as for the trinket, stop being lazy as zachary said, its better to do it yourself since if this bot/cc would it can fuck up a rotation or bad timing which means dps lowered. time it yourself.
Hey hey. Here's some VERY helpful information. Check it out. Damage per rage: BT: 1450 RB: 1000 HS: 850 Execute: 1200 ____________________________________________ Here are the following scenarios in which heroic strike usage is ok. Rage > 85 and you're not in execute phase. Colossus smash and rage > 50 Incite proc (Save for Colossus smash if possible.) Battle trance proc It should be noted, that even though heroic strike is our least rage efficient attack, you will still be using it a lot. It generally ends up being 8-12% of my overall damage on most encounters. General rotation: BT_BT_BT Fill in blanks with CS > Slam > Execute > RB > Battle shout Rage management is incredibly important here. I would highly recommend grabbing some sort of add-on that places a rage bar close to the middle of your screen. I use enraged at the moment, and I would recommend it as it’s highly customizable. You’re going to be pooling rage, which will lead to moments where you think you need to use heroic strike.. but you’re going to have to hold off using it for colossus smash. Why do we pool rage? Colossus smash. When Colossus Smash occurs, you're going to want to shove as many abilities as possible in that 6 second window, and if possible you want to save an incite proc as well for this. If you have timers, I would HIGHLY suggest that you place Colossus Smash as one of your timers so that you know when it’s about to come up so you’re not like “Oh %***, I have no rage.” So when Colossus Smash happens, in a perfect world it would like this: CS-Bt-Slam-Bt With 2 heroic strikes thrown in. If for some reason you do not have a slam proc, it is fine to throw in a raging blow instead. If you’re rage starved (<50 rage), do not use heroic strike unless you have an incite proc. The reason you want to pool rage as much as possible is that to do the entire rotation in 6 seconds it will require 120 rage without raging blow, 140 with it. That means that if you pool 80 rage for CS, you'll need to have a rage income of 40-60 over the next 6 seconds to make this work effectively. Generally you will have enough rage, as with most gear setups you probably have an average Rage Generation per Second of anywhere between 12-14, which means that in 6 seconds on average you gain 72-84 rage. Of course anyone who has actually played fury will tell you that our rage generation is not very reliable as hit-cap is not feasible nor is it even recommended even trying to hit, and a string of misses could lead to you being rage starved over this 6 second period, which is why we want to pool as much rage as possible to counteract RNG. Effective colossus smash usage is THE most important part of this rotation. Execute phase: Execute is no longer our hardest hitting ability as blizzard buffed everything else and to make this easy… you’re basically only going to use execute to maintain the 25% haste buff and as an extreme rage dump. When it’s ok to execute: Getting stacks of executioner up to 5, or when executioner is going to expire in 2 seconds. You want to initially get your stacks up by doing this BT-Execute-BT-Execute-BT-Execute... Rage is above 50, or the boss is going to die in the next 3 seconds and you need to empty out your rage bar. As a filler during colossus smash, if you don’t have a slam proc, you can do BT_Execute_BT instead. (Due to rage capping you will actually do this a lot.) You will no longer use raging blow during execute phase unless you have more than 13 mastery which after the 4.1 patch is just incredibly unlikely. Execute is more rage-efficient due to the "Adjustment" mastery/raging blow took recently, if you have more than 13 mastery go ahead and use raging blow as normal. Keeping executioner up is your highest priority. It doesn't matter what you're doing, if it's about to run out... execute. Generally during execute phase your rage income is high enough that your rotation will end up being BT-Exe-Bt-(slam proc?)-Bt-Exe, with very very few free GCDs.
Does anyone know a good website kind of like ShadowCraft - Rogue DPS Spreadsheet to help with reforging/gems ? I'm horrible at deciding those things.
Just did some exensive testing on arms rotation with the new beta testing build. 1. Slam should not be used if MS is less .9 seconds from being off the GCD. 2. OP should not be used if MS if .6 seconds from being off the GCD. 3. Colossus Smash should not be used if MS CD is greater than 2 seconds.
It was a simple question. I don't understand why you have to be rude about it. I was asking because I want to further my DPS to do raids with this CC and I personally don't really like the addon, but thank you.
I'm not being rude. I'm simply informing you that you are being rude by asking questions that are unrelated to the author's thread subject - His Warrior CC. If you want to ask that type of question you can, but this is not the place for it.
Another thing I noticed for Arms. Arms has a chance to reset the CD of CS. The bot currently immediately will use it right away, which is a problem if CS is already up. You end up losing the benefit. is it possible to add a detection that if CS is up, don't cast CS? Thanks!