More actions
m Update Expansions link. |
m Change unneeded piped link, making use of redirect and the link end trick. |
||
| Line 15: | Line 15: | ||
=== Empire space === | === 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 which the four main NPC factions hold sovereignty (High Security and Low Security). In Empire space, whether high or low security, [[ | |||
==== High security ==== | ==== 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, High-sec, Highsec, Hi-sec, and Hisec. | ||
| Line 25: | Line 23: | ||
==== Low security ==== | ==== 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, 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 | 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 === | ||
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, 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 Null-Sec the gloves are off: [[ | 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 to NPC null and claimable null. | ||
==== NPC null security space ==== | ==== NPC null security 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 null-security space where the sovereignty is claimed by NPC factions, similar to normal 'Empire' space, and therefore cannot be claimed by [[capsuleer]] alliances. | ||
| Line 128: | Line 123: | ||
=== High security space === | === High security space === | ||
* [[CONCORD]] destroys any criminal player. | * [[CONCORD]] destroys any criminal player. | ||
* [[ | * [[NPC]] navies will chase players with very low [[NPC standings#Faction standings|faction standing]]. | ||
* Player with a a sufficiently low security status (below -2.0) may be [[Security Status Details#Security Status and Traveling Restrictions|attacked by NPC faction navy ships]]. | * Player with a a sufficiently low security status (below -2.0) may be [[Security Status Details#Security Status and Traveling Restrictions|attacked by NPC faction navy ships]]. | ||
* True [[ | * True [[capital ships]] (i.e. ships that specifically require the {{sk|Capital Ships}} skill) may not enter high security space. | ||
* [[ | * [[Cynosural field]]s cannot create beacons for jump drives. | ||
=== Low security space === | === Low security space === | ||
* [[CONCORD]] no longer responds, however [[NPC]] guns on gates and stations will respond to illegal aggression. | |||
* [[CONCORD]] no longer responds, however [[ | |||
* [[Player-Owned Starbases]] do not require Empire Charters to operate. | * [[Player-Owned Starbases]] do not require Empire Charters to operate. | ||
=== Null security space === | === Null security space === | ||
* [[PvP]] aggression does not change player security status. | |||
* [[ | |||
* Items flagged with the Banned in Empire Space attribute can now be used, including launching [[bombs]], anchoring [[EVE Lexicon#Warp bubble|bubbles]], and firing doomsdays. | * Items flagged with the Banned in Empire Space attribute can now be used, including launching [[bombs]], anchoring [[EVE Lexicon#Warp bubble|bubbles]], and firing doomsdays. | ||
* Sentry guns do not take any actions towards players who aggress other players. | * Sentry guns do not take any actions towards players who aggress other players. | ||
=== Wormhole space === | === Wormhole space === | ||
* Local chat does '''''not''''' display all capsuleers currently in the system, only those that have recently spoken in Local. | * Local chat does '''''not''''' display all capsuleers currently in the system, only those that have recently spoken in Local. | ||
** Frequent and heavy use of the [[ | ** Frequent and heavy use of the [[directional scanner]] is recommended. | ||
* No stargates are present, [[wormholes]] are the sole means of travel. | * No stargates are present, [[wormholes]] are the sole means of travel. | ||
* As truesec -1.0, w-space has the highest concentrations of [[Planetary Commodities|planetary resources]]. | * As truesec -1.0, w-space has the highest concentrations of [[Planetary Commodities|planetary resources]]. | ||
* Aggression [[timers]] do not restrict jumping through [[wormholes]] as they do with [[stargates]] and docking. However, every individual wormhole has a one-way 5-minute 'Polarization' timer on it, which restricts multiple repeated jumps through it. | * Aggression [[timers]] do not restrict jumping through [[wormholes]] as they do with [[stargates]] and docking. However, every individual wormhole has a one-way 5-minute 'Polarization' timer on it, which restricts multiple repeated jumps through it. | ||
* [[ | * [[Cynosural field]]s cannot create links to other systems; jump drives cannot be used to enter or leave systems in wormhole space. | ||
=== Pochven === | === Pochven === | ||
| Line 160: | Line 152: | ||
* Stations and stargates do not have traditional gate guns. However, they may or may not have multiple Entropic Disintegrator Werposts, which will attack any pilots with negative Triglavian Collective standings. | * Stations and stargates do not have traditional gate guns. However, they may or may not have multiple Entropic Disintegrator Werposts, which will attack any pilots with negative Triglavian Collective standings. | ||
* Aggression [[timers]] do not restrict jumping through [[wormholes]], however they do restrict stargates and docking. | * Aggression [[timers]] do not restrict jumping through [[wormholes]], however they do restrict stargates and docking. | ||
* [[ | * [[Cynosural field]]s cannot be lit within Pochven and so jump drives cannot be used to enter the region. However, capital ships in Pochven can use their jump drives to permanently ''leave'' the region. | ||
=== Anchoring === | === 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://community.eveonline.com/news/dev-blogs/starbase-changes-for-crius/ Dev blog: Starbase changes for Crius]</ref> | ||
| Line 169: | Line 160: | ||
* 0.5 - 0.8: Containers, starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system [[sovereignty]]. | * 0.5 - 0.8: Containers, starbases and starbase structures may be anchored except for structures requiring anchoring corp to have system [[sovereignty]]. | ||
* 0.0 - 0.4: All containers and starbase structures may be anchored, except structures requiring anchoring corp to have system [[sovereignty]]. <ref>https://forums.eveonline.com/default.aspx?g=posts&m=4707013#post4707013</ref> | * 0.0 - 0.4: All containers and starbase structures may be anchored, except structures requiring anchoring corp to have system [[sovereignty]]. <ref>https://forums.eveonline.com/default.aspx?g=posts&m=4707013#post4707013</ref> | ||
* -1.0 - 0.0: All containers and starbase structures may be anchored, assuming that anchoring corp has system [[sovereignty]]. Player-built stations may be constructed in systems where the corp building the station has | * -1.0 - 0.0: All containers and starbase structures may be anchored, assuming that anchoring corp has system [[sovereignty]]. Player-built stations may be constructed in systems where the corp building the station has sovereignty (as of this writing, player-built stations are completely indestructible and are limited to one station per system). | ||
== True security == | == True security == | ||
A given system's security level is actually a real number between -1.0 and 1.0 to 5 decimal places (this is known as the system's True Security Level, True-Sec, or Truesec). It is rounded and displayed as the system's security level according to the following rules. | A given system's security level is actually a real number between -1.0 and 1.0 to 5 decimal places (this is known as the system's True Security Level, True-Sec, or Truesec). It is rounded and displayed as the system's security level according to the following rules. | ||
| Line 182: | Line 172: | ||
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.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. | ||
{{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 | {{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. | ||
This bug was fixed in the [[Expansions#Revelations|Revelations]] expansion <ref name="Revelations I">[https://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.}} | This bug was fixed in the [[Expansions#Revelations|Revelations]] expansion <ref name="Revelations I">[https://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 == | == References == | ||
<references/> | <references /> | ||
[[Category:Game mechanics]] | [[Category:Game mechanics]] | ||