System security: Difference between revisions

Line 26:

=== 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, ~~Nullsec~~, 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, 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.

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 ~~nullsec~~ the gloves are off: [[Frigate#Stealth Bombers|stealth bombers]] can use bombs and players can deploy [[Gate Games#Bubbles|bubbles]]; players frequently fly under not-blue-shoot-it ('NBSI') rules of engagement.

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: [[Frigate#Stealth Bombers|stealth bombers]] can use bombs and players can deploy [[Gate Games#Bubbles|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.

Line 34:

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

NPC ~~NullSec~~ 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 null-security 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 ~~NullSec~~:

Regions classified as NPC Null-Sec:

* '''Curse''', ''claimed by Angel Cartel''

* '''Great Wildlands''', ''claimed by Thukker Tribe''

Line 46:

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

In the rest of ~~nullsec~~ sovereignty is claimed (or contested!) by capsuleer alliances. Any stations in claimable ~~nullsec~~ 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 ~~nullsec~~, unless in a fleet lead by an [[ILN]] Officer, in order to preserve the University's neurality. 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 [http://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 neurality. 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 [http://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]].}}

A regularly-updated map of player-owned territory is available [http://go-dl1.eve-files.com/media/corp/Verite/influence.png here].

Regions classified as Claimable ~~NullSec~~:

Regions classified as Claimable Null-Sec:

* '''[http://evemaps.dotlan.net/map/Branch Branch]'''

* '''[http://evemaps.dotlan.net/map/Cache Cache]'''

Line 94:

-->

In terms of security mechanics, Wormhole Space ("w-space" or "j-space") is similar to ~~nullsec~~: [[CONCORD]] does not monitor what happens in wormhole pockets, players can use bombs and bubbles at will and aggression will not impact player security status.

In terms of security mechanics, Wormhole Space ("w-space" or "j-space") is similar to Null-Sec: [[CONCORD]] does not monitor what happens in wormhole pockets, players can use bombs and bubbles at will and aggression will not impact player security status.

W-space also functions differently from known space ("k-space") in that players do not appear in the Local chat channel until they speak in it. This means there could be 1 player or 100 players in a wormhole system and you would not be able to tell the difference just by looking at the local window.

Line 171:

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 [http://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 trusec 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 ~~nullsec~~ systems) but also some problems in the form of inadvertent security status loss in what seemed like ~~nullsec~~.

{{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 trusec 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.

This bug was fixed in the [[Expansion#Revelations|Revelations expansion]] <ref name="Revelations I">[http://www.eveonline.com/updates/patchnotes.asp?patchlogid=99 Revelations I patch notes]</ref>, and the game now uses the rules above. This ensures that any system displayed as "0.0" is truly ~~nullsec~~. Some third-party utilities may not know of the above rules, and so may incorrectly identify some lowsec systems as ~~nullsec~~.}}

This bug was fixed in the [[Expansion#Revelations|Revelations expansion]] <ref name="Revelations I">[http://www.eveonline.com/updates/patchnotes.asp?patchlogid=99 Revelations I patch notes]</ref>, and the game now uses the rules above. This ensures that any system displayed as "0.0" is truly Null-Sec. Some third-party utilities may not know of the above rules, and so may incorrectly identify some lowsec systems as Null-Sec.}}

==References==

@@ Line 26: / Line 26: @@
 === 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, Nullsec, 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, 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.
-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 nullsec the gloves are off: [[Frigate#Stealth Bombers|stealth bombers]] can use bombs and players can deploy [[Gate Games#Bubbles|bubbles]]; players frequently fly under not-blue-shoot-it ('NBSI') rules of engagement.
+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: [[Frigate#Stealth Bombers|stealth bombers]] can use bombs and players can deploy [[Gate Games#Bubbles|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.
@@ Line 34: / Line 34: @@
 ==== NPC null security space====
-NPC NullSec 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 null-security 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 NullSec:
+Regions classified as NPC Null-Sec:
 * '''Curse''', ''claimed by Angel Cartel''
 * '''Great Wildlands''', ''claimed by Thukker Tribe''
@@ Line 46: / Line 46: @@
 ==== Claimable null security space====
 {{main|Sovereignty}}
-In the rest of nullsec sovereignty is claimed (or contested!) by capsuleer alliances. Any stations in claimable nullsec 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 nullsec, unless in a fleet lead by an [[ILN]] Officer, in order to preserve the University's neurality. 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 [http://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 neurality. 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 [http://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]].}}
 A regularly-updated map of player-owned territory is available [http://go-dl1.eve-files.com/media/corp/Verite/influence.png here].
-Regions classified as Claimable NullSec:
+Regions classified as Claimable Null-Sec:
 * '''[http://evemaps.dotlan.net/map/Branch Branch]'''
 * '''[http://evemaps.dotlan.net/map/Cache Cache]'''
@@ Line 94: / Line 94: @@
 {{:Wormhole Space}}
 -->
-In terms of security mechanics, Wormhole Space ("w-space" or "j-space") is similar to nullsec: [[CONCORD]] does not monitor what happens in wormhole pockets, players can use bombs and bubbles at will and aggression will not impact player security status.
+In terms of security mechanics, Wormhole Space ("w-space" or "j-space") is similar to Null-Sec: [[CONCORD]] does not monitor what happens in wormhole pockets, players can use bombs and bubbles at will and aggression will not impact player security status.
 W-space also functions differently from known space ("k-space") in that players do not appear in the Local chat channel until they speak in it. This means there could be 1 player or 100 players in a wormhole system and you would not be able to tell the difference just by looking at the local window.
@@ Line 171: / Line 171: @@
 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 [http://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 trusec 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 nullsec systems) but also some problems in the form of inadvertent security status loss in what seemed like nullsec.
+{{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 trusec 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.
-This bug was fixed in the [[Expansion#Revelations|Revelations expansion]] <ref name="Revelations I">[http://www.eveonline.com/updates/patchnotes.asp?patchlogid=99 Revelations I patch notes]</ref>, and the game now uses the rules above.  This ensures that any system displayed as "0.0" is truly nullsec.  Some third-party utilities may not know of the above rules, and so may incorrectly identify some lowsec systems as nullsec.}}
+This bug was fixed in the [[Expansion#Revelations|Revelations expansion]] <ref name="Revelations I">[http://www.eveonline.com/updates/patchnotes.asp?patchlogid=99 Revelations I patch notes]</ref>, and the game now uses the rules above.  This ensures that any system displayed as "0.0" is truly Null-Sec.  Some third-party utilities may not know of the above rules, and so may incorrectly identify some lowsec systems as Null-Sec.}}
 ==References==