Just updated via SVN and expose armor and shadowstep dont seem to be used. Even the previous revision the shadowstep didnt work at all.
No. It will only use CD's when you are in a party and the target is a boss. To test solo on the dummies, enable always use cooldowns.
Altec - Thanks for working on this. This forum is in desperate need of a solid Rogue CC. Especially with the buggy Singular (poisons, etc) and the general frailty of rogues now a days a good CC is priceless. Looking forward to updates!
hi ty for work im use combat on asasin and off movement, but his move and move fase on boss, can im off it?
no, atm it doesnt stop to eat/regen. Altec will prolly add it. Im using 3-in-1 routine for combat/sub (since they both share same stat prior/reforging/enchanting) and with "use movement" turned off i only find CC facing boss/rare/normal mob from time to time when i try to get out of range. Maybe ur using some plugins for HB that glue you to your target, like "iGlue." Altec, i must praise your AoE detection part of routine, its working fast, however, i found a small bug.. If i attack mob and another pack one joins fight, so its 4+ mobs, it will auto turn on BF and start FoK rotation, keeping its single target rotation going on main target, as it should, but, even if i move a little and im still in AoE melee range of mobs (maybe lose one target) it will disable BF and continue rotation without it, re-enabling it after CD (or instantly if its not on CD).
Yea, it is almost ready for an update, been working late and going straight to bed when I get off. Anywho, blade flurry in itself was hard to get to work properly. I might know of a good fix for it turning off.
Thank you for your replies and support, but also for updates that you are doing despite your busyness in RL. As it is now, 3-in-1 CC for combat rogue even in current beta is performing really well so there is no need for rush, RL comes first. Keep up the good work, i really hope that your routine will be "the one" for rogue class.
Ok, new update here, 1.3! Added in a "start-up Rotation" check whenever you obtain a new target (single target only as AoE was just that, AoE...) I can foresee a possible bug with this but I will address that down the road. Removed the solo combat routine options (assassination / combat / sublety) since the 3-in-1 has all three inside, it was taking up useless space. Added in food option to eat when your HP% is below 65% (will add in an option for this at a later date so users can decide when to eat the food).
New rotation doesnt use slice and dice at the start combat, and since we want SnD up near 100% imo new rotation looks bad. Also with the old rotation i'd get around 900dps with lazy raider with me playing manually i'd get around 1700 big increase.
I'm using Assassination and having problems with the new version initiating its rotation at all... just seems even more buggy with the new update. Ahhh I need version 1.21 back
Combat rotation seems more fluent and better, getting close to what it should be. Now, for few bugs, first 2 are really nasty ones: 1. HB with Lazyrider as botbase: CC just stop working from time to time. HB with Lazyrider as botbase are running without any errors, but CC isnt doing anything. Further checking and testing led me to believe that there is a bug when CC is switching from AoE to Single target rotation when it needs to disable BF. This is most easily noticeable on second and last boss in "Stormstout Brewery" dungeon when CC needs to switch from single target to AoE and back to single target during one fight. To fix it you need to stop HB and restart 2. HB with Lazyrider as botbase: CC settings "Enable Movement" - disabled. Strange movement bugs, CC is, from time to time just keep bugging and making 4-5 steps and stop. Example: I hold my "W" button to move forward, CC makes 5 steps and stop, i need to release "W" and press it again to move another 5 steps. This issue fixes it self after 6-8secs and you keep moving normally after that. No errors in HB log whatsoever. 3. HB with Lazyrider as botbase: CC settings "Kick" - Enabled. CC doesnt use Kick at all. 4. HB with Lazyrider as botbase: CC "Recuperate" settings set to 65%. Doesnt use Recuperate at all. 5. HB with Lazyrider as botbase: After combat ends, you have extra CP left and SnD buff on, CC is constantly trying to use CPs that are left after combat on SnD, bugging it self in loop if more powerful SnD is on. It should cast Recuperate if you are out of combar, have extra CP left and SnD buff active instead of retrying to cast new SnD. 6. I see that currently CC allows SnD to fall off for a few secs, even when it fall off it doesnt try to refresh it with any CP at disposal. I guess that its not possible to do 5CP SnD opener and then refresh it with any CP left since code will detect "SnD opener" as missing buff and refresh it, so its either 5CP SnD or refreshed with any CP at disposal, it cant be both. So, practically, its not an bug. Currently im only playing combat, so i didnt had chance to test rest 2 builds, but i presume that errors affect them all.
Testing a new rotation, and this is endgame optimized. Have not changes it for leveling rogues. Nothing about assassination spec was changed since 1.21.
Not sure about movement bug, will look into this. Slice and dice opener does not get detected during regular combat rotation.
Check my previous post, added some new bugs, attached log from SB and some screenshots that shows that HB is running but it stopped. "Error1" and "Error2" are both bugs where CC just stooped working with HB and Lazyrider still running. "WoWScrnShot_121912_170432" is a SS of a bug where CC is trying to refresh more powerful SnD with inferior SnD (less CPs) with leftover CPs, instead using those points on Recuperate Also, notice that SnD is far from its refresh timer (3sec before exire) so, by default it should cast Recup. Log file is from "Stormstout Brewery" dungeon when CC stopped working mid combat. I pressed "Stop" and then "Start" again but soon after that CC ended up bugged again. HB and Lazyrider were running, but CC was crashed and it wasnt doing a thing (thats prolly what ppl think when they say "having problems with the new version initiating its rotation at all.."). As you can see, im in combat (auto attacks and DP tick, but i have full energy since CC stopped working while HB and Lazyrider were still running (thats why it says "honorbuddy stopped working" while i have a button "stop" instead of "start").
Yea, going to keep current version in the svn and add the beta to be tested, so if there are any issues with beta people can still use this routine.
