EVE Online Dev Tracker

The emails sent to [email protected] were forwarded to Team Security.
But we decided to slowly transition away of reporting any violations in the game to that specific email, as it was setup for something different, like InfoSec.

So now the best way to reach Team Security regarding botters, fraudsters, RMTers and hackers is via a support Ticket. This for sure will end up in our queue and get attention it deserves.

We definitely try! Always fishing for those big sharks out there…

Good questions, thank you!

1. This happens, of course. This is no secret and I see no point in making this topic taboo of some sort. There are very different scenarios for this situation. Some of them are covered in the blog, it’s the part about ISK selling and possible consequences for individuals. Ironically, in this case the seller is more in danger from other capsuleers than from us. ISK selling is such a slippery slope, the initial success leads to eventual mistakes and, well, consequences.
   Besides, those people who are determined to get rid of anything, might have change of heart later on. But the assets are gone and, well… the account is kind of damaged already.

2. Easy answer - nope, it does not. It brings some level of frustration to the team because we investigate the big amount of reports, and if there is nothing to act upon… well, what was the point of those? But again, reports on its own do not do harm, if the ratters did not use any mo...

That’s not exactly how botting works in EVE, but who knows, maybe one day it might. Personally I have never seen the bot doing all of this together. Bots, or rather the human behind them (who is creating them) usually have very clear goals and rather simple means to achieve them.
But the phrasing of accelerated rate is absolutely correct, you are right.

I know what you mean!
That’s probably for the other teams to be discussed, but I’ll certainly bring it up and see if something can be done

Hi,

A lot to unwrap, but the bottom line is “do not bot”. As most of the user agreements, EULA needs to cover as much as possible in a short amount of words and in the comprehensive manner (more or less). Hence the choice of words.
I personally think that this quote is rather self-explanatory, and accelerated rate means, well, the automation. Simple example: it might take a human to win a game of chess in 2 minutes, for bot it will be half a minute. Same here.
You are absolutely correct in your observation, automation exceeds the human input tremendously. And it is very much visible. There are many things that are considered EULA violation and botting is one of them.

It does not matter what exactly Ishtar does. It can engage in PVP, it can go search for drifters, it can dock and undock just for the sake of it. But if automation is used in any of those actions - that is considered botting. The gameplay as a whole is important, not the action itself.

We ...

It might have been forwarded to Team Sec before, but if it was a couple of years ago, then it was before my time and I can’t answer this, sadly.

It’s monitored, but by different people, not Team Sec.
Send us a support ticket and we’ll have a look, your efforts will not be in vain.

Ah, this is one of those cases where I can not provide any info because it’s about another player. Sadly, “can neither confirm nor deny”.

No no, you did not miss it, no worries It was not mentioned in the blog itself, but I can definitely talk about it.
Most likely it is, yep. Some limitations can be lifted later, but same with bans, it’s always case-by-case.

Got it! Will be discussed very closely

No bans are done just for this, EVE-O-Preview has nothing to do with it. The ban happens when the certain threshold is hit, simply put. Let’s say - you have a 100 reports on you, our internal tools picked you up, our certain checks returned positive result. In this case yes, there is definitely something to worry about. But even throughout these cases we had false positives. This is why the edge cases are being investigated by a couple of people. There have been some instances when I made a mistake...

Ah, did not realize that! Super valid point, actually. Looks like the wording might be a bit weird, but this ToS was written a while ago, to be fair. Let me bring this up with the team. If there are any updates, I’ll let you know

I think that because it was a bug report it might have been treated differently? But if it was an RMT/bot report, you’d probably would have been asked to submit a ticket

Ah, it’s not a secret at all - those limitations include inability to transfer the chararcter and SP extraction. And since the account is considered to be involved in EULA violations, further violations (even of different nature) might include more severe penalties.