Cheers Phelon. It kicks now and then, and i have stop everything to get the kick i want. before it just kicked all the time, and it worked perfectly. give me a PM in inbox aswell, i want to pay for the help. I didnt pay for support. View attachment 173914
I added a GCD check so it wouldn't spam it. I will maybe add a GCD Check to the Interrupt list so you can tell it to use off GCD Is Rebuke is on the GCD isn't it? I don't really do live support, even for money unfortunately (as that is not allowed). I will how ever take a look at your logs. Edit: You will have to delete your Interrupts.xml as of the new update and remake it since I added facing check.
NOTICE: You will have to delete your Interrupts.xml as of the new update and remake it since I added facing check.
Hello Thanks for the help man, i appreciate it. Rebuke has no GCD. you have to add this GCD check ON/OFF cus right now i can kick better then the bot, i play at 2.8 mmr+ and i really need the bot to kick when i want it to kick, like before, now i dont know when it will kick, or if it will kick, its kicking so randomly. and i really enjoyed the bot when it kicked right away, while i was bursting people and stuff. i didnt need to stop everything i did, for landing a kick. GCD for Rebuke = 0 second. It's just my way to say thank you for the help. I will try this out, i will get back to you lets just say its a donation
I agree with the post above, the kick bot is just randomly kicking now, it used to kick spells like Penance for example instantly, but now it's just terrible.
Sorry for posting again. But it still doesnt work for me. I think it has something to do with detecting the cast. I set all my cast to interrupt after 500ms. Sometimes it works fine, other times it misses the interrupt. Im running with 60 tps. That should be fast enough i think.
Thank you for the input. I am going to remove the GCD check for now. HelloKitty expect a PM from me. I Think it might be the same as above but try enabling Account for Latency in the config and see if that makes a difference.
Sorry for posting so much, but since the update the ultimate interrupter settings no longer opens, just thought I'd let you know.
See the post 4 up in red? =) Since I added some stuff you will have to delete the Interrupts.xml and start over. I will add something for that tonight to delete it for you if it fails. Thank you for coming to report it either way, I do appreciate it!
Sorry xD If an off target is casting that should be interrupted. It works when the hitbox is overlapping with my current target. That would explain why it works almost every time on fanspore. Because the add is standing the large hitbox of the boss. My other theory is is that there is problem with with hitboxes and the range settings. In pvp the hitboxes are always the same i guess. But in pve the hitboxes are varying and with that the range ? Btw i still have the missing interrupt issue with account for latency is checked. Can you make it switch back to my last target after kick pls? I also have a another question. The two new options Face Target Caster and Target Caster are working independently regardless what i set my interrupt spell to? (TargetAny and Facetarget)
1. So you mean it doesn't account for hitbox size. I get it, I am adding code for that now. 2. The 2 new options act independently of the target any. It will target what ever it is supposed to interrupt or face it depending on your settings.
Ah just edited my post with the hitbox thing xD. Thanks again for looking into this. What about the thing with target switch back? And can you please explain how the random option works in delay. Does it choose a random interrupt time taking the cast time into account or by varying the delay time? If yes how much does vary?
Switch Back.. I will look into but make no promises. Here is the code for the randomization: Code: randomDelay = rand.Next(150, 500); latencyDelay = Convert.ToInt32(StyxWoW.WoWClient.Latency); CurrentCastTimeLeft.TotalMilliseconds < x.Delay + randomDelay + latencyDelay
Thanks. I thought about the switch back. may be you can add some slight delay. to make it not to look too botish. x.delay is the delay set for the specific spell i guess? If i get this right randomtime can only be positive. Maybe you can make the range from negative to positive. And add some safety value. So delay time doesnt get too high or too low to prevent instant kicks and missing interrupts. How do you compare for casting target and target switching? By name or by guid?