lumberzach

I had this issue and even turned off lua to move and only used click to move to try and stop it, eventually I did a fresh install of wrobot and it worked. I am not sure what the automation product is, but maybe it's that? I only use the Quester and specifically only use grinding profiles. I made a second account and tried using the fisherbot, and for whatever reason it triggers the afk warning and kicks me so maybe it's not only tied to movement

For those with this problem in the future, it was addons causing it to crash, disabled all addons and it works.

I was able to run for about 12 hours yesterday, but today when I launch it and it tries to attach to the wow process, it gives that error. I made sure all firewall/antivirus stuff was still disabled. Did a PC restart and still nt working. Here is my log Any ideas? 18 Nov 2025 08H51.log.html

Nevermind, a GM slept me today and told me to stop triggering the anticheat, no ban but she said to just turn it off and don't use it again.

This seems to be fixed after a restart

I have Lua Movement turned off and CTM on but it still happens. Anyone else still getting this issue?