Is it worth even adding an 'anti-ban' to a script?

[Minted]

From what I understand, the OSBot API has an AI mouse moving function, so that the developers don't have to code it. From my understanding, this would mean that the movements wouldn't be linear, or teleporting across the screen. I have also discovered the 'anti-ban' 

 

What are the needed features of an 'anti-ban'?

I don't quite understand what the 'anti-ban' system a developer would put in place actually does - whilst the name obviously states that it's gonna stop you from getting banned, but what kind of things does it do to prevent that?

I assume it changes your camera yaw, AFK delays, move outside of screen, change the mouse click delay? I'm really not quite sure.

 

Why is it optional in most scripts?

I have used multiple scripts by @Czar which have the option for to enable anti-pattern, which I don't quite understand. Surely you'd want this on? It's just an unneeded option from what I understand.

 

Any help would be nice, I would like to extend my knowledge. My friend @Tacts is developing a script which hopefully the community will enjoy, and will be on the SDN.

If you'd like more information on said script, check out this thread: 

 

Thank you!

[SqueezeTheorem]

Anti-ban is largely bullshit, and a marketing ploy. Based on what I can tell, the current bot detection system uses a combination of machine learning, statistical analysis, and even manual review to catch bots. However, there are some legitimate anti-ban techniques that can help you avoid being banned, but a lot of what you see is nonsense. 

The most promising form of anti ban (based off of my own experience) seems to be:

• Anti-pattern (not taking the same path every time, varying delays between actions, etc)
• Novel behavior (Doing weird shit to accomplish a common task, not doing a task in the most efficient or straightforward way)
  • I once made a mistake with a f2p mining script, and left out one of the tin ore IDs, so the bot only mined roughly half of the ores at barb village. To my surprise, I was able to suicide bot up to ~60 mining without a ban as a level 3. I have my suspicions that my mistake of leaving out some of the ore IDs was such a bizarre behavior that BotWatch had no comparable behavior to compare it to. 

I'm doing some experiments with this sort of stuff right now trying to find out what's the most effective approach. 

Edited February 2, 2019 by SqueezeTheorem

[extatus]

if it serves its purpose, yes, but i would argue that most antiban is indeed useless for the fight against heuristics.  Just pure marketing, as Squeeze said.

 

 

[luciuspragg]

What are the needed features of an 'anti-ban'?

At the very least some kind of anti pattern, which is essentially just not doing the exact same thing the same way over and over again. Use random breaks between actions, different banks, paths, varied spots/pixels/colors etc (though this one isn't necessary with osbot). This is one of the reasons using a basic autoclicker (e.g clicks once every second) is a bad idea. 

 @SqueezeTheorem was saying novel behavior, which I agree with. This is one of the harder things to add to a script because it's difficult to know how much or how little you can get away with. A human won't perform every task perfectly or might do stupid little things for absolutely no reason and it's almost impossible to account for every single one of those little quirks that can arise when a real person is playing. When crafting or cooking maybe they'll interact with a different item each time without an easy to guess pattern, or they'll attack the mob across the room rather than the one that's closest for literally no reason, they could be alt tabbed during a level-up and not resume the activity immediately etc. I've found in my personal experience that more "goofy" scripts result in more time before a ban.