More actions
| Line 41: | Line 41: | ||
The mechanics of capturing and defending structures is based around the use of an [[Entosis Link]]. | The mechanics of capturing and defending structures is based around the use of an [[Entosis Link]]. | ||
===Placing structures=== | |||
If a system does not currently have an I-Hub, TCU or Station, a player may place one. Deploying a station requires the players alliance owning the TCU in the system. | |||
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. | |||
Stations work differently; once deployed and after the next downtime, the station will belong to the corporation that deployed it. | |||
===Capturing existing structures=== | |||
To capture or disable a structure, attackers must first use an Entosis Link on the structure during its [[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 timer depends on the type of structure attacked and the ADM of the system. | To capture or disable a structure, attackers must first use an Entosis Link on the structure during its [[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 timer depends on the type of structure attacked and the ADM of the system. | ||
| Line 57: | Line 66: | ||
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 N17". | 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 N17". | ||
===Command Node control=== | ====Command Node control==== | ||
* Once the reinforce timer for a structure hits 0, command nodes spawn randomly within the constellation. Initially X of these spawn, with a further X spawning later. | * Once the reinforce timer for a structure hits 0, command nodes spawn randomly within the constellation. Initially X of these spawn, with a further X spawning later. | ||
* 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 64: | Line 73: | ||
* Any entosis link activated by a player not in the defending alliance is counted as attacking. This means that and alliance can not enlist other entities to defend their structures with entosis links. | * Any entosis link activated by a player not in the defending alliance is counted as attacking. This means that and alliance can not enlist other entities to defend their structures with entosis links. | ||
===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 a station is attacked, it enters Freeport mode. This allows any player to dock at the station. It remains in this state for 48 hours, at which point a new command node control event begins. The winner of this event gains control of the station. | 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 a station is attacked, it enters Freeport mode. This allows any player to dock at the station. It remains in this state for 48 hours, at which point a new command node control event begins. The winner of this event gains control of the station. | ||