Warriorus Very simple CC for assisting a Fury warrior in Dungeons/Raids/BGs. Built on new TreeSharp technology. It was just my attemt to understand TreeSharp better. What it does: - Fury rotation (CS-RB-BT-Slam-HS) - Some PvP stuff What it doesn't: - Move - Face - Anything that may interrupt yours control Installation Unzip Warriorus.zip to your custom class folder Choose blank profile in your settings Start up honorbuddy, log in, and start Combat/Heal bot. Please consider this as a test release, this wasn't tested much and should contain bugs - please report them. Thanks to Nesox, Apoc, fpsware, Truman422 for code, exaples and other stuff! SVN: warriorus - Revision 13: /trunk Please use SVN for most actual version! V 1.0.14 rev. 14 - modified rotation (should do better DPS now) - RESOLVED bug with Slam not working rev. 6 - changed TG rotation for better DPS rev.5 - clean up - added self healing with ER - Heroic Throw for PVP rev.1 Initial realease
Slam bugs out everytime... i don't know why, but after one proc HB doesn't detect it, so it's kinda fucked up with not casting Slam at all. All warrior classes - Singular, Gladiatore, Champion of Aldeeran suffer from that (bug?). And do you mean change RB and Slam, because I thought smf rotation is - CS-BT-SL-HS-RB. And maybe I'll add this later.
if you are testing in a dummy yes it will bug out... but in raids heroics it works.... it doesn't do it instantly because it isn't suppose to but it does it. and for smf i thought everything was the same except rb and slam and hs is last prio just used to dump rage
Q: What rotation should I be using for Titan's Grip? A: Bloodthirst -> Raging Blow (use Berserker Rage to activate if necessary) -> Bloodthirst -> Free GCD. Colossus Smash between Bloodthirsts, delaying Raging Blow if necessary. Use Slam only when you have a Bloodsurge proc during a free GCD. Heroic Strike should only be used at 90+ rage with a threat of capping and should be lined up with Colossus Smash as much as possible. Q: What rotation should I be using for Single Minded Fury? A: Same rotation as Titan's Grip. However, Slam is more important to SMF than Raging Blow. Prioritize accordingly. from EJ
Hmm, maybe i need to adjust my TG rotation according to this. So its more like BT-RB-CS-Slam-Heroic. Really long time i didn't play my Warrior ^^ I'll look into this. Thank you!
i think hb isnt detecting slams right ... my smf rotation on gladiatore isnt working right now... it doesnt detect some slams at all its frustrating cause it isnt throwing an error.
rather troubleshoot the cc before placing blame as it should be working fine, although no thrown errors but thats off topic... anyone here else test this cc out ?
It's about HB bug, not CC. And I have reported this twice. Seems HB doesn't detect some auras for some reason. Yes, there is an add detection if you have more than 1 target infront of you, it will do AOE stuff (WW, Cleave)
rev. 15 - modified rotation (should do better DPS now) - RESOLVED bug with Slam not working Get from SVN =)
ups, a bit overhead ^^ rev.14 is the last one, so slam is fixed in 14 I really need to know Arms rotation and priorities, because after one year pause, seems everything changed. Eventually, I'll relase Fury/Arms/Prot CC. Next release I'll add smfury
Priority list. Hamstring (if not applied) > Rend (if not applied) > CS > MS > OP > OP > Slam > HS Burst Damage Output / Make sure rend is on the target and Lambs to the Slaughter has full stacks / Ideally you want to fit a CS -> MS -> OP -> OP in with as many HS uses as possible without rage depriving yourself. Remember to not use CS when low on rage, it doesn't hit very hard by itself and if you can't use other abilities while the ArP is up on the target there is no point Also, does your CC immediately rip off bubbles?
Mind informing us how you fixed slam, I assume the bug was the detection of BloodSurge? Good work btw! Not placing the blame on anyone. I just wonder if one of the CC programmers actually reported that the detection of bloodsurge in HB is somewhat buggy. It seems that Ilyals found a work-around or a fix in rev14. Will test is out soon.
Yes, it was a Bloodsurge. "The fix" was suggested by Nesox. It now uses SpellID instead of Spellname to detect Bloodsurge proc (plain simple and working). No, because Shattering Throw requires Battle stance and I really don't wanna do any stance dancing by a bot, but I should think about it.
