Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

CONCORD Details: Difference between revisions

From EVE University Wiki
Added some information. Format changes to clarify information and improve layout.
Line 3: Line 3:




==CONCORD Responses==
==Allowed Actions==


CONCORD will respond to the following list of player activities.
CONCORD '''will not''' respond to the following list of player activities.
 
* Locking onto a player
* Cargo scanning a player
* Remote repairing a player ''('''Note:''' If the player becomes a criminal while you are repping them, your remote repair modules will deactivate. Before Crucible, they would kill you instead.)''
* Shooting at [[asteroids]]
* Shooting players against whom you have [[Kill Rights]] or other legal [[War Targets]]
* Damaging or committing an act of aggression against another Corporation member. ''(Does not apply to [[NPC corporations]].)''
* Damaging or committing an act of aggression against the Faction Navies. ''(However this may be met with resistance from the faction themselves.)''
* Having low security status and jumping into a [[Eve_Lexicon#HiSec|Hi-Sec System]] '''NOT''' in the [[Sanctum Constellation]].
 
==Prohibited Actions==
 
CONCORD '''will''' respond to the following list of player activities.


* Aggressing a player who is not a legal target in highsec. (See [[crimewatch]] for details.)
* Aggressing a player who is not a legal target in highsec. (See [[crimewatch]] for details.)
Line 14: Line 27:
* Having low security status and jumping into a [[Eve_Lexicon#HiSec|Hi-Sec System]] in the [[Sanctum Constellation]]
* Having low security status and jumping into a [[Eve_Lexicon#HiSec|Hi-Sec System]] in the [[Sanctum Constellation]]


==CONCORD Allowed Actions==
==CONCORD Response==
 
CONCORD will '''not''' respond to the following list of player activities.
 
* Locking onto a player
* Cargo scanning a player
* Remote repairing a player ''('''Note:''' If the player becomes a criminal while you are repping them, your remote repair modules will deactivate. Before Crucible, they would kill you instead.)''
* Shooting at [[asteroids]]
* Shooting players against whom you have [[Kill Rights]]
* Damaging or committing an act of aggression against another Corporation member.
* Damaging or committing an act of aggression against the Faction Navies.


=== CONCORD Response Action ===
If a player performs one of the prohibited actions, as above: two CONCORD cruisers and a CONCORD battleship will warp to the location. The two cruisers have a lock time of about 2 seconds. Both Cruisers will warp-scramble, web, jam, reduce the drone bandwith to zero, and neut the offender completely every 5 seconds. That means from there on the only damage the offender can do is smartbombs, but only when cap injected. They will also shoot at the offender and each will deal about 1.000 damage every volley. 15 seconds after CONCORD has warped in, the Battleship will lock the offender and immediately destroy it unless the cruisers have done so already.
At first two CONCORD Cruisers and a CONCORD Battleship will warp to the location. The two Cruisers have a lock time of about 2 seconds. Then both Cruisers will warp-scramble, web, jam, reduce the drone bandwith to zero and neut the offender completely every 5 seconds. That means from there on the only damage the offender can do is smartbombs but only when cap injected. They will also shoot at the offender and each will deal about 1.000 damage every volley.  
15 seconds after CONCORD has warped in, the Battleship will have locked the offender and immediately destroy it.


==CONCORD Response Times==
==CONCORD Response Times==
The CONCORD Response Time depends basically 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.
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.
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.