localization client.... maybe.... this CC not working in localization client. (tested korean client) this is log... View attachment 1552 2012-12-20 04.14.txt
Ok, update 1.3.1 - Fixed a bit of errors, starting from here on out I will release a beta version before removing the current stable version. Took out the startup rotation for combat spec, that code is still being improved upon. I need to get it down before trying it again.
hey altec, i updated the svn folder yesterday and saw the 3-in-1 routine only tried the assassination spec wont work at all. If this is fixed in the new update 1.3.1 then just ignore my msg ^^
Not sure what the deal is and I am probably just doing something wrong. However it seems that it has a hard time doing early level questing. It appears to get stuck pretty easily and target things it shouldn't. This might be the profile I am using but when I switch over to Singular it doesn't appear to have that problem. For low level questing I don't think using Singular is a bad thing, will try this CC again at later levels and see what happens. Like I said, have not tinkered with it much but thought I would give a heads up to people questing in the 1-60 range (where I am currently at). I have read that it is not a stand alone CC as well, might have changed some but like I said, I might be wrong and just not setting it up right or I might be trying to use it for the wrong purpose all together.
From the little time that i had to test it, CC for combat rogue is working flawlessly. I did, however, managed to reproduce "movement bug" that i mentioned few posts back. Movement bug is caused by "resting" part of code, when you are below 65% of HP and you dont have anything to eat. Its forcing bot to stop in place, and since your trying to move, it will stop your movement after few steps and try to rest. Now, this might be an issue in raid so, it would be nice if you have little time to implement in UI setting option to disable "resting." I fixed it for my self by disabling this part of code, line 132: Code: public override void Rest() { if (!Me.Mounted && !Me.IsMoving && !Me.IsCasting && (!Me.HasAura(ARSettings.Instance.MHPoison) || (Me.HasAura(ARSettings.Instance.MHPoison) && Me.ActiveAuras[ARSettings.Instance.MHPoison].TimeLeft.Minutes < ARSettings.Instance.MHPT)) && CastMeUp(ARSettings.Instance.MHPoison)) { Logging.Write("Applying " + ARSettings.Instance.MHPoison); } if (!Me.Mounted && !Me.IsMoving && !Me.IsCasting && (!Me.HasAura(ARSettings.Instance.OHPoison) || (Me.HasAura(ARSettings.Instance.OHPoison) && Me.ActiveAuras[ARSettings.Instance.OHPoison].TimeLeft.Minutes < ARSettings.Instance.OHPT)) && CastMeUp(ARSettings.Instance.OHPoison)) { Logging.Write("Applying " + ARSettings.Instance.OHPoison); } // if (Me.HealthPercent <= 65 && Me.IsAlive) { Styx.CommonBot.Rest.Feed(); } } Also, same thing is happening again with leftover CPs after battle, CC is trying to refresh more powerful, active, SnD with inferior SnD (less CP's) instead of casting Recuperate. Now small suggestion and reminder. It would be good, when you have time, if you can implement that CC "Kidney Shot" uninterruptible spell casts (like mobs channel spells (for instance Rare Panda mobs Spinning Crane Kick)) and add it option to UI since it would be pointless for CC to try to Kidney Shoot a boss. Reminder: I asked you few days back for Combat Rogues "Combat Opener" (5CP's SnD and Ripture) code and to tell me where to implement it, i would like to test it with current Revision. PS. U have beta tester right here, so if you need one, you can count on me.
Would it be possible to add override keybindings for movement? E.g.: When w, a, s, d or arrow keys are pressed, we are actually able to move the bot although "Enable Movement" is ticked in the options? I'm actually using your CC with DungeonBuddy as a follower for my tank (hand played) and it would help tremendously if we were able to move the rogue out of aoe effects (because DungeonBuddy isn't able to do so itself). Btw, v1.3.1: Config - General: SB are ticked Config - Combat: AR + KS are ticked But if I don't enable "Always use cooldowns" as well, it won't use these three cooldown ever, even on boss fights?
Boss checker only checks if target is a raid boss. Ie skull instead of level. Again, I have not optimised this for leveling yet, still working on the bugs or has. Will add that soon though, the leveling dungeon boss stuff. I was thinking of adding a detection for bad aoe and move out of it. Will add some type of override like you mentioned soon as well.
Yea sorry about that. I know you're willing to beta test, and for that I thank you. I will be adding beta versions to the svn from now on, just wanted to push a stable version for everyone else to keep enjoying without bugs. I am going to add in a check to see if first the player has food before trying to use it. Should fix that issue. I have not yet changed the code for using CP's after combat. The reason for not using recuperate after combat is because it is coded: if your hp is greater then what recuperate's HP% is in the GUI, it will not use it. The reason I removed that startup code was because it was freezing the routine. I need to fine tune that code, which is what I will work on, before releasing it to stable. I will add KS as you mentioned as well, that and add in a check for bad aoe the bot is standing in. This should make it look smoother.
This CR has nothing to do with targeting, well to an extent. This CR only runs when you get into combat, with a few non combat checks, ie your poison check or food check.
Hi, As Altec wrote, this is mainly CR that is build to be monitored, so you cant use it, at least not with great success, for leveling. You can mark "enable movement" and try using questing bot, but im pretty much sure that you will end up standing in one place after mob is killed or leveling would go really slow. Personally i used http://www.thebuddyforum.com/honorbuddy-forum/combat-routines/all-one/76780-fightthisway.html with some edits for leveling since Poisons are working and it has good AoE surv, but alas it blows ALL your CDs in one fight, and switched to Altec's as soon as i hitted 90 and i can highly recommend it to you, no matter what CR are you using, switch to Altec's as soon as you can.
Easy, just un-check enable movement, that will stop the CR from moving your character. I am not quite familiar with Lazy Raider and such though.
Thanks, but it is unchecked . The problem is when questing and lazy raiding I often need to turn around to do something other than fight the mob I am on. As soon as I turn the character he spins back to attack the mob. May not even be a problem with the CC, but the way lazy raider works. Basically makes it tough to run away if I need to.
