CONCORD: Difference between revisions

(5 intermediate revisions by 4 users not shown)

Line 1:

'''CONCORD''' is a special NPC faction in EVE. In [[System security#High security|high security space]]—and ''only'' in high security space—they bring inevitable consequences to anyone breaking the law.

{{hatnote|This article is about the in-game mechanics related to the CONCORD Assembly faction. For the lore background of the CONCORD Assembly, see [[CONCORD (Lore)]].}}

'''CONCORD Assembly''' (or simply '''CONCORD''') is a special NPC faction in EVE. In [[System security#High security|high security space]]—and ''only'' in high security space—they bring inevitable consequences to anyone breaking the law.

In EVE's lore, CONCORD is a regulation and policing organisation that arose from the NPC empires, but now operates independently of them.

Line 15:

Line 16:

A few seconds later, a CONCORD battleship will enter the grid and instantly kill any criminals. CONCORD ships do not shoot capsules, but if a criminal then boards another ship in space, CONCORD will appear and destroy that 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~~.

The time it takes for CONCORD to react varies. The higher the [[System security|security level]] of a star system, the lower CONCORD's reaction time. If CONCORD units have already been triggered in the system, the reaction time also reduces.

=== Prohibited actions ===

Line 41:

Line 42:

===Response times===

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 is possible that CONCORD has yet to spawn in the system, has already spawned elsewhere in the system, or is already present on grid.

The CONCORD response time depends on the displayed security level (not the [[System security#True security|true security level]]) of the system and the status of CONCORD presence in the system. It is possible that CONCORD has yet to spawn in the system, has already spawned elsewhere in the system, or is already present on grid.

The lock time of the CONCORD ships appears not to depend on the signature radius of the offender's ship. The following list 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.

<u>'''Security ~~Status~~: Response Time'''</u>

<u>'''Security Level: Response Time'''</u>

* '''0.5''': Roughly '''19''' seconds

* '''{{ColorSecurityRating|0.5}}''': Roughly '''19''' seconds

* '''0.6''': Roughly '''14''' seconds

* '''{{ColorSecurityRating|0.6}}''': Roughly '''14''' seconds

* '''0.7''': Roughly '''10''' seconds

* '''{{ColorSecurityRating|0.7}}''': Roughly '''10''' seconds

* '''0.8''': Roughly '''7''' seconds

* '''{{ColorSecurityRating|0.8}}''': Roughly '''7''' seconds

* '''0.9''' and '''1.0''': Roughly '''6''' seconds

* '''{{ColorSecurityRating|0.9}}''' and '''{{ColorSecurityRating|1.0}}''': Roughly '''6''' seconds

When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in 1.0 security to about 8 seconds in 0.6 and 9 seconds in 0.5.

When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in {{ColorSecurityRating|1.0}} security to about 8 seconds in {{ColorSecurityRating|0.6}} and 9 seconds in {{ColorSecurityRating|0.5}}.

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

When CONCORD has already spawned elsewhere in the system but is not yet on grid, the response time is significantly increased. In this case, it will take about 19 seconds for them to arrive and start firing in a {{ColorSecurityRating|0.6}} system, and 24 seconds in a {{ColorSecurityRating|0.5}} system.

If CONCORD has already spawned in the system and is not on grid, suicide gankers will have more time to apply damage. In these circumstances, it's possible for a {{sh|Thrasher}} to do 3,000 EHP damage in a 0.6 system.

If CONCORD has already spawned in the system and is not on grid, suicide gankers will have more time to apply damage. In these circumstances, it's possible for a {{sh|Thrasher}} to do 3,000 EHP damage in a {{ColorSecurityRating|0.6}} system.

<big>{{co|coral| All methods of delaying CONCORD's response are considered an exploit by CCP. However, the technique 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]}}

Line 64:

Line 65:

The actual CONCORD faction, an organization similar to that of a player alliance, is called '''CONCORD Assembly'''.

~~It is impossible to gain standing with this faction, but you~~ can lose standing by destroying CONCORD ships in pirate-faction missions and by doing storyline missions for pirate factions. If you lose enough standing, you will be attacked by faction ships in CONCORD-controlled high-security systems.

You can lose standing by destroying CONCORD ships in pirate-faction missions and by doing storyline missions for pirate factions. If you lose enough standing, you will be attacked by faction navy ships (not CONCORD criminal response ships) in CONCORD-controlled high-security systems. Since the Havoc expansion, standings with this faction can be gained through derived standings with the four main Empire factions.

{| class="wikitable"

Line 180:

Line 181:

* [https://www.eveonline.com/news/view/exploit-notification-delaying-concord-response Exploit Notification Delaying CONCORD Response]

[[Category:Factions]]

@@ Line 1: / Line 1: @@
 {{legality}}
-'''CONCORD''' is a special NPC faction in EVE. In [[System security#High security|high security space]]—and ''only'' in high security space—they bring inevitable consequences to anyone breaking the law.
+{{hatnote|This article is about the in-game mechanics related to the CONCORD Assembly faction. For the lore background of the CONCORD Assembly, see [[CONCORD (Lore)]].}}
+'''CONCORD Assembly''' (or simply '''CONCORD''') is a special NPC faction in EVE. In [[System security#High security|high security space]]—and ''only'' in high security space—they bring inevitable consequences to anyone breaking the law.
 In EVE's lore, CONCORD is a regulation and policing organisation that arose from the NPC empires, but now operates independently of them.
@@ Line 15: / Line 16: @@
 A few seconds later, a CONCORD battleship will enter the grid and instantly kill any criminals. CONCORD ships do not shoot capsules, but if a criminal then boards another ship in space, CONCORD will appear and destroy that 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.
+The time it takes for CONCORD to react varies. The higher the [[System security|security level]] of a star system, the lower CONCORD's reaction time. If CONCORD units have already been triggered in the system, the reaction time also reduces.
 === Prohibited actions ===
@@ Line 41: / Line 42: @@
 ===Response times===
-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 is possible that CONCORD has yet to spawn in the system, has already spawned elsewhere in the system, or is already present on grid.
+The CONCORD response time depends on the displayed security level (not the [[System security#True security|true security level]]) of the system and the status of CONCORD presence in the system. It is possible that CONCORD has yet to spawn in the system, has already spawned elsewhere in the system, or is already present on grid.
 The lock time of the CONCORD ships appears not to depend on the signature radius of the offender's ship. The following list 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.
-<u>'''Security Status: Response Time'''</u>
+<u>'''Security Level: Response Time'''</u>
-* '''0.5''': Roughly '''19''' seconds
+* '''{{ColorSecurityRating|0.5}}''': Roughly '''19''' seconds
-* '''0.6''': Roughly '''14''' seconds
+* '''{{ColorSecurityRating|0.6}}''': Roughly '''14''' seconds
-* '''0.7''': Roughly '''10''' seconds
+* '''{{ColorSecurityRating|0.7}}''': Roughly '''10''' seconds
-* '''0.8''': Roughly '''7''' seconds
+* '''{{ColorSecurityRating|0.8}}''': Roughly '''7''' seconds
-* '''0.9''' and '''1.0''': Roughly '''6''' seconds
+* '''{{ColorSecurityRating|0.9}}''' and '''{{ColorSecurityRating|1.0}}''': Roughly '''6''' seconds
-When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in 1.0 security to about 8 seconds in 0.6 and 9 seconds in 0.5.
+When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in {{ColorSecurityRating|1.0}} security to about 8 seconds in {{ColorSecurityRating|0.6}} and 9 seconds in {{ColorSecurityRating|0.5}}.
-When CONCORD has already spawned elsewhere in the system but is not yet on grid, the response time is significantly increased. In this case, it will take about 19 seconds for them to arrive and start firing in a 0.6 system, and 24 seconds in a 0.5 system.
+When CONCORD has already spawned elsewhere in the system but is not yet on grid, the response time is significantly increased. In this case, it will take about 19 seconds for them to arrive and start firing in a {{ColorSecurityRating|0.6}} system, and 24 seconds in a {{ColorSecurityRating|0.5}} system.
-If CONCORD has already spawned in the system and is not on grid, suicide gankers will have more time to apply damage. In these circumstances, it's possible for a {{sh|Thrasher}} to do 3,000 EHP damage in a 0.6 system.
+If CONCORD has already spawned in the system and is not on grid, suicide gankers will have more time to apply damage. In these circumstances, it's possible for a {{sh|Thrasher}} to do 3,000 EHP damage in a {{ColorSecurityRating|0.6}} system.
 <big>{{co|coral| All methods of delaying CONCORD's response are considered an exploit by CCP. However, the technique 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]}}
@@ Line 64: / Line 65: @@
 The actual CONCORD faction, an organization similar to that of a player alliance, is called '''CONCORD Assembly'''.
-It is impossible to gain standing with this faction, but you can lose standing by destroying CONCORD ships in pirate-faction missions and by doing storyline missions for pirate factions. If you lose enough standing, you will be attacked by faction ships in CONCORD-controlled high-security systems.
+You can lose standing by destroying CONCORD ships in pirate-faction missions and by doing storyline missions for pirate factions. If you lose enough standing, you will be attacked by faction navy ships (not CONCORD criminal response ships) in CONCORD-controlled high-security systems. Since the Havoc expansion, standings with this faction can be gained through derived standings with the four main Empire factions.
 {| class="wikitable"
@@ Line 180: / Line 181: @@
 * [https://www.eveonline.com/news/view/exploit-notification-delaying-concord-response Exploit Notification Delaying CONCORD Response]
+{{FactionsNav}}
 [[Category:Factions]]