The primary problem with this CC is that it doesn't detect the bosses hit box well enough so it can't do the rotation unless you are literally inside the bosses hitbox. Not only that, but it auto-declicks whenever I try to use heroic leap.
you can change the hit box in the settings config so u can hit the box i normally change from 15 to 100 for big bosses like nef or alakir ... heroic leap was enabled in previous ver 3.2 but there was complaints it was buggy (using heroic leap on its own without having it enabled) so he removed it. But i have noticed if u arent exactly close enuf to a target n bot isnt attempting its rotation you should be able to heroic leap across the room to set of mobs to kill or running away from something just declick ur target first as well.. but there is no hit box problem just use the settings config.
I am not looking for it to heroic leap on it's own, but just be able to use it on my own like I can with the Singular Warrior CC.
I can add it back in but I'm currently trying to see if I can start a new thread and start up full development again with original author permission.
Nice! Also, with haste being implemented, the bot doesn't spam the actions quick enough imo. Can anything be done for this? Thanks!
Yay! And if you can add so it uses pvp-trinket when you get cc'ed by an enemyplayer would be nice as well. Happy to hear someone still cares for this CC and wishes to improve it <3 It really makes it easier raiding.
For example, the Bot has enough Rage and Mortal Strike just came off CD. But it often waits .5 miliseconds before actually activating it because it is too slow - even with wow's in game latency at 50. [note] - do not confuse this with Colossus Smash up time optimization as explained below. It needs to be slightly faster on key presses to maximize rotation. Also, It should never press Colossus smash unless Mortal Strike is (or almost) off cool down. That way it can maximize Colossus Smash uptime which is a substantial DPS increase. The same thing applies for SMF Fury and Bloodthirst. The goal for Arms (for example) is to get off 1 MS + 2 OP + 2 Heroic Strikes all in one Colossus Smash. Which means the Bot doesn't want to Heroic Strike right before it Colossus Smashes, it wants to have roughly 75 rage then be able to implement all of that for maximum DPS. Until a CC can do that, the warrior class is not working completely as it should.
Sounds about right. daorigin, have you had any luck on getting the Okay to start moving forward on updating this CC?
Both fury specs do absolute perfect raid damage, I know of the delay you speak of and yes I did receive the okay but the optimization you ask of may actually may require to rewrite the entire cc as a whole, something funny bout that request itself because the original author is actually already working on that. So for right now I'm just going to release the fixes I have made to arms ie demo shout bug/ pummel not working. Also try to figure out why hb misses slam procs although saying it did slam
Sadly no timeline given and I wouldn't ask for one, did say it was halfway done and if anyone has skimmed through the lines put into this cc they know it's a lot of coding. Patience will be rewarding. I'm still not in front of a pc until tomorrow thats when I'll toss up another minor update for bug fixes and re enable the heroic leap detection that worked in 3.2
Im checking in on this thread all the time, thanks a million to daorigin & those who keep it alive <3
This bot often isn't using Colossus Smash on CD. Also, I've seen it actually use Battleshout when CS is up. That is a HUGE dps loss. testing all this as SMF fury.
I've noticed that the CC stops doing rotations and just does nothing while certain raidbosses. Nefarian and Al'Akir are the ones I've had problems with. Pressing stop/start doesnt help.
If you read one of my previous replies, just go into class configuration and change the range on your rotation in the bottom left from 15 to 100 (max allowed) and you will find your warrior being epic again.