Dragon Roar is perfectly coded in the routine. There is no use of doing it yourself, that will be a DPS loss.
I mentioned to use victory rush since i use it while doing quests and need to use it manualy everytime i need
Rly? It works awful for me with Avatar build. I changed it to: Code: YBSpell.Cast("Dragon Roar", ret => G.DRTalent && !G.ColossusSmashAura && ( (SF.Instance.Tier4Abilities == YBEnum.AbilityTrigger.OnBossDummy && YBUnit.IsTargetBoss) || (SF.Instance.Tier4Abilities == YBEnum.AbilityTrigger.OnBlTw && (G.BloodLustAura || G.TimeWarpAura)) || (SF.Instance.Tier4Abilities == YBEnum.AbilityTrigger.Always) )), And only after that routine starts to cast it, before the change (with avatar and BB checking) DR was casted very, veryyy rarely.
Did some more toying around with the developer test version in raids, it's fucking awesome. performing top notch. Used it for several TOT Raids.
Yes the 209 beta is alot better than the 206 release. The upcoming beta, 210 is even more of a leap forward ^^ almost ready! Glad you like this routine.
Nom - tested out XXX - .... and ... AMAZING. AOE DPS - Much Higher Single Target - 3 - 4K higher from my initial tests CD's lining up - Beautiful. I love how you have Reck / Banner programmed. Dragon Roar is now much much MUCH more consistent. Biggest shock is AOE - great numbers. One slight problem I noticed is that AOE routine does not allow execute to pop at all. I confirmed this on one AOE boss fight and plenty of AOE trash. Example, Stone Guard 1st boss MV, did 175k but zero of that was execute. execute did not pop once. Had execute worked correctly, I would have had 185 - 190k or more. On the other bosses, execute worked perfectly. Something in the routine force whirlwind over execute in those AOE situations. Otherwise, amazing dps. I saw higher numbers across the board.
Quick question, with the rallying cry activation at 10% health, is that your health or anybody in the raid? Should probably be anybody, at least for prot since you have last stand for yourself. Though personally id say for anyone is best regardless, also maybe same with demo banner. If this is already the case good work batman! If not then its a suggestion you may want to consider. Im pretty sure this is doable as ive seen ret profiles LOH anybody in raid below 10%.
Tried to tank with this yesterday. Seems to not be using Shield barrier or shield block. also had some threat issues. Not my main char though, and I basicly never tank, so I dont know if threat issue is due to my gear, the CR or the warrior class -.-
Ive used it for tanking and for the most part its pretty good, only uses block/barrier on bosses, i think i read earlier in the thread though this is going to change. Im an experienced tank but also a raid leader so being able to free up my mental resources to focus on bitching at people this is helpful. Ive spoke to nomnom in past about my suggestions for how to solve the block barrier problem and while not the choice i would have taken the one he has implemented does have its benefits and definitely make things easier for those not so experienced with tanking, which i think is the whole point. Nomnom also does the purerotation warrior CRs which are setup slightly different perhaps try that as an alternative if this is not floating your boat.
I had everything enabled etc, still didnt even preform block and barrier on boss, so I switched to Purerotation after the first boss. They are both realy good CRs, but I get a feeling that YBMBT is preforming slightly better still! The only reason I switched was becouse its my alt, the gear is not that great, so I had to rely on the defencive CDs to work.
Yeah sure, sorry about the slow reply, I did not have the logg file on my laptop. Haven't been home until now. here you go. You can see that I use Tyrel etc and Framelock at 60.
This is using Heroic Strike on <20% targets. Could someone help me fix this? I have tried changing the Heroic Strike section of the priority to the following: This CC has so many advantages over the others, and I love it, but this is a serious problem for me. Unless I am greatly misunderstanding the class entirely Execute should replace Heroic strike under 20%, 100% of the time with no exceptions. *nevermind, that line works just fine when I add it to the correct file.
Glad you like it . It's for yourself, I can investigate the anybody's HP but it requires alot of scanning around and that will not be beneficial for the routines speed. But will investigate for a good method. The shield block and/or barrier issues should be close to fixed in the next release. It has updated code for this. Yeah We're going to use lists, only viable method. If it didn't pop at a boss, I'll need a log ... If you want it fixed NOW. Otherwise wait for next release. There are reasons why it's still there. As HS is off-GCD you will not be wasting any incoming rage. There might occur situations in which you still get rage, but are unable to cast execute for whatever reason. Then the HS rule takes care of your rage-cap. It'll rarely happen, but I really suggest to keep it as I coded it. See above. Wait for next release and give me a log of that. I'm going to improve the logging so we can diagnose it better.
Would be amazing, its crazy just how much of a difference that extra 10% hp can make in keeping a raid member alive, so often the difference between a kill and a wipe.
the problem is to make a "smart" block / barrier algorithm. The rotation itself is quite good for prot. i use it my self sometimes. just let the cc do its magic and pop barrier / block your self. only one thing i would change is to add some hp treshold for impending victory / victory rush. something like hp < 86 cast impending victory hp < 81 || Victory Rush aura fading -> cast victory rush (hp < 71 && HasGlyph("Victory Rush") || victory rush aura fading -> cast victory rush and maybe add a check if barrier / block is up. so the heal is out when some defence is up. Cause if you pop the heal and then gets hit hard it is some kind of wasted. and maybe also cast only when rage is 70 or more. sry nomnomnom that i am currently not very active with testing. was quite busy the last days. but for the quick test its working quite good good job mate as always!