Lazy raider is what I am using with newest version of stable honor buddy. Edit: I will try a fresh HB install a little later Edit: looking at the log [04:00:55.356 N] Not Facing Target happens multiple times which may be the problem because movement is off.
I am encountering some major issues with stealth using this CC. HB version: latest stable release Bot: Questing Profile: Kick's Jade Forest Spec: Assassination Level: 85 Setting it to always stealth looks weird and botlike, because it then stealths IMMEDIATELY after combat, even before looting! But looting breaks stealth. So it stealths, bot loots, then that breaks the stealth. Stealth goes to CD and bot moves on to next mob, often reaching before stealth is off CD. Is there any way to get the bot to wait until AFTER looting to stealth? EDIT: Inconsistent stealthing was solved by upping the pull distance from Kick's default of 25, which was way too low. 45 works fine.
Can you possibly add in a DELAY before it stealths after combat, allowing enough time for HB to loot before popping stealth?
Ok, so today in my guild raids I noticed it was energy capping, Focusing on working on this issue ATM.
I will let you know if fresh install works later. The amount of times this was shown seems like the amount of lag spikes that occurred. Something changed within the latest release when I asked for the option to disable auto facing the target. Ever since then it has done this. Is there a link to that version I can test later if the fresh install does not work? Edit: Updated with a log using a fresh install of honor buddy. The last fight on the log I re-enabled movement and the lag drop was much worse. Edit 2: Second log is the standard singular with no lag loss not sure if it helps. Thanks for the effort don't spend to much time on just me if nobody else is having the problem. Everything in class config unchecked except for Recuperate using lazy raider
By checking your logs i dont see anything wrong. Quick cross checking your logs with mine, everything look exactly the same. Only thing that i noticed is that you are using Dx11 while i use Dx9, try using Dx9.. this is only suggestion that i can give you atm untill i get home and check logs a bit deeper. __ Sent from S.ony Tab S via Tapatalk
I am reworking the code. Seems to delay or get stuck while tuning some code. Will work on an overhaul this week.
Thanks for the reply, as for Dx11 I have a nice high end machine 3930k, 32gb ram, gtx 670, I dont feel I should sacrifice quality of the graphics because it was working fine before. (for altec) Why with movement off is it still trying to face the target according to log? shouldn't this not be in the log at all with movement off?
That is because you are outside the 70* angle for attacks. It should be 110* but I didn't change it, now that I look back.
Hum, I need to clear my inbox out. Thanks for reminding me. I doubt I have a decent sub version not tied into my 3-in-1. I'll take a look.
you need to make rupture optional, mobs are dying on my grind profile before it's even been on about 5 seconds, waste of CPs
Did you not read the first post? Changing this routine massively. The last version released got bugged. Re-coding and Re-testing before I release a stable version. All I have currently is Combat Spec with little to no options to adjust, and that is still in coding stages before releasing for beta testing.