@
Incurable; is correct on our, Clarity and I's, stance. ogLib, for one, doesn't use mouse movements.
I think user agents play a part. We rarely hear about bans with ogLib, with its lack of mouse movements, but a few weeks ago we heard about a lot - I got hit with 3 bans out of 19 running farm accounts (DarkScape). @
Lucidity; then returned from the dead and sent me a message along the lines of, "So I noticed SMART is using the user agent
abc?"
Apparently a test file that was sent through Skype to Clarity, Ross, and myself was pushed to Github. We fixed it to use a random user agent
here and such reports have stopped and we, myself included, have been smooth sailing since.
Like has been pointed out, I think scheduling breaks is key.
Also, you'll find that in a lot of ban reports, they occur with more then 3 accounts per machine.
There's also a few things I make mine do:
- Randomly talk. Send an SRL friend (who may also be botting) a PM like, "Oi, check Skype.". If cutting a tree is taking forever, "Really Jamflex?..."
- Schedule breaks based on local time (like dinner).
- Even if taking 15-30 minute breaks, don't bot for 12+ hours straight. 8 hours, break an hour or two, repeat.
- Make it react to the public - watch chat for all or part of your name.
- Never run more then 3 bots per machine.
Etc.