Difference between revisions of "Territorial Claim Unit"

From EVE University Wiki
Jump to: navigation, search
m (Add link.)
(Update for patch 22.01 Release 2024-10-29.1)
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
| border= red
 
| border= red
 
|Territorial Claim Unit(TCU) will be phased out with the Equinox expansion ([https://www.eveonline.com/news/view/equinox-expansion-notes Patch notes]).
 
|Territorial Claim Unit(TCU) will be phased out with the Equinox expansion ([https://www.eveonline.com/news/view/equinox-expansion-notes Patch notes]).
* TCUs will continue to represent the legacy claim in a system that hasn't yet had a Sovereignty Hub deployed, or where the IHub hasn't yet transitioned.
+
* TCUs will continue to represent the legacy claim in a system that hasn't yet had a [[Sovereignty Hub]] deployed, or where the Infrastructure Hub(IHub) hasn't yet transitioned.
 
* New TCUs can no longer be deployed or captured if they were previously deployed but not captured.
 
* New TCUs can no longer be deployed or captured if they were previously deployed but not captured.
 
* Any ongoing TCU campaigns will be cancelled.
 
* Any ongoing TCU campaigns will be cancelled.
Line 12: Line 12:
 
Transition (Planned for <s>20 June 2024</s> 27 June 2024) [https://www.eveonline.com/news/view/equinox-expands-a-new-update Delay reason]
 
Transition (Planned for <s>20 June 2024</s> 27 June 2024) [https://www.eveonline.com/news/view/equinox-expands-a-new-update Delay reason]
  
Upon transition of the sovereignty hub operating in legacy IHub mode into Sov Hub mode any TCU in the system will be removed and transferred to the owning corporation HQ station.
+
Upon transition of the sovereignty hub(SovHub) operating in legacy IHub mode into SovHub mode any TCU in the system will be removed and transferred to the owning corporation HQ station.
  
The transfer period will end with the next expansion, when any sovereignty hub operating in legacy IHub mode will be automatically transitioned into Sov Hub mode.
+
The transfer period will end with the next expansion, when any sovereignty hub operating in legacy IHub mode will be automatically transitioned into SovHub mode.
 +
 
 +
Transfer period ended on 29 October 2024 [https://www.eveonline.com/news/view/patch-notes-version-22-01 Patch notes Release 2024-10-29.1]
  
 
For an in-depth explanation of the SovHub transition, you can visit the [https://www.eveonline.com/news/view/sovereignty-structures-and-transition Sovereignty, Structures & Transition devblog]. More info: [https://www.eveonline.com/news/view/sovereignty-updates-transition-and-upgrades Sovereignty Updates: Transition & Upgrades]
 
For an in-depth explanation of the SovHub transition, you can visit the [https://www.eveonline.com/news/view/sovereignty-structures-and-transition Sovereignty, Structures & Transition devblog]. More info: [https://www.eveonline.com/news/view/sovereignty-updates-transition-and-upgrades Sovereignty Updates: Transition & Upgrades]

Latest revision as of 11:51, 29 October 2024

Territorial Claim Unit(TCU) will be phased out with the Equinox expansion (Patch notes).
  • TCUs will continue to represent the legacy claim in a system that hasn't yet had a Sovereignty Hub deployed, or where the Infrastructure Hub(IHub) hasn't yet transitioned.
  • New TCUs can no longer be deployed or captured if they were previously deployed but not captured.
  • Any ongoing TCU campaigns will be cancelled.
  • TCUs can no longer be targeted by entosis and so cannot be used to remove a claim.
  • Instead, an attacker must usurp the claim by capturing the Sovereignty Hub in the system.

Transition (Planned for 20 June 2024 27 June 2024) Delay reason

Upon transition of the sovereignty hub(SovHub) operating in legacy IHub mode into SovHub mode any TCU in the system will be removed and transferred to the owning corporation HQ station.

The transfer period will end with the next expansion, when any sovereignty hub operating in legacy IHub mode will be automatically transitioned into SovHub mode.

Transfer period ended on 29 October 2024 Patch notes Release 2024-10-29.1

For an in-depth explanation of the SovHub transition, you can visit the Sovereignty, Structures & Transition devblog. More info: Sovereignty Updates: Transition & Upgrades


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 are deployed near planets and can be destroyed or secured by using an Entosis Link.

Deploying

To set up a TCU for an alliance, you must meet the following criteria:

  • You must be in a player corporation which is in the alliance.
  • You must have the skill Anchoring trained to at least Level I (needs re-verification, possibly removed with corp roles[Verify])
  • You must have a target system that is in sovereign nullsec (not NPC-controlled) that does not currently have a TCU deployed.
  • You must be near a planet. You can be as close as 350km from the planet or as far as the warp-in distance plus another 1,000km.
  • To claim the TCU for your alliance, you must have an Entosis Link fitted.

You can right click the TCU in your cargo hold, use the radial menu, or simply drag-and-drop it into space to deploy it. The TCU may appear far away, as it's programmed to center itself on the nearest available grid, avoiding any overlap with other structures or ships. When first deployed a TCU is owned by the NPC Secure Commerce Commission. You'll have to capture it through an Entosis Link to actually claim ownership.

Capturing

Once a TCU is in space, it is visible on the overview of every pilot in the system. Anyone with an Entosis Link who is a member of a player alliance can attempt to capture the TCU during its Vulnerability Window.

If a TCU is successfully captured, it enters a reinforcement period until a random time during its vulnerability window two days later. When the reinforcement period ends, a Capture Event will begin in the constellation where the TCU is located. 5 Command Nodes will spawn in random systems in the constellation. The Capture Event will continue until one side wins total control of the "tug-of-war." Each Command Node is worth 7% control, and the contest begins 60-40 in favor of the defender. This means that the owner can successfully defend the TCU if they capture 6 Nodes without giving up any to the attackers. Conversely, this means the attackers have to capture a minimum of 9 Nodes.

Each Command Node's capture time has a base value of 4 minutes, multiplied for the attackers by the Activity Defense Multiplier of the system in which the TCU is located. The Activity Defense Multiplier of the system in which the Command Node is located in has no effect.

If the Capture Event goes on for very long, the number of active Command Nodes at any one time will increase from the initial 5 up to a max of 10. As soon as one Node is captured, it will despawn and be replaced by another randomly spawned somewhere in the constellation.

If the defenders win the Capture Event, they will secure the TCU and it will become invulnerable until its next window. If the attackers win the Capture Event, the TCU will be destroyed and anyone can deploy a new one and capture it to claim the system for themselves.