Known & Declared Exploits

Disclaimer

This article outlines public exploit notifications which are still in effect and also addresses certain practices which are commonly misunderstood as exploits when they in fact are not.

Please do keep in mind that this list is not an exhaustive resource for every disallowed action in EVE Online, only exploits which have been publicly disclosed will be listed below.

Should you think that you may have discovered an unknown exploit, please report it directly to us through the "Exploit" category in a support ticket. Furthermore please always remember that exploit abuse carries repercussions as outlined in the EVE Online Terms of Service.

Please bear in mind that publishing steps on how to abuse game errors or making a game feature appear erroneous for personal gain will be treated in the same manner as publishing an exploit, independently of whether or not there is an actual issue. Report all erroneous game behavior immediately.

Declared Exploits

This page contains all publicly declared exploits which are still in effect. Many bugs which have been publicly declared as exploits in the past have at this time been fixed and are therefore not included in the table below.

The links provided will take you directly to any past public exploit notifications.

Committing a criminal act and delaying CONCORD response for an extended period of time.

Commonly involves leaving empty ships or drones in space that CONCORD focuses on before dealing with the attacker. This exploit is not limited to drones or ships and applies to any item or method which might be used to delay CONCORD.

It is also considered an exploit to commit a criminal act and prevent ship loss to CONCORD by any means.

Having a cynosural field generator active is supposed to leave the generating pilot immobile and vulnerable. As such, managing to be within a forcefield or being otherwise effectively invulnerable (or inaccessible) while generating a cynosural field is considered an exploit.

Using any method to bypass acceleration gate ship restrictions to enter complexes is an exploit. The notification specifies Factional Warfare complexes but this has since been extended to all sites which have acceleration gates.

Gaining the Omega Clone State Double Training speed of skills while the account is in Alpha Clone state is not permitted.

Accounts in the Omega Clone state enjoy double skill training speed compared accounts in the Alpha Clone state. Somehow managing to retain this increased Omega training speed while the account is in Alpha State is not permitted.

Any and all methods preventing a wormhole from appearing when it should are not permitted

All methods of blocking the spawning of a wormhole are considered exploits.

Common Misconceptions about Exploits

This passage contains common tactics and other player conduct that is often mistakenly reported as exploits but are in fact not.

Non-Exploit

Description

Log Off Traps

Players are free to log out and back into our game at their own leisure.

Surprising a target by logging in is not considered to be an exploit.

Grid Manipulation

Extending the grid to increase the available information on the overview.

AFK Cloaking

A player is present in a system for a long time, usually cloaked, doing nothing at all most of the time.

MWD Cloak Warp

Using a Cloaking Device and one cycle acceleration on a Microwarpdrive module to enter warp immediately upon decloaking.

Ship Bumping

Ram the ship of another player with your own in order to prevent them from warping.

Warp disruption fields at star gates

Having players dragged into bubbles by strategically placing them behind star gates is not an exploit.

Constant War Declarations

War Declarations are a risk that every player corporation has to face and they are under no circumstances considered harassment. Wars in general can be completely avoided by remaining in an NPC corporation.

Ship text always shown on all brackets

It is possible to always show ship types next to each bracket, as outlined in this forum post. However, this function is not officially supported and may result in unexpected behavior of the client. Use at your own risk.