More actions
m Change link to reference. Update link. Remove {{Main}} to non-existing article. |
|||
| Line 22: | Line 22: | ||
=== Territorial Claim Unit === | === Territorial Claim Unit === | ||
{{main|Territorial Claim Unit}} | {{main|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 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. | ||
| Line 29: | Line 28: | ||
=== Infrastructure Hub === | === Infrastructure Hub === | ||
Infrastructure Hubs or I-Hubs are used to upgrade the system, allowing it to spawn more [[Cosmic Anomalies|Combat Anomalies, Ore Sites]], or [[Cosmic Signatures|Signatures]], or allowing the owner to set up more advanced flex 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 Hubs or I-Hubs are used to upgrade the system, allowing it to spawn more [[Cosmic Anomalies|Combat Anomalies, Ore Sites]], or [[Cosmic Signatures|Signatures]], or allowing the owner to set up more advanced flex 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. | ||
==Claiming Sovereignty == | == Claiming Sovereignty == | ||
The mechanics of capturing and defending structures are based around the use of an [[Entosis Link]]. | The mechanics of capturing and defending structures are based around the use of an [[Entosis Link]]. | ||
===Placing structures=== | === Placing structures === | ||
If a system does not currently have an I-Hub, or TCU a player may place one. | If a system does not currently have an I-Hub, or TCU a player may place one. | ||
Deploying an I-Hub or TCU involves buying or making one, and then launching it in to space (right-click and "launch" or dragging the structure to space). Once this is done the structure is in a neutral state and owned by the SCC. To gain ownership of the structure, a player must activate an entosis link on the structure to capture it. Other alliances are free to attempt to capture the structure while it is in this state. | Deploying an I-Hub or TCU involves buying or making one, and then launching it in to space (right-click and "launch" or dragging the structure to space). Once this is done the structure is in a neutral state and owned by the SCC. To gain ownership of the structure, a player must activate an entosis link on the structure to capture it. Other alliances are free to attempt to capture the structure while it is in this state. | ||
=== Capturing existing structures === | |||
To capture or disable a structure, attackers must first use an entosis link on the structure during its [[#Vulnerability Window | Vulnerability window]]. Once the link has completed its first cycle, the capture process begins and the alliance owning the structure is notified of the attack. Once the entosis link has been active and uncontested for a certain amount of time, the structure enters reinforce mode and a reinforce timer begins. The duration of this timer depends on the type of structure attacked and the Activity Defense Multiplier (ADM) of the system. These timers are all affected by [[Time Dilation]]. | |||
===Capturing existing structures=== | |||
To capture or disable a structure, attackers must first use an | |||
The base timer for each type of structure is: | The base timer for each type of structure is: | ||
* Structure (I-Hub, TCU): 10 minutes | * Structure (I-Hub, TCU): 10 minutes | ||
* Command Node: 4 minutes | * Command Node: 4 minutes | ||
ADM is explained [[#Activity Defense Multiplier | below]]. | ADM is explained [[#Activity Defense Multiplier | below]]. | ||
| Line 60: | Line 52: | ||
The reinforce timer will end at a randomly determined point during the structure vulnerability timer two days later. Once the timer expires, command nodes will begin to spawn in the same constellation as the contested structure. | The reinforce timer will end at a randomly determined point during the structure vulnerability timer two days later. Once the timer expires, command nodes will begin to spawn in the same constellation as the contested structure. | ||
====Command | ==== Command node ==== | ||
Command nodes are objects that appear in space. They are shown on the overview and it is possible to warp to them directly. These nodes can spawn in any system within the constellation, regardless of the owner of that system. Their name in the overview identifies the system they are connected to as well as the structure in that system. They also have a unique ID to help identify which node in a system players are referring to. For example, a command node for the TCU in O1Y-ED may spawn in X36Y-G with the name "O1Y-ED Territorial Claim Unit Command Node NK17". | Command nodes are objects that appear in space. They are shown on the overview and it is possible to warp to them directly. These nodes can spawn in any system within the constellation, regardless of the owner of that system. Their name in the overview identifies the system they are connected to as well as the structure in that system. They also have a unique ID to help identify which node in a system players are referring to. For example, a command node for the TCU in O1Y-ED may spawn in X36Y-G with the name "O1Y-ED Territorial Claim Unit Command Node NK17". | ||
====Command | ====Command node control==== | ||
* Once the reinforce timer for a structure hits 0, command nodes spawn randomly within the constellation. Initially 5 of these spawn, with more spawning as time goes one. Once a node is captured, a new node spawns. | * Once the reinforce timer for a structure hits 0, command nodes spawn randomly within the constellation. Initially 5 of these spawn, with more spawning as time goes one. Once a node is captured, a new node spawns. | ||
* As the command nodes spawn, a progress bar for the structure appears. It starts at 60%. If it reaches 100%, the defenders have won. If it reaches 0%, the attackers have won. | * As the command nodes spawn, a progress bar for the structure appears. It starts at 60%. If it reaches 100%, the defenders have won. If it reaches 0%, the attackers have won. | ||
| Line 72: | Line 64: | ||
* Once one side has won the event, all other nodes related to that structure will self-destruct. | * Once one side has won the event, all other nodes related to that structure will self-destruct. | ||
====After the event==== | ==== After the event ==== | ||
If the defender wins the command node event, the structure being fought for becomes invulnerable and will remain that way until the next vulnerability window occurs. If the attacker wins, the next steps depend on the type of structure being attacked. For I-Hubs and TCUs, the existing structure explodes. This allows anyone to anchor their own structure in space to replace the old one. | If the defender wins the command node event, the structure being fought for becomes invulnerable and will remain that way until the next vulnerability window occurs. If the attacker wins, the next steps depend on the type of structure being attacked. For I-Hubs and TCUs, the existing structure explodes. This allows anyone to anchor their own structure in space to replace the old one. | ||
==== Regeneration ==== | |||
====Regeneration==== | |||
Structures that have been attacked but not reinforced and command nodes all have defensive regeneration. This means that if the structure is left uncontested, eventually the defending side will win. The maximum regeneration times are as follows: | Structures that have been attacked but not reinforced and command nodes all have defensive regeneration. This means that if the structure is left uncontested, eventually the defending side will win. The maximum regeneration times are as follows: | ||
| Line 97: | Line 88: | ||
[[File:Sovfullcaptureevents.jpg]] | [[File:Sovfullcaptureevents.jpg]] | ||
==Activity Defense Multiplier== | == Activity Defense Multiplier == | ||
The length of time it takes to reinforce a structure or capture a command node depends on the Activity Defense Multiplier (ADM) for the system. This rewards an alliance for holding and being active in the system, making it easier for them to defend. | The length of time it takes to reinforce a structure or capture a command node depends on the Activity Defense Multiplier (ADM) for the system. This rewards an alliance for holding and being active in the system, making it easier for them to defend. | ||
| Line 108: | Line 99: | ||
* Industrial Index: Increases in proportion to the volume of ore mined in the system. | * Industrial Index: Increases in proportion to the volume of ore mined in the system. | ||
In terms of the Industry index: mining waste is [https://forums.eveonline.com/t/from-extraction-to-production-update/337887#mining-efficiency-2 | In terms of the Industry index: mining waste is NOT<ref>EVE forum: [https://forums.eveonline.com/t/from-extraction-to-production-update/337887#mining-efficiency-2 From Extraction To Production: Update] By CCP Psych 2021-11-10. Accessed 2023-06-30.</ref> going to be part of the ADM calculation. | ||
Each of these indices has a level between 0 and 5. To determine the current ADM of a system, find the corresponding modifier for each of the system's indices in the table, then add them all to the base value of 1. For example, a system with Military Index 3 (+1.7), Industrial Index 1 (+0.6) and Strategic Index 5 (+1.0) would have an ADM of 1.0 + 1.7 + 0.6 + 1.0 = 4.3. The maximum value for ADM is 6, which would extend the time taken to reinforce a structure to 60 minutes, or capture a command node to 24 minutes for an attacker. As 6 is the maximum ADM, if the calculation produces a value above 6, the ADM for the system will be 6. | Each of these indices has a level between 0 and 5. To determine the current ADM of a system, find the corresponding modifier for each of the system's indices in the table, then add them all to the base value of 1. For example, a system with Military Index 3 (+1.7), Industrial Index 1 (+0.6) and Strategic Index 5 (+1.0) would have an ADM of 1.0 + 1.7 + 0.6 + 1.0 = 4.3. The maximum value for ADM is 6, which would extend the time taken to reinforce a structure to 60 minutes, or capture a command node to 24 minutes for an attacker. As 6 is the maximum ADM, if the calculation produces a value above 6, the ADM for the system will be 6. | ||
| Line 148: | Line 139: | ||
|} | |} | ||
===Capital | === Capital systems === | ||
Major staging systems aren't necessarily a safe place for activities that boost Military or Industrial indices, which can have a negative effect on the ADM for those systems. This could make it more difficult for an alliance to defend their home system. To counter this, each alliance is able to designate one system as its Capital system. The alliance must own the TCU in the system it chooses. The system set as the Capital system will have a +2 bonus to the ADM. The maximum ADM is still 6x, the capital boost acts purely as a mechanism to make it easier to reach ADM 6. Changing the capital system of an alliance takes several days to take effect. | Major staging systems aren't necessarily a safe place for activities that boost Military or Industrial indices, which can have a negative effect on the ADM for those systems. This could make it more difficult for an alliance to defend their home system. To counter this, each alliance is able to designate one system as its Capital system. The alliance must own the TCU in the system it chooses. The system set as the Capital system will have a +2 bonus to the ADM. The maximum ADM is still 6x, the capital boost acts purely as a mechanism to make it easier to reach ADM 6. Changing the capital system of an alliance takes several days to take effect. | ||
===Raising | === Raising indices === | ||
In 2009, CCP posted this chart indicating the time required to raise strategic index levels.<ref>Devblog: [https://www.eveonline.com/news/view/upgrading-and-upkeep-of-sovereign-solar-systems-in-dominion Upgrading And Upkeep Of Sovereign Solar Systems In Dominion] By CCP Chronotis 2009-11-07. Accessed 2023-06-30.</ref> The exact formula for raising of the other indices is unknown. | |||
In 2009, CCP posted this chart indicating the time required to raise strategic index levels.<ref>[https://www.eveonline.com/ | |||
{| class="wikitable" | {| class="wikitable" | ||
| Line 175: | Line 165: | ||
|} | |} | ||
==Vulnerability | == Vulnerability window == | ||
Structures are not vulnerable to attack 24 hours a day. Each alliance has a window of time set during which their structures are vulnerable to attack. This is usually their "prime time" where they are best able to fend off any attacks. Newly deployed or captured structures will inherit this setting from the alliance that controls it. However, the alliance can choose to change the window of any structure the default setting to a custom value. If a structure is partially captured at the end of a vulnerability window, it will remain vulnerable until it is either reinforced or successfully defended. | Structures are not vulnerable to attack 24 hours a day. Each alliance has a window of time set during which their structures are vulnerable to attack. This is usually their "prime time" where they are best able to fend off any attacks. Newly deployed or captured structures will inherit this setting from the alliance that controls it. However, the alliance can choose to change the window of any structure the default setting to a custom value. If a structure is partially captured at the end of a vulnerability window, it will remain vulnerable until it is either reinforced or successfully defended. | ||
=== Changing the vulnerability window === | |||
===Changing the | |||
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. | ||
==References== | == References == | ||
<references /> | |||