In software development, you generally don’t want to make too many changes to the code before testing. Otherwise, when it breaks, (assuming it’s not a blatant syntax error), you’ll lose track of what, exactly, caused the new issue. It’s slower… but to make one change, and then test it, it’ll often be easier to identify the cause of the error.
Banning too frequently gives them invaluable information to work with - knowing how they were spotted, and what’s working, or not working, in evading detection. If they’re banned, we don’t want them to be able to infer how, or why.
On top of the observation to get more evidence and bots, we really do want to do them in large, silent batches, to keep their evolution to a minimum. It’s less harmful to let them bot for awhile longer, than to accidentally create “super bugs”, as an analogy to the problem of antibiotics.
CCP can’t really win here. From a technical perspective, they want to be as silent and infrequent about it as possible… but in the meantime, they come across as indifferent or ignoring the problem.
This thread will run the typical “OMG Bots!” storyline:
Acusation made; sometimes data in the form of screen shot/ video included.
Further anecdotal evidence presented by other players; sometimes more “proof”.
A smattering of CCP loyalist/botters/naive players post counter arguments.
Thread churns through at least a couple hundred posts.
CCP remains silent.
ISD shuts thread down or combines with an existing one.
…and EVE continues the old status quo and don’t expect PA to make any changes. Sad, but probably a fair predictiction.
Yet they can port botters directly to Yulai for people to kill…that doesn’t protect the botter’s identity or the identity of the alliance that condones botting. They have already proven that they don’t care if the players know who bots.
All of that just shows that they are not doing anything vs bots in any great number.
at men