Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Enta en bauldry/SOV: Difference between revisions

From EVE University Wiki
No edit summary
 
Line 16: Line 16:
==Claiming SOV==
==Claiming SOV==
To claim and maintain sovereignty over a system, knowledge of the various mechanics surrounding SOV is required.  
To claim and maintain sovereignty over a system, knowledge of the various mechanics surrounding SOV is required.  
===General Mechanics===
=====Capital, Vulnerability Window and Indexes=====
=====Entosis Link=====
Entosis Link


===Structures===
===Structures===
Structures erected by players are central to sovereignty gameplay. They must be attacked and defended to have a meaningful impact on the SOV landspace. Structures are vulnerable at certain times of the day. Further explanation of transferring control of structures will follow after each structure is introduced.
Structures erected by players are central to sovereignty gameplay. They must be attacked and defended to have a meaningful impact on the SOV landspace. Structures are vulnerable at certain times of the day. Further explanation of transferring control of structures will follow after each structure is introduced.


=====Territory Claim Unit=====
=====Territorial Claim Unit=====
The Territory Claim Unit or TCU is what literally puts your alliance on the map. When active and under your control, your alliance will show up on the sovereignty map, your logo will be displayed on the TCU and any alliance-owned starbases -not stations- in system will recieve a 25% reduction in fuel consumption.
The Territory Claim Unit or TCU is what literally puts your alliance on the map. When active and under your control, your alliance will show up on the sovereignty map, your logo will be displayed on the TCU and any alliance-owned starbases -not stations- in system will receive a 25% reduction in fuel consumption. Only one Territorial Claim Unit may be active in a given system.
 
To capture a TCU, the aggressor alliance(s) must activate an entosis link on it during the daily vulnerability window. After successful reinforcement of the TCU, the aggressor alliance must return to complete the capture.


=====Infrastructure Hub=====
=====Infrastructure Hub=====
The Infrastructure Hub or IHub enhances the properties of a system based on the choice of the owner organization. The IHub has a daily ISK cost for  maintenance. The costs are based the upgrades employed on the IHub and the levels of the upgrades.
The Infrastructure Hub or IHub enhances the properties of a system based on the choice of the owner organization. The IHub has a daily ISK cost for  maintenance. The costs are based the upgrades employed on the IHub and the levels of the upgrades.
To capture an IHub, the aggressor alliance(s) must activate an entosis link on it during the daily vulnerability window. After successful reinforcement of the TCU, the aggressor alliance must return to complete the capture.


=====Outpost=====
=====Outpost=====
Line 31: Line 41:
===Entosis Link===
===Entosis Link===
Central to any attempt at capturing a system is the Entosis Link module. It may be fitted on a high slot of any ship with adequate powergrid.
Central to any attempt at capturing a system is the Entosis Link module. It may be fitted on a high slot of any ship with adequate powergrid.
*Are TCU's indestructible, can they be unanchored?
*When TCU/IHubs are reinforced, who can entosis it to capture it. Is it an a sort of "neutral state" or is it a contest between the initial aggressor and defender?