These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Conversation spam

First post First post
Author
GM Homonoia
Game Master Retirement Home
#1 - 2012-10-25 11:20:17 UTC  |  Edited by: CCP Navigator
Customer support is making this post to clarify a specific type of case and our policies regarding that type of case. Recently we have seen a rise in reimbursement requests on the grounds of a conversation spam exploit.

Is this an exploit? No, it is not an exploit and we will not be reimbursing any losses on the grounds of conversation spam.

To clarify this point, this used to be an exploit, but the conditions that caused it to be an exploit were fixed a while ago. In the past a conversation request would generate a popup that would take focus within the game client and would not let you continue to play until you made a decision on the request. However, currently the popup will not lock you out of the rest of the game and it will not grab focus. You can ignore the request and keep playing the game. There is also an option to automatically decline any conversation requests sent your way.

Is conversation spamming allowed? No, it is not.

While conversation spam is not considered an exploit, it IS considered spam. Anyone caught doing this (this includes a large group of people each sending only 1 request) will be warned and, if the behavior does not cease, banned. We encourage everyone who is subjected to conversation spam to file a petition under the “harassment” category.

Tl;dr If you are the victim of conversation spam you will not be reimbursed as it is not an exploit, but please do report it as we do take action against the spammers; spamming is not allowed.


Update on Monday, November 12

Hello everyone,

Lead GM Grimmi has asked that we publish this news item as an update.

In short, convo spamming is very bad and will be dealt with harshly. There is no need for further discussion on the matter and this topic will be locked on request of Customer Support.

Senior GM Homonoia | Info Group | Senior Game Master

Chribba
Otherworld Enterprises
Otherworld Empire
#2 - 2012-10-25 11:44:41 UTC
How will we know who initiated the "spam" though, should we petition ever pilot trying to open a convo a the time or how's the though proceedure?

/c

★★★ Secure 3rd party service ★★★

Visit my in-game channel 'Holy Veldspar'

Twitter @ChribbaVeldspar

GM Homonoia
Game Master Retirement Home
#3 - 2012-10-25 11:47:59 UTC
Chribba wrote:
How will we know who initiated the "spam" though, should we petition ever pilot trying to open a convo a the time or how's the though proceedure?

/c


Just file a single petition stating where and when you were when it happened and we will figure out the rest. We can see exactly who did this and we will act accordingly.

Senior GM Homonoia | Info Group | Senior Game Master

Inquisitor Kitchner
The Executives
#4 - 2012-10-25 12:45:59 UTC
So even though it's something players shouldn't do, if I lose a ship because of it I wont be reimbursed?

Do you mind if I just ask you to flesh out the logic behind that a bit? Not saying there isn't logic there, I just don't get it at the moment. Unless you're threatening to ban players outright, what's stopping me from saying to my 256 man fleet "OK anyone who hasn't already got warned about this, send a conversation"? If I say it over TS you wont be able to prove I ever said it, so can't really punish me for suggesting it.

If everyone did that to say, kill a Titan which you know they wont be reimbursed for, a lot of people would think it's worth it.

"If an injury has to be done to a man it should be so severe that his vengeance need not be feared." - Niccolo Machiavelli

GM Homonoia
Game Master Retirement Home
#5 - 2012-10-25 13:00:55 UTC
Inquisitor Kitchner wrote:
So even though it's something players shouldn't do, if I lose a ship because of it I wont be reimbursed?

Do you mind if I just ask you to flesh out the logic behind that a bit? Not saying there isn't logic there, I just don't get it at the moment. Unless you're threatening to ban players outright, what's stopping me from saying to my 256 man fleet "OK anyone who hasn't already got warned about this, send a conversation"? If I say it over TS you wont be able to prove I ever said it, so can't really punish me for suggesting it.

If everyone did that to say, kill a Titan which you know they wont be reimbursed for, a lot of people would think it's worth it.


It is not allowed because it is spam. However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled. Even if you have not, you will receive 1 popup that does not grab focus and does not prevent you from controlling your client normally. Simply ignore it.

Senior GM Homonoia | Info Group | Senior Game Master

Benny Ohu
Royal Amarr Institute
Amarr Empire
#6 - 2012-10-25 13:25:03 UTC
Separate to the 'popup takes focus' issue, in previous threads some people claimed that the conversation auto-reject might be client-side, meaning a convobomb would still cause a good amount of lag due to the number of requests queued up only to be rejected by the client (to my limited understanding :D)

Was this not true, or is it just not a problem?
Femaref
Nocturnal Romance
Cynosural Field Theory.
#7 - 2012-10-25 13:28:25 UTC
GM Homonoia wrote:
Inquisitor Kitchner wrote:
So even though it's something players shouldn't do, if I lose a ship because of it I wont be reimbursed?

Do you mind if I just ask you to flesh out the logic behind that a bit? Not saying there isn't logic there, I just don't get it at the moment. Unless you're threatening to ban players outright, what's stopping me from saying to my 256 man fleet "OK anyone who hasn't already got warned about this, send a conversation"? If I say it over TS you wont be able to prove I ever said it, so can't really punish me for suggesting it.

If everyone did that to say, kill a Titan which you know they wont be reimbursed for, a lot of people would think it's worth it.


It is not allowed because it is spam. However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled. Even if you have not, you will receive 1 popup that does not grab focus and does not prevent you from controlling your client normally. Simply ignore it.


It pops up in the middle of the screen and as such, can be a massive distraction, simply because that where the action happens; even more so if you are flying small ships and need to control it manually. Maybe make convo invites only appear in the neocom when you have an aggrotimer?
Prototype Epsilon
Crimson Wraiths
#8 - 2012-10-25 13:39:46 UTC  |  Edited by: Prototype Epsilon
Quote:

It is not allowed because it is spam. However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled. Even if you have not, you will receive 1 popup that does not grab focus and does not prevent you from controlling your client normally. Simply ignore it.


what about the case were im in a fleet and actually want to receive legitimate chat convos? is that such a "fringe case" now so i should simply block all incoming chat requests while in a fleet?
James Amril-Kesh
Viziam
Amarr Empire
#9 - 2012-10-25 13:42:26 UTC  |  Edited by: James Amril-Kesh
GM Homonoia wrote:
However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled.

Have you investigated whether this actually works? I've heard that because the client still has to receive the request before it automatically rejects it, there's still a lot of traffic generated which can cause lag and/or a client crash.

If you haven't tested it I'd strongly suggest you do so, and if you have and you've found it not to be a problem then I agree with the decision against declaring this an exploit.

I'd test it myself but it's rather difficult to get enough people to agree to try it.

Enjoying the rain today? ;)

GM Homonoia
Game Master Retirement Home
#10 - 2012-10-25 13:44:00 UTC  |  Edited by: GM Homonoia
James Amril-Kesh wrote:
GM Homonoia wrote:
However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled.

Have you investigated whether this actually works? I've heard that because the client still has to receive the request before it automatically rejects it, there's still a lot of traffic generated which can cause lag and/or a client crash.

If you haven't tested it I'd strongly suggest you do so, and if you have and you've found it not to be a problem then I agree with the decision against declaring this an exploit.


We are aware of those claims and they are being investigated.

Edit: Note that causing lag is not an exploit per se. If it was, bringing a large fleet to an engagement would be an exploit. However, purposefully causing lag is not allowed and we do warn and ban for that; conversation spamming is no different in that sense if our investigations into the matter yield confirming results. HOWEVER, the fact that someone did something that is not allowed does not automatically mean that the other party will be reimbursed. Many different considerations factor into a decision like that.

Tl;dr Using an exploit and doing something wrong are not always the same thing.

Senior GM Homonoia | Info Group | Senior Game Master

Bruceleeng
Doomheim
#11 - 2012-10-25 13:54:21 UTC  |  Edited by: Bruceleeng
GM Homonoia wrote:
[...] In a fleet fight you should simply have auto-reject enabled [...]

Best. Gaming. Experience. Ever.


This decision is bad and the GM team should feel bad about taking it. One needs to be able to get convos from scouts, fcs, spies, etc. during a fleet. What you are suggesting is a work-around. I know another work-around for this problem. Don't play EvE.
Inquisitor Kitchner
The Executives
#12 - 2012-10-25 14:05:20 UTC  |  Edited by: Inquisitor Kitchner
GM Homonoia wrote:


It is not allowed because it is spam. However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled. Even if you have not, you will receive 1 popup that does not grab focus and does not prevent you from controlling your client normally. Simply ignore it.


To be totally honest I have never been convo spammed, so I can't comment on what it used to do compared to what it does do now.

If there was evidence to show it does more then simply annoy pilots, would the GM team reconsider their stance?

I'm only asking because while I appreciate there's a way to block them if they are no more annoying then local chat, if they effect actual gameplay in even some cases I think, in my own personal opinion, telling people to always fly where people can't chat to them is a bit unfair. There's a difference between saying "It's annoying, but you can block it if you wish to trade off not being annoyed for no-one convo-ing you" and "You need to fly with no-one being able to convo you otherwise you MAY lose your ship due to tactics which could result in a player being banned."

I get the difference between you saying "This is an exploit, you lost your ship unfairly, we wont tolerate it and here's your ship back" and "They are breaking the EULA by being an annoying spammer, but you haven't lost your ship unfairly". I think an open mind on changing your stance should new information or examples come to light is important that's all.

Just my thoughts on the matter anyway.

"If an injury has to be done to a man it should be so severe that his vengeance need not be feared." - Niccolo Machiavelli

GM Homonoia
Game Master Retirement Home
#13 - 2012-10-25 14:11:18 UTC
Inquisitor Kitchner wrote:
GM Homonoia wrote:


It is not allowed because it is spam. However, no one should lose a ship specifically because of this. In a fleet fight you should simply have auto-reject enabled. Even if you have not, you will receive 1 popup that does not grab focus and does not prevent you from controlling your client normally. Simply ignore it.


To be totally honest I have never been convo spammed, so I can't comment on what it used to do compared to what it does do now.

If there was evidence to show it does more then simply annoy pilots, would the GM team reconsider their stance?

I'm only asking because while I appreciate there's a way to block them if they are no more annoying then local chat, if they effect actual gameplay in even some cases I think, in my own personal opinion, telling people to always fly where people can't chat to them is a bit unfair. There's a difference between saying "It's annoying, but you can block it if you wish to trade off not being annoyed for no-one convo-ing you" and "You need to fly with no-one being able to convo you otherwise you MAY be effected by tactics which could result in a player being banned.

Just my thoughts on the matter anyway.


We will, of course, review our stance if new evidence comes to light. However, situations where these tactics are usually used are complex and the conversation spam is not the only factor weighing in. For example, in fleet engagements we do not reimburse for any reason; we punish people abusing our systems, but we do not reimburse because there is no way to do so fairly. It is most likely that when it is proven that convo spam causes significant lag that the punishment for using such a tactic will grow harsher.

As I said above, reimbursement is a complex issue and simply the fact that someone used something that is not allowed does not automatically mean that you will be reimbursed. It DOES mean that the perpetrator will be punished.

It's really simple, we want everyone to play by the rules and people who don't want to can take a hike; forcefully if need be.

Senior GM Homonoia | Info Group | Senior Game Master

Katsami
Holy Amarrian Battlemonk
Crimson Inquisicion
#14 - 2012-10-25 15:26:18 UTC  |  Edited by: Katsami
I'm interested to see how you could potentially differentiate a ship loss resulting solely from convo-bombing versus one that was fated to die anyways in the given circumstances.

Honestly, one way to get rid of the issue is to come down hard and reimburse all losses in which request abuse occurred by opposing forces. Creating a disincentive gets rid of the problem.
Jim Era
#15 - 2012-10-25 15:39:21 UTC
This thread made me lose hope in ccp

Wat™

Inquisitor Kitchner
The Executives
#16 - 2012-10-25 15:44:15 UTC
GM Homonoia wrote:

As I said above, reimbursement is a complex issue and simply the fact that someone used something that is not allowed does not automatically mean that you will be reimbursed. It DOES mean that the perpetrator will be punished.


So essentially while dying when convo spammed doesn't automatically equal reimbursement it doesn't mean that ship reimbursement is totally ruled out, just dependent on circumstances? (Presumably like every other situation)

"If an injury has to be done to a man it should be so severe that his vengeance need not be feared." - Niccolo Machiavelli

Prototype Epsilon
Crimson Wraiths
#17 - 2012-10-25 15:45:25 UTC  |  Edited by: Prototype Epsilon
Jim Era wrote:
This thread made me lose hope in ccp


agreed, I wish they consulted CSM about these things
James Amril-Kesh
Viziam
Amarr Empire
#18 - 2012-10-25 15:59:38 UTC  |  Edited by: James Amril-Kesh
GM Homonoia wrote:
For example, in fleet engagements we do not reimburse for any reason; we punish people abusing our systems, but we do not reimburse because there is no way to do so fairly.

What exactly is your justification for that? How do you define fair in this context? How do you define "fleet engagement"?

In fact, while we're on the subject, what makes something an exploit vs. "not allowed"?

Enjoying the rain today? ;)

Prototype Epsilon
Crimson Wraiths
#19 - 2012-10-25 16:11:50 UTC
Quote:
In fact, while we're on the subject, what makes something an exploit vs. "not allowed"?


what ever their reason is, it has little to do with the way the rest of the world uses these world and more closely resembles just a GMs bias against an issue.
GM Homonoia
Game Master Retirement Home
#20 - 2012-10-25 16:13:03 UTC
James Amril-Kesh wrote:
GM Homonoia wrote:
For example, in fleet engagements we do not reimburse for any reason; we punish people abusing our systems, but we do not reimburse because there is no way to do so fairly.

What exactly is your justification for that? How do you define fair in this context? How do you define "fleet engagement"?

In fact, while we're on the subject, what makes something an exploit vs. "not allowed"?


What exactly is your justification for that?

That is a discussion that would take too long to have here. The matter is incredibly complex and we have had several long discussions on that, both internally in CS, internally with other departments and externally with the CSM. Basically it is more important to remain fair and impartial and treat everyone equally than it is to see that everyone is happy. This is incredibly hard to do where large scale fleet engagements are concerned.

How do you define fair in this context?

Treat everyone equally; this means applying our reimbursement policies as strict as possible for everyone involved.

How do you define "fleet engagement"?

By consensus and on a case by case basis using internal metrics and guidelines. Yes, this is vague and it will stay that way. It is simply impossible to define this externally in a way that would satisfy the majority of our players.

what makes something an exploit vs. "not allowed"?

Linking porn in chat channels is not allowed, but it is not an exploit. Basically, everything that breaches our rules (EULA, ToS, etc) is not allowed, but abusing the system in a way that drastically affects the game can be determined to be an exploit once the process has been verified and can be tracked. In that sense there have even been exploits that were "allowed" simply because it was impossible for a player to know that he was using an exploit.

Senior GM Homonoia | Info Group | Senior Game Master

123Next pageLast page