I've been searching around the forums trying to find guidance on how to implement antibans or antipatterns into my bots but every thread I find seems to say that it's almost as bad to implement it as it is to just keep it out. In my case I have my bot that does a task consistently but im not sure what to add for "antiban". It'll never stray from the main decision tree nor is super random in what it does.
Tutorial - Use custom PlayerSense keys in your bots to simulate different playstyles across your userbase Tutorial - How, and why, to use the PlayerSense API PlayerSense is the main form of "antiban" used on here. Most bots tend to not support traditional form of anti-ban (execute a random movement (camera change, click, ...) between x and y seconds) , since it's believed to generate a detectable pattern.
Oh I should've mentioned besides PlayerSense as until I get my bots to a certain degree of reliability and not as botlike, I don't feel comfortable releasing anything publicly. What do people refer to then when they mention "antiban" in their descriptions?
One of the best 'antiban' features is having a bot that gets the job done without any hiccups (e.g., random walking, spazzing out, infinite action loops).
