After weeks of use, i would like to say that this CC works very well (maybe i could have a better dps with my fury warrior if i had a better CPU Well done guys
Code: YBSpell.Cast("Shield Block", ret => SP.Instance.CheckShieldBlock && !G.ShieldBarrierAura && YBUnit.IsShieldBlockTarget) YBUnit.IsShieldBlockTarget <-- because of this condition. List of targets you can find in Helpers\YBMoP_Hashsets.cs
I am still not getting enough Executes. In LFR on 50 million hp mob, char was at full rage @ 20% casted all kinds of stuff and 1 Execute. Mob died and I was again at full rage. I have the dev SVN installed.
Thats not fixed yet, so yeah . Glad you like it. Its cause of the logic, I'll change it to fit better in next release.
Update Working copy 'C:\Users\mitchell\Desktop\HBmain\Routines\YourBuddy MoP BT - Warrior' locked. 'C:\Users\mitchell\Desktop\HBmain\Routines\YourBuddy MoP BT - Warrior' is already locked. not sure what happened trued to update I get this message.
Alright guys. I don't know HOW you'll do it, but I'm lost in the forest of execute advices. Someone create a new topic and discuss it (Not here) and let me know the results what the best method is to handle execute. And hurry up, take some responsibility as the users and help me with this ^^.
your current release... Code: YBSpell.Cast("Execute", ret => G.EnrageAura || G.ColossusSmashAura || G.RecklessnessAura || Lua.PlayerPower >= 90), ... you didnt fix the line to have execute check, thats why still lack of executes going out. earlier in this this thread this was posted. maybe you should fix this line before attempting to theorycraf your code, cause from what i read its absolutely perfect. Second your cleave rage dump value should be at >=110 as simC states. anywho hope this helps... and one question logic on intimidating shout during fury rotation (option to turn it off,maybe)??? edit: 501 ilvl - Tortos LFR - With Execute Check -- Never Capped Rage
@daorigin I made the change in the Execute code. I am signed for LFR to test it. Hopefully I get in. Will post how it performed. About Cleave, I noticed it being used right after charging into multiple mobs. Not that I have paid any special attention when exactly it gets used, or that I am any expert in warriors. It just grabbed my attention that I charged at Wind Lord adds and I saw Cleave..
Either I am too dumb or my logic sux, but I have that turned off from the very beginning that I am using this CC. I dont see how ST will bring me dps boost when I am loosing 1.5sec cast time + GCD + 25 rage.
Oooo yes man! Just killed an elite @ 6mil HP. I had a lot of parry and shit so rage could not go high, but it still casted 5 Executes
It uses fear ONLY with Intimidating Shout glyph and on non-boss targets. This way they do not run away cause of the glyph, but saves damage ... If you really want the ability to turn this off, let me know. I know, it's still a forest though . I know, will be fixed in next release. Cleave changes are made for next release. Retest after we released 2.0.7. (Today). The intention is a 2-way method. 1: Let the routine autocast it when checked. 2: Enable hotkey mode, uncheck the autocast and use hotkeys to cast Shattering Throw. Good, this execute "fix" will be added to next release. It will not be the final fix, just a temporary "patch on the wound". Fixed in next release. Only uses barrier on barrier-bosses in ToT. Rest it will use block. Delete folder and checkout again.
Committed the changes I made last night to developers SVN. Release will be updated during the evening. Changelog: Internal revision 207. * Changed item-usage priority (First trinkets, then hands). * Created hash set for non-placeable spell-targets. * Updated advanced logger for nomnomnom's use. * Changed settings files to reflect different default settings. * Preparations made for on-keypress actions. * Fury: Updated Execute usage. * Fury: Updated Cleave in AoE. * Fury: Fixed Shattering Throw. * Prot: Updated Shield block to use on all targets except Shield Barrier hash set targets (YBUnit.IsShieldBarrierTarget). * Global: Updated interrupt code in Prot & Fury.
i dont get quoted! i gets no love!!!!! niiice steady feedback, steady update good job nom. I assure you though there isnt anything wrong with execute phase once the check is in place, but you sure have your work cut out for you with prot/arms