CONCORD: Difference between revisions

Serving as the police force, the long arm of the law, '''CONCORD''' acts as an unstoppable force of consequence for anyone breaking the law in [[System Security#High Security|high security space]].

It's important to realize that CONCORD isn't there to defend you, they are simply there to enforce the consequences of breaking the law. As such, people are able to break the law at any time of their choosing, as long as they are ok with the consequences.

This distinction is paramount to understanding how EVE works and why [[suicide ganking]] is valid game mechanics. The loot and consequence mechanics help serve as a self-regulatory risk vs reward system, where people are forced to consider how much ISK they put on a ship. Some modules are incredibly powerful and increase their efficiency, but at the same time makes them more of a target for suicide ganking. As such it allows players to directly control the balance of powerful ships and modules.

Practically this means that while it's impossible to stop someone else from breaking the law, you can drastically reduce the chances of someone suicide ganking you by not fitting too many costly modules, thus removing profit as an incentive.

= CONCORD Mechanics =

CONCORD are triggered by illegal aggression in high-sec. This means that if you activate an offensive module on an innocent player in high-sec, a countdown timer will begin. At the end of this countdown timer, CONCORD cruisers will appear on grid and ECM jam, sensor damp, tracking disrupt, and energy neutralise any players who have taken hostile action. This means that guns can no longer be fired, however AoE modules such as smartbombs and ECM bursts can still be activated. A few seconds later, a CONCORD battleship comes on grid and instantly kills any criminals. CONCORD do not shoot capsules, however if a criminal boards a ship in space, CONCORD will appear and destroy the ship. The time it takes for CONCORD to react varies. The higher the security status of a star system, the lower CONCORD's reaction time. If CONCORD units have already been triggered in the system, the reaction time also increases.

==Prohibited Actions==

* Shooting another players loot (yellow can) while in high sec.

==CONCORD Response==

The CONCORD response time depends on the displayed security status (not the real sec) of the system and the status of CONCORD presence in the system. It's possible CONCORD still has to spawn in the system, has already spawned elsewhere in the system, or is present on grid.

It seems the lock time of the CONCORD ships does not depend on the signature radius of the offender's ship. The following table gives the time in seconds between the offending action and the first felt action of a CONCORD ship when CONCORD has just spawned in a system.

When CONCORD is already on grid, the response time is severely reduced. There are no hard numbers on that yet but it looks like as if the response time drops to 2 seconds in 1.0 to about 8 seconds in 0.6 and 9 seconds in 0.5.

When CONCORD has already spawned elsewhere in the system but isn't on grid, the response time is significantly increased. In this case it will take about 19 seconds them to arrive and start firing in a 0.6 system, and 24 seconds in a 0.5 system.

If CONCORD has already spawned in the system and is not on grid, it's possible the Thrasher can do 3000 EHP damage in a 0.6 system.

<big>{{co|coral| All methods of Delaying CONCORD's Response are considered an exploit by CCP. However, the method of pulling, which is the act of moving CONCORD from one location to another is not considered a delay of CONCORD. : [https://www.eveonline.com/news/view/exploit-notification-delaying-concord-response Exploit Notification Delaying CONCORD Response]}}

=== CONCORD Security Vessels ===

== CONCORD Stations ==

==See Also==