Being below expertise means that out of the attacks that would not miss some of them will be dodged . Let's say that you have 5% dodge chance and 100% hit chance (being hit capped but not exp capped). That means that out of the 100 attacks , 95 will land and 5 will be dodged. Now if you have 20% crit, that means that you will crit only on those 95 attacks, effectively lowering your crit from 20% to 19%. In other words, expertise will always be of a higher dps value as long as the other stat modfiers for warriors stay as they are.

As in many situations with other things like hit it is better to be a couple of points under instaed of going quite a few points over. Points over are 100% ineffective coming at a high opportunity cost, points under are statistically insignificant (I've run 7.98% hit for a long time and gone weeks without missing).

I got a question for a perfect CD usage.
Lets say i got VoA + AoK, we start a timer, i drink a prepot at 1s, BR + Shout > CS > reckle+dw+synapse+hcleap > BT etc.
I use AoK at 2nd CS, and what then? I use every CD when its ready or shall i stack some with other, liek DW + AoK/reckle, ofc assuming we take patchwerk style encounter.
I'd be very grateful if someone could describe best CD usage from the start of the pull.

self explanatory







p.s. somewhat random logs from WoL top20, any coincidence is just a coincidence.

If that's true then you should be able to get 4 during CS by doing CS-BT-Exe-Exe-BT which will be a bit more managable in terms of rage income.

Runtime, that normaly would not work since you will be casting BT before CS anyway, making your next BT (the one after CS) still on CD (and thus not benfiting from the latency reducation).
However we can do something like BT>CS>Slam>RB>BT>Slam, even while not in execute phase.

I think a good option would be BT-Slam/Shout-CS-BT-RB-Slam if procs BT otherwise-BT if slam proced. That way your not delaying BT if you don't get a slam proc.

Yeah sorry I made a mistake. I realized it as soon as I left home! A BT can never be used on cooldown across anytime during the CS debuff.

When I keep thinking about it all the requirements to pull this off not in Execute phase are really hard since the slam chance is low and, shout availability might be sparse. You can't really guarantee you have the slam. You can only possibly know if you'll have one slam going into this.


BT>CS>(RB, Slam, BT, Slam) could work, but if you don't get the second slam you screwed yourself.

BT>Shout>CS>(BT, Slam/RB, RB/Slam, BT) would work well, since you know if you will have shout and have 2 chances (51%) for slam or could carry one over from a previous BT (only 1 second left on the buff tho). I don't like this at all for SMF because of the awkward rearranging of the BT for an RB. Maybe it would work better with T12 (shout buff and Fiery Attack) but not so much T13

Only about 50/50 on that slam being there or not if you use shout there, and you know if you'll have the slam ahead of time. If you slam first instead of RB there's also a chance it could be active from a BT before all that mess with 1s left.

I'm seeing a problem here of a delayed CS (it usually finishes CD right after a BT) and the skipped RB if you're TG.

1. I doubt the delay in CS is any concern, since you lose 1.5 seconds of the CD but gain one whole BT into it.
2. I think it happens more times then not. As you said, in a rotation like BT(bloodsurge proc)>RB>BT>shout>CS>X you still have time to slam. if bloodsurge didn't proc, then it can still proc during the second or third BT (as in, after BT>shout>CS>BT). All in all there is more chance slam would proc then not.
3. As you said there might be big delays in BT and RB useages in the first secenrio you delay BT for another extra gcd), and I will leave the math of this to you. However I think it's importent to remember that 2/2 booming voice makes shouts line up very well with CS, and even if we lose RB the extra rage can still be used to HS, before you throw it out of the window.

edit: I just relized that the first secenrio I suggested is almost impossible, since you will have to get a bloodsurge proc from the BT that is used inside the CS.

I recently was looking over simcraft and was wondering why it tended to only use bloodthirst every 3.84 seconds or so with the current priority list.

So, I looked over the data and bloodthirst was being skipped occasionally because it was 0.1-0.3 seconds away from being off cooldown as the program simulates latency.

So you would run into situations such as this for SMF:

Bloodthirst
Slam
Raging Blow/battle shout/whatever (0.1 seconds away from BT being available)
Bloodthirst

I found adding in the following conditions: (Obviously not the entire priority list)
actions+=/colossus_smash,if=cooldown.bloodthirst.remains>0.3
actions+=/slam,if=buff.bloodsurge.react&cooldown.bloodthirst.remains>0.3
actions+=/raging_blow,if=target.health_pct>20&cooldown.bloodthirst.remains>0.3 (Obviously for SMF)
actions+=/battle_shout,if=rage<70&cooldown.bloodthirst.remains>0.3

Resulted in about a 3-4% dps gain, which is rather significant.

It's not a change in how we play, it's just a change in simcraft to better simulate how we play.

Now, one question I have for everyone here is... what's an easier way to program this logic? Or do we HAVE to add in that condition to every line? Or maybe latency could be set to 0, I suppose.