No real suggestion in what best to do with the rotations and such, as for such matters I've found that the ideas you've had and that you've been getting from other here vastly improve on your CC more than anything i could say would. However from a coding perspective I only have the one suggestion, which is one a made a few days ago, and that's to add in the open and closes to your if statements in your combat rotations. I'm not sure if this is just the case for me as I'm not sure why its making a difference as it really shouldn't matter for 1 line if statements, but through out all my test I have been seeing some abilities trying to get used out side there defined IF statement, whilst after I added the { and }'s I haven't noticed these any more. I can also so that in doing this I have been getting a constant increase in dps from both this CC and your Hunter Marks CC.
@Macphee: I havent seen anything written here about that before! I must of missed it :/ But yeah, I'll take a look at that.
@Maxphee I had wondered why there were no openers and close tags in the CC when I had first started to edit it, as I had never seen a CC do this before Titan Arms, but I assumed since it wasn't throwing errors and was running very fast that this was the cause of the CC's speed and ability to quickly change from single target to AOE rotations with little or no delay. Good call tho if this is actually causing issues, and I will have to add openers/closers to Titan Shields as well. Looking forward to the update Shadd. Only suggestion I would have isn't really that big of a deal as its the difference in rotation for 4pc t13 or not having 4pc t13 and that is if 4pc t13 then MS > CS but if you don't have 4pc t13 then CS > MS. Currently I am just making the adjustment manually on each update as I only have 2pc t13 (since I used my other tokens for upgrading my prot set from LFR to regular tokens). Keep up the good work. I am going to be looking into some additional stance dance code today and will see what I come up with for a way to stabilize the dancing. I will let you know if I am able to come up with anything good!
Hey, havent had much time the past days so Im not up to date on this topic but I did a raid yesterday with the standard 2.2 version; This is all in a 10-man NORMAL DS Morchok; 29k Zonozz; 59k!!! Ooze boss; I forgot ... Ultrax: 38k!! Hagara; Forgot but wasnt impressive. Ilvl of my character is 390, with T13 2P and Gurth raidfinder edition.
Not bad! Hagara is hard to gauge. Did you get Ice Tombed at any part of the fight and if so was it possibly during sub 20% health? If so, this could have been the cause of your sub par numbers compared to the other fights.
Titan Arms v2.2 Update. Bladestorm Execute Phase #Region Combat #Region CastSpell Method #Region Add Detection All of the above has either been improved, removed or altered. --------------------------------------------------------------- A few minor bug fixes and i've added {} to the If statements to see if it results in a DPS increase. As usual I'd love to have some feed back! PS: I've done 2 hours of testing with Stance Dancing, this is the last time i ever attempt to code that into Titan Arms!
Seems better then ever Still would love seeing Overpower and Slam get delayed if Mortal Strike/Colossus Smash CD < 0.5 seconds. And did you alter the execute rotation to just Colossus Smash > Execute (if Executioner < 5) > Mortal Strike > Execute. I think this execute rotation is the way to go.
its CS > Execute (stacks to 5, refreshes at 3 sec) > Mortal Strike > Execute if nothing else > Return. Is that what you wrote too? Glad you like it I think its good aswell atm, and i dont have any further update plans for now either! Everything seems to work out alright.
Should be: Execute (if Executioner < 3 seconds) > Colossus Smash > Execute (if Executioner < 5 stacks) > Mortal Strike > Execute This is the correct execute rotation, and i think it's the one you got. I'm planning to remove the charge/heroic leap ability from your cc plus remove the cooldown usage like recklessness and blood fury. This is so that i can have even more control over my character, i don't like the fact i'm already running to another mob the CC charges the one i'm targetting cause i failed to select the target i was moving to Removing cooldown usage like recklessness allows me to turn them on when i really need to.
Editing CC's for personal use is of course allowed! Nothing i can stop you from doing And of course, some want the leap + cd's in the CC others dont! Those who dont can just edit/delete it Personally I dont mind it using CD's or leap/charge. I hope it lives up to your expectations!
It is already living to my expectations By the way Shaddar, if you have time to spare read this -> 4.3 Arms PvE Guide - Forums - World of Warcraft Found it just now and it has lots of information regarding rotations, single and aoe targets.
I've already read the theory crafts in Elitist Jerks and Mmo-Champion mate I wont be reading a third! haha
The post there basically reflects what is said over at EJ but it includes gear listings and stuff is all.
Do you mean Code: private bool IsTargetBoss() { string UnitClassification = Lua.GetReturnValues("local classification = UnitClassification(\"target\"); return classification")[0]; string UnitLevel = Lua.GetReturnValues("local level = UnitLevel(\"target\"); return level")[0]; if (!Me.IsInRaid) { if (UnitClassification == "worldboss" || (Me.CurrentTarget.Level == 87 && Me.CurrentTarget.Elite) || (Me.CurrentTarget.Level == 88)) return true; else return false; } else { if (UnitLevel == "-1") return true; else return false; } } Becuase thats already implemented. The only cooldown this CC use when your not engaging bosses is "Deadly Calm".
Thats an easy fix. I can upload an update when i get home. for now you can just manually edit the file. Just change: Code: (Me.CurrentTarget.Level == 87 && Me.CurrentTarget.Elite) || to: Code: (Me.CurrentTarget.Level == 88 && Me.CurrentTarget.Elite) || Or even higher if you prefer that.
I'm gonna make some modifications of my own, if i can with Shaddar's help, something like delaying overpower and slam if colossus smash or mortal strike cooldown is inferior to one second. And to not cast Colossus Smash if the boss has Colossus Smash debuff (i think it's a debuff or maybe it's a buff, dunno really ), removing cooldown usage like Recklessness, Blood Fury, Charge, Heroic Leap and trinkets. With that it would be sheer perfection.
If you have already applied Colossus Smash to the Target, it doesnt cast Colossus Smash till it wears off. Thats already implemented in Titan Arms. However I dont see the need of delaying Overpower/Slam as Colossus Smash has higher priority then both of them to begin with and should favor CS -> OP/Slam. Removing Cooldown usage is just to delete the lines below /////////////////////////////////Cooldowns are here//////////////////////////////// Hope that clear things up.
Sorry, i haven't make myself clear... it's a gain of dps if you hold overpower or slam, if colossus smash or mortal strike cooldown is < 1 second cause of the gcd. If you hold these 2 abilities... it will use mortal strike right when the cooldown pops up, the same for colossus smash... that's an increase in dps according to all the forums i read.
