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

System security: Difference between revisions

From EVE University Wiki
m Change wording
 
(3 intermediate revisions by 3 users not shown)
Line 10: Line 10:
Security level should not be confused with [[security status]], which is an attribute attached to a player character.
Security level should not be confused with [[security status]], which is an attribute attached to a player character.


== {{anchor|Known Space}}Known space ==
== Known space ==
 
{{anchor|Known Space}}
There are three general classifications of systems in known space (also commonly referred to as k-space by players) based on system security: High Security, Low Security, and Null Security.
There are three general classifications of systems in '''known space''' (K-space) based on system security: High Security, Low Security, and Null Security.


=== Empire space ===
=== Empire space ===
Line 20: Line 20:
High Security systems are those with a security level of 0.5 to 1.0. [[CONCORD]] will react to hostile actions between pilots, with the response time ranging from almost instant in 1.0 space to up to 19 seconds in 0.5 space. Players also commonly use the terms High, HS, High-sec, Highsec, Hi-sec, and Hisec.
High Security systems are those with a security level of 0.5 to 1.0. [[CONCORD]] will react to hostile actions between pilots, with the response time ranging from almost instant in 1.0 space to up to 19 seconds in 0.5 space. Players also commonly use the terms High, HS, High-sec, Highsec, Hi-sec, and Hisec.


In these systems, stargates may be patrolled by NPC CONCORD, customs, faction police and/or faction navy ships who will fine or [[Security status|attack enemies of the faction and criminals]. Stargates and stations will have sentry guns. Aggression (i.e. committing a [[Crimewatch|Criminal-level offense]]) will provoke a response from CONCORD and any nearby sentry guns. Aggression resulting in the destruction of another player's ship and/or pod will result in a loss of security status.
In these systems, stargates may be patrolled by NPC CONCORD, customs, faction police and/or faction navy ships who will fine or [[Security status|attack enemies of the faction and criminals]]. Stargates and stations will have sentry guns. Aggression (i.e. committing a [[Timers#Criminal Timer|Criminal-level offense]]) will provoke a response from CONCORD and any nearby sentry guns. Aggression resulting in the destruction of another player's ship and/or pod will result in a loss of security status.


==== Low security ====
==== Low security ====
Line 56: Line 56:
In the rest of Null-Sec, sovereignty is claimed (or contested!) by capsuleer alliances. Any stations in claimable Null-Sec will be player-owned and will usually only allow their owners' allies to dock.
In the rest of Null-Sec, sovereignty is claimed (or contested!) by capsuleer alliances. Any stations in claimable Null-Sec will be player-owned and will usually only allow their owners' allies to dock.


{{expansion past|1=University policy, until March 2014, was that University pilots were not allowed to enter claimable Null-Sec, unless in a fleet lead by an [[ILN]] Officer, in order to preserve the University's neutrality. That changed in March 2014, after a successful 1-month experiment, and [[Azmodeus Valar]] mailed out "[O]ur month long test of increased Sov Null access has been a success. We will be continuing it indefinitely. This means that anyone can lead a fleet into sovereign null security space for PvP purposes. Do not engage in PvE activities in Sov Null space, and do not participate in structure or sovereignty battles." See [https://forum.eveuniversity.org/viewtopic.php?f=31&t=76988 this forum thread] for more details. This was later updated to allow PvE activities as well, see EVE University's '''[[EVE_University_Rules|Rules of Engagement]]'''.}}
{{expansion past|1=University policy, until March 2014, was that University pilots were not allowed to enter claimable Null-Sec, unless in a fleet lead by an [[ILN]] Officer, in order to preserve the University's neutrality. That changed in March 2014, after a successful 1-month experiment, and [[Azmodeus Valar]] mailed out "[O]ur month long test of increased Sov Null access has been a success. We will be continuing it indefinitely. This means that anyone can lead a fleet into sovereign null security space for PvP purposes. Do not engage in PvE activities in Sov Null space, and do not participate in structure or sovereignty battles." This was later updated to allow PvE activities as well, see EVE University's '''[[EVE_University_Rules|Rules of Engagement]]'''.}}


A regularly-updated map of player-owned territory is available on the external [https://sov.space/ SovMap website]
A regularly-updated map of player-owned territory is available on the external [https://sov.space/ SovMap website]