System security: Difference between revisions

(10 intermediate revisions by 7 users not shown)

Line 10:

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 ==

There are three general classifications of systems based ~~upon~~ 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 is the name given to the regions which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, [[stealth bomber]]s can't use [[bombs]] and players cannot deploy [[Tackling#Warp_disruption_fields|bubbles]].

Empire space is the name given to the regions in which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, [[stealth bomber]]s can't use [[bombs]] and players cannot deploy [[Tackling#Warp_disruption_fields|bubbles]].

==== High security ====

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, 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, and/or faction navy ships, and ~~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 systems are those with a security level of 0.1 to 0.4. Players also commonly use the terms Low, Low-sec, Lo-sec, Lowsec, and Losec.

Low Security systems are those with a security level of 0.1 to 0.4. Players also commonly use the terms Low, LS, Low-sec, Lo-sec, Lowsec, and Losec.

In these systems, stargates and stations will have sentry guns (although fewer than in Highsec), but [[CONCORD]] will '''not''' react to hostile actions between pilots, although any nearby sentry guns will still open fire on the attacking player(s) and unprovoked attacks will cause losses of security status.

=== Null security ===

Null Security systems are those with a security level of -1.0 to 0.0. Players also commonly use the terms Null, ~~Null-sec~~, Null-Sec, and 0.0 (pronounced "zero zero", "zero dot zero", or "oh dot oh"). The name originates from a time when instead of showing negative security status the displayed statuses were rounded to 0.0.

Null Security systems are those with a security level of -1.0 to 0.0. Players also commonly use the terms Null, NS, Null-Sec, and 0.0 (pronounced "zero zero", "zero dot zero", or "oh dot oh"). The name originates from a time when instead of showing negative security status the displayed statuses were rounded to 0.0.

These systems are essentially lawless and no NPC organizations will respond to aggression, nor will actions of any kind result in a loss of security status. In Null-Sec the gloves are off: [[stealth bomber]]s can use bombs and players can deploy [[Tackling#Warp_disruption_fields|bubbles]]; players frequently fly under not-blue-shoot-it ('NBSI') rules of engagement.

Null security space can further be split to NPC ~~null~~ and claimable ~~null~~.

Null security space can further be split into NPC Null-Sec and claimable sovereign Null-Sec.

==== NPC ~~null security~~ space ====

==== NPC Null-Sec space ====

NPC Null-Sec is ~~null-security~~ space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by [[capsuleer]] alliances.

NPC Null-Sec is space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by [[capsuleer]] alliances.

Regions classified as NPC Null-Sec:

Line 45:

* '''Venal''', ''claimed by Guristas Pirates''

~~Constellations~~ classified as NPC Null-Sec:

Individual constellations classified as NPC Null-Sec:

* '''38G6-L''' within Pure Blind, ''claimed by Sisters of ~~Eve~~''

* '''38G6-L''' within Pure Blind, ''claimed by Sisters of EVE''

* '''N-K4Q0''' within Geminate, ''claimed by Society of Conscious Thought''

* '''Phoenix''' within Fountain, ''claimed by Serpentis''

Line 52:

* '''XPJ1-6''' and '''6-UCYU''' within Delve, ''claimed by Blood Raiders''

==== Claimable ~~null security~~ space ====

==== Claimable Null-Sec space ====

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 ~~the~~ '''Rules of Engagement''' ~~page on [[ROE#Claimable NullSec|claimable nullsec]]~~.}}

{{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 [https://~~go-dl1~~.~~eve-files.com/media/corp/Verite~~/~~influence.png here~~].

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

Regions classified as Claimable Null-Sec:

Line 114:

* [[Asteroid]] types found in asteroid belts. More lucrative asteroids are generally found in lower-security systems.

* General difficulty of [[rat]] spawns, including belt and gate rats. More difficult rats are generally found in lower-security systems.

* General difficulty of [[rat]] spawns, including [[Belt rat|belt]] and gate rats. More difficult rats are generally found in lower-security systems.

* General difficulty of [[Cosmic Anomalies|cosmic anomalies]] and [[cosmic signatures]]. More difficult sites are generally found in lower-security systems.

* Reward level of [[missions]]. Greater LP rewards for the same mission are given by agents in lower-security systems.

Line 155:

=== Anchoring ===

The security level of a system may limit what may be [[Anchoring|anchored]] in that system. <ref>[https://~~community~~.eveonline.com/news/~~dev-blogs~~/starbase-changes-for-crius/ Dev blog: Starbase changes for Crius]</ref>

The security level of a system may limit what may be [[Anchoring|anchored]] in that system. <ref>[https://www.eveonline.com/news/view/starbase-changes-for-crius Dev blog: Starbase changes for Crius]</ref>

* 0.9 - 1.0: Containers may NOT be anchored. Starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system [[sovereignty]].

Line 170:

Many security related mechanics use the true security instead of the rounded security status, however. A lower True-Sec system has better mission pay-outs than a higher True-Sec system, even if the displayed sec status is the same.

The true security is not visible anywhere in game, instead it can be found in the [https://community.~~eveonline~~.com/community/fansites/toolkit/ official datadump] or from [https://esi.tech.ccp.is/latest/#/ ESI API]. Many third party mapping tools such as [https://evemaps.dotlan.net/ Dotlan] also show the true security.

The true security is not visible anywhere in game, instead it can be found in the [https://community.testeveonline.com/community/fansites/toolkit/ official datadump] or from [https://esi.tech.ccp.is/latest/#/ ESI API]. Many third party mapping tools such as [https://evemaps.dotlan.net/ Dotlan] also show the true security.

{{expansion past|width=50%|1=In the past, truesec values in the range (0.0, 0.5) were rounded half up, i.e. rounded down to 0.0 because all numbers in that range are below 0.5. This was a bug, because EVE considers all systems above a truesec rating of 0.0 to be lowsec but the game displayed their security level as "0.0". This bug not only caused some confusion (there were sentry guns within apparently Null-Sec systems) but also some problems in the form of inadvertent security status loss in what seemed like Null-Sec.

@@ Line 10: / Line 10: @@
 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 based upon 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 is the name given to the regions which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, [[stealth bomber]]s can't use [[bombs]] and players cannot deploy [[Tackling#Warp_disruption_fields|bubbles]].
+Empire space is the name given to the regions in which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, [[stealth bomber]]s can't use [[bombs]] and players cannot deploy [[Tackling#Warp_disruption_fields|bubbles]].
 ==== High security ====
-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, 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, and/or faction navy ships, and 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 systems are those with a security level of 0.1 to 0.4. Players also commonly use the terms Low, Low-sec, Lo-sec, Lowsec, and Losec.
+Low Security systems are those with a security level of 0.1 to 0.4. Players also commonly use the terms Low, LS, Low-sec, Lo-sec, Lowsec, and Losec.
 In these systems, stargates and stations will have sentry guns (although fewer than in Highsec), but [[CONCORD]] will '''not''' react to hostile actions between pilots, although any nearby sentry guns will still open fire on the attacking player(s) and unprovoked attacks will cause losses of security status.
 === Null security ===
-Null Security systems are those with a security level of -1.0 to 0.0. Players also commonly use the terms Null, Null-sec, Null-Sec, and 0.0 (pronounced "zero zero", "zero dot zero", or "oh dot oh"). The name originates from a time when instead of showing negative security status the displayed statuses were rounded to 0.0.
+Null Security systems are those with a security level of -1.0 to 0.0. Players also commonly use the terms Null, NS, Null-Sec, and 0.0 (pronounced "zero zero", "zero dot zero", or "oh dot oh"). The name originates from a time when instead of showing negative security status the displayed statuses were rounded to 0.0.
 These systems are essentially lawless and no NPC organizations will respond to aggression, nor will actions of any kind result in a loss of security status. In Null-Sec the gloves are off: [[stealth bomber]]s can use bombs and players can deploy [[Tackling#Warp_disruption_fields|bubbles]]; players frequently fly under not-blue-shoot-it ('NBSI') rules of engagement.
-Null security space can further be split to NPC null and claimable null.
+Null security space can further be split into NPC Null-Sec and claimable sovereign Null-Sec.
-==== NPC null security space ====
+==== NPC Null-Sec space ====
-NPC Null-Sec is null-security space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by [[capsuleer]] alliances.
+NPC Null-Sec is space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by [[capsuleer]] alliances.
 Regions classified as NPC Null-Sec:
@@ Line 45: / Line 45: @@
 * '''Venal''', ''claimed by Guristas Pirates''
-Constellations classified as NPC Null-Sec:
+Individual constellations classified as NPC Null-Sec:
-* '''38G6-L''' within Pure Blind, ''claimed by Sisters of Eve''
+* '''38G6-L''' within Pure Blind, ''claimed by Sisters of EVE''
 * '''N-K4Q0''' within Geminate, ''claimed by Society of Conscious Thought''
 * '''Phoenix''' within Fountain, ''claimed by Serpentis''
@@ Line 52: / Line 52: @@
 * '''XPJ1-6''' and '''6-UCYU''' within Delve, ''claimed by Blood Raiders''
-==== Claimable null security space ====
+==== Claimable Null-Sec space ====
 {{main|Sovereignty}}
-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 the '''Rules of Engagement''' page on [[ROE#Claimable NullSec|claimable nullsec]].}}
+{{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 [https://go-dl1.eve-files.com/media/corp/Verite/influence.png here].
+A regularly-updated map of player-owned territory is available on the external [https://sov.space/ SovMap website]
 Regions classified as Claimable Null-Sec:
@@ Line 114: / Line 114: @@
 * [[Asteroid]] types found in asteroid belts. More lucrative asteroids are generally found in lower-security systems.
-* General difficulty of [[rat]] spawns, including belt and gate rats. More difficult rats are generally found in lower-security systems.
+* General difficulty of [[rat]] spawns, including [[Belt rat|belt]] and gate rats. More difficult rats are generally found in lower-security systems.
 * General difficulty of [[Cosmic Anomalies|cosmic anomalies]] and [[cosmic signatures]]. More difficult sites are generally found in lower-security systems.
 * Reward level of [[missions]]. Greater LP rewards for the same mission are given by agents in lower-security systems.
@@ Line 155: / Line 155: @@
 === Anchoring ===
-The security level of a system may limit what may be [[Anchoring|anchored]] in that system. <ref>[https://community.eveonline.com/news/dev-blogs/starbase-changes-for-crius/ Dev blog: Starbase changes for Crius]</ref>
+The security level of a system may limit what may be [[Anchoring|anchored]] in that system. <ref>[https://www.eveonline.com/news/view/starbase-changes-for-crius Dev blog: Starbase changes for Crius]</ref>
 * 0.9 - 1.0: Containers may NOT be anchored. Starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system [[sovereignty]].
@@ Line 170: / Line 170: @@
 Many security related mechanics use the true security instead of the rounded security status, however. A lower True-Sec system has better mission pay-outs than a higher True-Sec system, even if the displayed sec status is the same.
-The true security is not visible anywhere in game, instead it can be found in the [https://community.eveonline.com/community/fansites/toolkit/ official datadump] or from [https://esi.tech.ccp.is/latest/#/ ESI API]. Many third party mapping tools such as [https://evemaps.dotlan.net/ Dotlan] also show the true security.
+The true security is not visible anywhere in game, instead it can be found in the [https://community.testeveonline.com/community/fansites/toolkit/ official datadump] or from [https://esi.tech.ccp.is/latest/#/ ESI API]. Many third party mapping tools such as [https://evemaps.dotlan.net/ Dotlan] also show the true security.
 {{expansion past|width=50%|1=In the past, truesec values in the range (0.0, 0.5) were rounded half up, i.e. rounded down to 0.0 because all numbers in that range are below 0.5.  This was a bug, because EVE considers all systems above a truesec rating of 0.0 to be lowsec but the game displayed their security level as "0.0".  This bug not only caused some confusion (there were sentry guns within apparently Null-Sec systems) but also some problems in the form of inadvertent security status loss in what seemed like Null-Sec.