User Tools
eve:sovereignty:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
eve:sovereignty:start [2017/02/12 01:43] conscript |
eve:sovereignty:start [2017/02/13 22:19] (current) conscript created |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| ====Territorial Claim Unit==== | ====Territorial Claim Unit==== | ||
| - | **[[eve:sovereignty:territorial_claim_unit|Territorial Claim Units]]** or TCUs are essentially flags put up by an alliance. Whoever owns the TCU in a system will be listed on the starmap as the owner of the system.\\ | + | **[[territorial_claim_unit|Territorial Claim Units]]** or TCUs are essentially flags put up by an alliance. Whoever owns the TCU in a system will be listed on the starmap as the owner of the system.\\ |
| TCUs do have one tangible benefit, though, by way of a 25% reduction in fuel consumption to any Player-Owned Starbase owned by the same alliance in that system. | TCUs do have one tangible benefit, though, by way of a 25% reduction in fuel consumption to any Player-Owned Starbase owned by the same alliance in that system. | ||
| Line 36: | Line 36: | ||
| ====Infrastructure Hub==== | ====Infrastructure Hub==== | ||
| - | **[[eve:sovereignty:infrastructure_hub|Infrastructure Hubs]]** or I-Hubs are used to upgrade the system, allowing it to spawn more Combat Anomalies, Ore Sites, or Signatures, or allowing the owner to set up more advanced POS structures such as Jump Bridges or system-wide Cynosural Field Jammers. Maintaining an I-Hub costs an upkeep bill which is charged to the alliance wallet.\\ | + | **[[infrastructure_hub|Infrastructure Hubs]]** or I-Hubs are used to upgrade the system, allowing it to spawn more Combat Anomalies, Ore Sites, or Signatures, or allowing the owner to set up more advanced POS structures such as Jump Bridges or system-wide Cynosural Field Jammers. Maintaining an I-Hub costs an upkeep bill which is charged to the alliance wallet.\\ |
| Upgrades, which are actual items that must be produced and delivered to the I-Hub for installation, are unlocked by achieving specific System Index Levels. | Upgrades, which are actual items that must be produced and delivered to the I-Hub for installation, are unlocked by achieving specific System Index Levels. | ||
| Line 43: | Line 43: | ||
| ====Station==== | ====Station==== | ||
| - | **[[eve:sovereignty:station|Stations]]** are very similar to the ones found in high-sec, but with a few exceptions. The owner of the station can choose who is allowed to dock at the station. Maintaining a station costs an upkeep bill which is charged to the alliance wallet. Station services such as fitting and cloning can be disabled by attackers by activating an [[eve:sovereignty:entosis|entosis link]] on those services. Station owners can re-activate the services by using an entosis node on the disabled service. | + | **[[outposts|Stations]]** are very similar to the ones found in high-sec, but with a few exceptions. The owner of the station can choose who is allowed to dock at the station. Maintaining a station costs an upkeep bill which is charged to the alliance wallet. Station services such as fitting and cloning can be disabled by attackers by activating an **[[entosis|entosis link]]** on those services. Station owners can re-activate the services by using an entosis node on the disabled service. |
| ---- | ---- | ||
| Line 157: | Line 157: | ||
| ====Changing the Vulnerability Window==== | ====Changing the Vulnerability Window==== | ||
| To stop an alliance shifting vulnerability timers at short notice in an attempt to avoid an impending attack, it takes 96 hours for a change in the vulnerability window to take effect. At the end of this 96 hour waiting period, the structure will be vulnerable twice within the same 24 hour period, during both the old window and the new one. From then on, the new vulnerability window setting takes effect. | To stop an alliance shifting vulnerability timers at short notice in an attempt to avoid an impending attack, it takes 96 hours for a change in the vulnerability window to take effect. At the end of this 96 hour waiting period, the structure will be vulnerable twice within the same 24 hour period, during both the old window and the new one. From then on, the new vulnerability window setting takes effect. | ||
| + | |||
| + | |||
| + | ---- | ||
| ====ADM Scaling==== | ====ADM Scaling==== | ||
| The default length of the vulnerability window is 18 hours, but this can be reduced by increasing the ADM of the system. The length of the window is 18 hours divided by the ADM. This gives a window ranging from 18 hours for ADM 1, to 3 hours for ADM 6. The length of each day's vulnerability window is locked in at the midpoint of the vulnerability window the day before. This is to ensure that players are not surprised by last minute changes to the window. | The default length of the vulnerability window is 18 hours, but this can be reduced by increasing the ADM of the system. The length of the window is 18 hours divided by the ADM. This gives a window ranging from 18 hours for ADM 1, to 3 hours for ADM 6. The length of each day's vulnerability window is locked in at the midpoint of the vulnerability window the day before. This is to ensure that players are not surprised by last minute changes to the window. | ||
eve/sovereignty/start.1486863818.txt.gz · Last modified: 2017/02/12 01:43 by conscript