Second Account Banned

[Lutt3]

Hey! Just came back from work when i noticed that my account had been banned.
This is my second account that is getting banned and i dont know if im doing something wrong or if im just extremely unlucky
When i went to work i started questing bot with kicks profile classic (A) 12-58 was in STV and dont know if i got stuck and did something really noticeable..
All other days i use my bot about 3-8 hours a day and using Lazyraider, sometimes i also use proffesionbuddy but i dont think it can be because of that?

I'll probably buy a new account and I was wondering if you had any advice for further use



Log Attachment Here's my latest log if you wanna check

 

[Undivine]

When i went to work i started questing bot with kicks profile classic

Not trying to be mean, but if you turn a bot on, then go to work, you should come back expecting your account to be banned. I'm only saying this because I have to suspect most of the folks posting in the 'Did you get banned because of Kicks' poll thread have used it in a similiar manner. No bot is 100% AFK'able for extended periods of time without serious risk. Read up on the 'avoid bans' thread and best of luck to ya!

 

[x11r6]

you got unlucky man. Be sure to change IP when you get banned, or you'll end up being banned very fast the next time you bot, i can assure you

 

[DJKid]

Any public profile you use increases your odds at getting caught, especially popular ones. Kick seems to make the most profiles from what I've seen, because of this a lot of people are blaming Kick's profiles. Profiles will almost always do the same thing for everyone, follow the same path, take the same quests in the same order, sell to the same vendor (even if there is a closer one). Little things like this can make it easier for wow to pick out the botters. And on popular profiles, you have thousand of botters doing it across multiple realms, making it more obvious that anyone using that profile is botting. But who is to say this is how you got caught? Your character could have gotten stuck on something and ran in place for a while. There is a number of things it COULD have been, and we're all just guessing without seeing what Blizz saw.