[2021] Pulling CONCORD is now a permaban offense

Closing for below

Any declared exploit will be posted on the following support page; as well as; will generally have a news article about it (See the most recent CRAB exploit notification Exploit Notification - CRAB | EVE Online)

1. Specifically restricted conduct.

The purpose of the EVE Online forums is to provide a platform for exchange of ideas, and a venue for the discussion of EVE Online. Occasionally there will be conflicts that arise when people voice opinions. Forum users are expected to courteous when disagreeing with others.

In order to maintain an environment where everyone is welcome and discussion flows freely, certain types of conduct are prohibited on the EVE Online forums. These are:

• Trolling
• Flaming
• Ranting
• Personal Attacks
• Harassment
• Doxxing
• Racism & Discrimination
• Hate Speech
• Sexism
• Spamming
• Bumping
• Off-Topic Posting
• Pyramid Quoting
• Rumor Mongering
• New Player Bashing
• Impersonation
• Advertising

Hello everyone, Lead GM Arcade here.

Thanks for your patience while this matter was discussed extensively within various departments including Customer Support.

It’s clear there is some confusion regarding what is an exploit and what is allowed. This may have been caused by a reference to posts by CCP’ers which may be outdated. EVE Online and its underlying mechanics continuously change, but the Known & Declared Exploits help center article is the definitive reference for exploits that all players should keep an eye on.

We encourage everyone to keep an eye on the Known & Declared Exploits help center article which is kept updated by the GM team and is the definitive reference for exploits.

Recently there has been a discussion within the community concerning what CONCORD manipulation is allowed. We would like to state, echoing the notification linked in the help center article, that “all methods of delaying Concord’s response time are considered an exploit.” This includes deliberately “pulling” or “spawning” CONCORD to a location for defensive or upcoming aggressive actions.

There are simply too many scenarios that may trigger CONCORD reaction and thus we would like to ask that players do not deliberately manipulate or interfere with CONCORD in any way.

Update:

It’s clear now that the above messaging is too vague and does not provide sufficient details or convey the intent of the policy changes. For this you have my apologies.

I would also like to apologize to the CSM who were not consulted before the above post was made. It’s fairly typical that the CSM are not consulted as a matter of course when it comes to customer support policies, but in this case it would have been beneficial to do so.

After this post was made, several CSM members were quick to raise their concerns about the impact on everyday gameplay activities that this policy change would have.

After listening to their feedback we have decided not to implement the policy update mentioned above. There will be no changes to how support are policing CONCORD interaction and that ‘pulling’ CONCORD or defensive spawning of CONCORD is currently permitted but we reserve the right to change this at a future date.