A couple of weeks back, we released a Dev Blog detailing a few changes to how Team Security is now operating and what the focus will be for the team going forward.

This news item is the first regular update that we’ll be providing to give more of an insight into the ongoing fight against botting and other general nastiness that occurs in New Eden.

Firstly, a few raw numbers!

February 2018 has seen the following in terms of account action from Team Security. Of the 1882 bans issued in total this month:

  • 896 bans related to account hijacking.
  • 511 bans related to macro use and botting.
  • 253 bans relating to ISK selling.

Changes To Account Restrictions For Botters

In addition to bans issued this month, we’ll also be increasing the level of account restriction that those who’ve been reprimanded for botting in the past will face going forward.

Currently, accounts that have served temporary bans in the past are locked out from character transfers. While they can receive characters, they are not permitted to send characters to another account to prevent evasion of further reprimand.

With the March release we’ll be extending restrictions so that these accounts will also be unable to extract skillpoints. This further reduces the ability of those who’ve previously breached our rules to be able to avoid further reprimand.

This change comes off the back of discussion with the community and was suggested by pilots as a possibility for toughening the stance on those who chose to break our rules on input automation.

Clarification On Section 18 Of The Terms Of Service

In the discussions following our communication on botting, bans and other reprimands were discussed and some players brought up section 18 of EVE’s Terms of Service which states:

“You may not publish private communications from CCP, their agents or representatives or EVE Online volunteers without authorization.”

Whenever this clause is brought up, it’s obvious it carries with it a couple of misconceptions that we probably haven’t worked hard to adjust. Some argue that we set this rule to hide what happens between us and players, which is not possible and is absolutely not our goal.

The actual reason the rule was originally set was to protect our staff from out of context posting and partial reposting intended to foster misinformation without us jumping in and clarifying. The thinking was (and to some degree still is) that this would put our staff in a position where unless they responded to every such post, it could be expected to represent proper context.

In that sense it was always meant to improve discussion, not censor it.

This clause also covers some pretty fair expectations regarding other forms of communication than ticket responses. Our staff converse with players through E mail, private messages on social media and on Discord about all manner of things and in that context the rule is in line with common courtesy.

Another misconception is that we´ll ban people for posting ticket replies which is not accurate. Over 15 years we’ve very rarely banned players for violating this clause (single digit number) and it’s always been on the back of a stack of previous warnings or over a wilful attempt to falsify or misconstrue communication for nefarious purposes.

Whether we need to clarify the wording of the TOS or whether having a conversation about what it means like we’re doing now is enough, is something we’ll consider.

For now, the best way is to ask whether you can share the communication if you feel you need to and be fair about how you treat one-on-one communication.


We’re currently working on a few tools and processes internally that will bring further hell down on those who choose to bot in EVE Online.

At this stage, we’re a little too early in the process to talk about any specifics, but be sure to keep checking back in these regular updates for more information.

If you'd like to discuss this dev blog, feel free to do so in the comments thread on the EVE Online Forums here!