AOE Rotation - on 3 - 5 Targets. Use Whirlwind x 3 to stack to build up Meatcleaver on those targets then Raging blow to strike those mobs. Dragon Roar on CD. You still of course want to maintain Bloodthirst, Colossus Smash and Raging Blow. Raging Blow on the 2, 3, stacks of Meatcleaver if 5 mobs. Example would be, 5 mobs. Open with BT, WW, BT on CD / CS on CD, and Dragon Roar on CD, WW until you have 3 stacks of Meatcleaver, then RB. For rage dump, use Cleave. Rules for stacking Meatcleaver is if 3 mobs, 2 stacks of meatcleaver, 4 mobs then 3 stacks of Meatcleaver. There are two schools of thought out there on this, 1 to 1 stacks and 1 stack less. That's a tweak we will have to play with. For now we can test out 3 stacks of Meatcleaver and see how that goes. AOE rules for 6+ Mobs, just spam BT, CS and Whirlwind. BT / CS on CD, Dragon Roar on CD.
I also want to tell this community that this routine is amazing with 522+ Item Level / Heroic ToT. Not that any of us would expect anything less. I just wanted to confirm that you indeed have something to look very forward to. Because of this rotation, I have about 10 US / World Records. A few of then in the low teens. With the incoming AOE and Execute tweaks, this rotation is going to destroy world of log records the US / World over. As it stands, I out DPS / Damage Rogues. Rogues that have a higher Item level than I do and these are world class rogues in some of the top guilds. This rotation just never fails, it never gets tired, it never makes a mistake. I'm also going to share a few top dps tricks with Nom to see if we can't figure a way to somehow get them implemented into this rotation.
AoE will be exactly as you describe in new release, and on the private SVN until the release. One small note; MeatCleaver can only stack to 3 according to the tooltip: Meat Cleaver - Spell - World of Warcraft "This effect stacks up to 3 times."
Current rotation during <= 20% HP is: Heroic strike @ 110 Rage Bloodthirst Wildstrike on Proc. Dragon roar on NO CS, Blodbath enabled Colossus Smash Execute @ enrage OR CS up OR Recklessness up OR >= 90 rage. i think it should look sth. like this: Current rotation during <= 20% HP is: Execute @ 110 Rage Bloodthirst Wildstrike on Proc. Dragon roar on NO CS, Blodbath enabled Colossus Smash Execute @ enrage OR CS up OR Recklessness up don't know if it had to look like this but @20% your goal should be: build up rage with BT->wildstrike proc. -> RB -> DR and execute when hitting rage cap (just like HS before 20%) but CS is still on CD. When CS is ready only use execute and than repeat. HS is very expensive and it should not be used below 20% instead use execute.
Hello guys, first of all I'd like to mention what an awsome combat routine. I really appreciate all the time that's spend to create this. But I've got a little problem with Commanding Shout on my Fury. I put CS in the Options, save and close, but next time I open there's Battleshout. I tried reinstalling ybmopbt incl. deleting cache but my Fury Routine still denies casting Commanding Shout. Am I doing something wrong? I use the official release of ybmopbt, so no dev-version.
Brilliant, you are the first one to notice this bug ! Will be fixed in next release . Edit: Bug exists in both Prot & Fury ...
I tried using the search this thread feature but found nothing.. Before it wouldn't use Disrupting Shout if Pummel was up but it is no longer the case since the update.
Hey there.. Does it support (and it's good enough) protection warrior leveling on dungeons? (Using Tyrael) Thanks for replying!
execute prio should look like this: cs --> exe --> bt ---> rb ---> dr ---> ht i am not rly sure about ws proccs, but maybe usefull if cs,rb are on cd and ure rage is low and it proccs. hs are really waste in the 20% phase!
all these different execute phase rotations this is entertaining... you got it but in 5.2 FREE WS is part of that priority before HT which idk why u have it in there but i guess doesnt hurt
IF you guys haven't yet, please consider supporting Nom with a donation. This is an excellent routine and lets all be honest. it's a lot of hard work. A little good will ( donation ) does a long way and will help keep up the momentum going.
i did that and will do it again! Smoother and faster than ever, by FAR rhe best Routine overall. Please Nom, dont spend to much time in this, ist allready perfect and keep your time for future upddates. Thx a lot
Internal revision 206 * Updated advanced logging (Debug function for nomnomnom). * Fixed a bug with unable to select and save Commanding shout in Fury & Protection. * Updated AoE rotation, should perform alot better. This is a quick release-update and not going into beta as not much has changed. Next release (207) will be a larger update --> Placeable banners, on-keypress heroic leap and the updated Execute rotation . Fixed . It will only use Disrupting Shout when Pummel is on cooldown. Its useless to burn 2 interrupts on 1 spellcast. There is no better protection rotation than this ... For level 90. I have no idea how this will work for below level 90. I truely appreciate what I received from you already! * Like * @ Everyone I will be reviewing and SimC-ing all the mentioned execute rotations and see what ends up as the best DPS. Thanks for the suggestions! .
hey nom in prot spec the alt mod isnt working in hotkey mode but all the other mods are working but in fury spec it works
Хотел спросить что стало с АОЕ в данный момент протестил в бою перс не использовал вообще заклинание 'ВИХРЬ" будет ли он в дальнейшем его прожимать? Данный тест проводился на двух стоящих рядом манекенах.
Yeah you need an exception rule for bosses. Garalon was also broke for AOE, leg and body ( 2 ) targets so no AOE in that fight which is bad cause of the leg buff. But we are going in the right direction as far as the AOE tweaks. Higher DPS in those situations.
Понятно теперь что по 3 цели,но бывают же такие ситуации где нужно по две цели выдать АОЕ,по крайней мере видел пару раз такое по две цели. То как с двумя целями бороться?