Althor,

I looked over the priority list and I have some questions and comments.

Should berserk always be delayed for tiger's fury? What if tiger's fury has 14 seconds left on cooldown, should you hold berserk? What about times when the fight won't last 15 more seconds so you could get a berserk, but not a tiger's fury? At what time is the global cost of berserk not worth it (For example if you only have 2 seconds until the fight ends)?

During execute, shouldn't you pool your energy to 70 for ferocious bites? I was under the impression that more energy is better for ferocious bites as long as you aren't sacrificing rake or rip uptime.

Is a 1 point ferocious bite better than a shred?

Are those cutoff times for when the ferocious bite determined experimentally?

I do not believe you need to check for omen of clarity anymore. "Ravage! is no longer consuming Clearcasting when it is used, and is only benefiting from Stampede."

It might be easier to reference the code if there were line numbers if thats no too difficult to implement. Excellent work so far. I eagerly await the finished product.

The priority list is just a conversion of Mew's priority list. I have no particular understanding of how they came up with those numbers but it did Sim (in SimulationCraft) higher than our old one by around 200 DPS.

You do have a point about the clearcasting thing however. It's would seem likely that check is no longer required. SimulationCraft already models Ravage not consuming Clearcasting in the code after all.

@Althor: The results look a lot better now (One quick thing that will be a net gain is to use Enchant 2H - Mighty Agility instead of Landslide). I'll cross check the output/code some more and let you guys know if I find anything else.

I'm the one to blame for most of these, so I'll answer.

This is encounter duration dependent. The decision is almost entirely based on "will pushing back Berserk cause me to lose one at the tail end?", which for most encounter lengths is "no". Adding a check to see if remaining encounter length will be <= the TF cooldown + Beserk duration is a good idea though. The global cost will not be worth it the moment it costs you a yellow attack (At the tail end of the encounter, a Feral Druid is not global locked for the vast majority of the fight.), but the exact situation is rather unlikely.

I haven't been able to get a net gain by doing this yet. The window you have for pooling (at least as of 4.0.1, have not rechecked yet) is somewhat smaller than you may expect since the Glyph of Shred was not being reset by Ferocious Bite. Getting to 5 cps, and pooling as high as you dare while avoiding Rip falling off due to a freak miss streak and ensuring Rake has a high uptime is a bit much for 16 seconds of time. Possible room for improvement perhaps but I don't see it as all that likely at a T11 gear point.

Nope, though a 1 point bite that you can cast is better than a Shred that you can't. My quick and dirty attempts to change this conditional all sim slightly lower. There is room for improvement here, though the difference is minor.

Yes they were.

Hmmm. Which is more likely, "OoC procing in the global after a Ravage" or "Ending up pushing back Ravage too far and losing the TF benefit if there was one"? If it's the former, then the code should still check OoC (There's a fallback conditional to prevent Stampede not being consumed entirely, so this is purely a matter of wasting an OoC proc). If it's the latter, then Ravage should be used regardless of OoC (Modifying my script suggests the check should remain, but the differential between the two is not statistically significant.).