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

Triglavian Invasion (Chapter 3): Difference between revisions

From EVE University Wiki
Made article past tense. Added info on aftermath.
Salartarium (talk | contribs)
m proofreading, link maintenance
 
(21 intermediate revisions by 5 users not shown)
Line 3: Line 3:
[[File:Invasion_Ch3_Keyart.jpg|400px|thumb|right|Chapter 3 keyart]]
[[File:Invasion_Ch3_Keyart.jpg|400px|thumb|right|Chapter 3 keyart]]


 
The 3rd and final chapter of the '''Triglavian Invasion''' was [https://www.eveonline.com/news/view/invasion-chapter-3-now-live introduced on May 26th. 2020]. It was a continuation of [[Triglavian Invasion (Chapter 1 & 2)|chapter 1 & 2]] of the Triglavian Invasion, and expanded upon and behaved differently.   
 
The 3rd and final chapter of the '''Triglavian Invasion''' was [https://www.eveonline.com/article/qaxqky/invasion-chapter-3-now-live introduced on May 26th. 2020]. It was a continuation of [[Triglavian Invasion (Chapter 1 & 2)|chapter 1 & 2]] of the Triglavian Invasion, and expanded upon and behaved differently.   


Triglavian Invasions were originally introduced as a new type of PvE content in the Invasion update in May 2019. The new content saw the [[Triglavian Collective]] taking over constellations of known space, and sending out patrols in these systems that attacked capsuleers, with the four empires and [[CONCORD]] unifying their defense initiative under the newly formed [[EDENCOM]]. The third chapter came out in May 2020, one year after chapter 1 began.
Triglavian Invasions were originally introduced as a new type of PvE content in the Invasion update in May 2019. The new content saw the [[Triglavian Collective]] taking over constellations of known space, and sending out patrols in these systems that attacked capsuleers, with the four empires and [[CONCORD]] unifying their defense initiative under the newly formed [[EDENCOM]]. The third chapter came out in May 2020, one year after chapter 1 began.
Line 19: Line 17:
[[File:Triglavian Invasion Agency Tab.jpg|thumb|right|This is the Agency Tab for the Triglavian Invasion Chapter 3]]
[[File:Triglavian Invasion Agency Tab.jpg|thumb|right|This is the Agency Tab for the Triglavian Invasion Chapter 3]]


With the release of chapter 3 of the Triglavian Invasion expansion, the Triglavian Collective began a full-scale invasion of New Eden. Capsuleers could join up and fight for either the Triglavian Collective or for EDENCOM. Doing this would improve the player's standing with the side they helped, while lowering it with the opposing faction.   
With the release of chapter 3 of the Triglavian Invasion expansion, the Triglavian Collective began a full-scale invasion of [[New Eden]]. Capsuleers could join up and fight for either the Triglavian Collective or for EDENCOM. Doing this would improve the player's standing with the side they helped while lowering it with the opposing faction.   


The invasion took place in High-Sec and Low-Sec Empire space, with systems undergoing invasion experiencing a temporary disruption.   
The invasion took place in High-Sec and Low-Sec Empire space, with systems undergoing invasion experiencing a temporary disruption.   
Line 42: Line 40:
Minor victory systems still spawned invasion sites for both sides (more for the winning side) and roaming fleets of the winning side will be present. The winning side may also deploy sentry towers (EDENCOM Gunstars or Entropic Disintegrator Werposts) in the system.
Minor victory systems still spawned invasion sites for both sides (more for the winning side) and roaming fleets of the winning side will be present. The winning side may also deploy sentry towers (EDENCOM Gunstars or Entropic Disintegrator Werposts) in the system.


Minor victory systems could be invaded again.{{verify}}
Minor victory systems could be invaded again, however this was eventually declared to be a bug and patched out. However, prior to this being declared a bug, several Minor Victory systems were invaded repeatedly, and thus acquired multiple separate sets of Minor Victory effects.
 
=== Capsuleer Belligerents ===
 
When the invasion began, Capsuleers quickly began organizing united war fronts on both sides.
 
Supporters of the invasion coalesced largely around the banners of Ashterothi, The Triglavian Initiative, and the Kybernaut Clade [CLKYB], which later split between CLKYB and the splinter group Stribog Kybernaut Subclade [SKS3]. The Kybernauts operated primarily heavily armored fleets, focused on a mix of lasers and Triglavian ships. CLKYB also had support from belligerent hisec organizations, most notably Hogs Collective and CODE.
 
Supporters of the empires coalesced largely around the banners of Darkezero, the EDENCOM Defense Initiative (EDI), and the scientists of the Arataka Research Consortium. EDI operated primarily medium shielded fleets, focused on Artillery and extremely low-cost and low-skill fits for new pilots. EDI also had support from multiple Minmatar and Amarrian Faction Warfare organizations, most notably Electus Matari and Phoenix Naval Systems.
 
In the time since the end of the invasion, CLKYB and EDI have largely dispersed, but each still retain groups of ideological devotees and continue to operate both in Pochven and in formerly-invaded systems.


== Enemy types ==
== Enemy types ==
Forces for the Triglavian Collective and the EDENCOM could be found throughout systems undergoing invasion.
Forces for the Triglavian Collective and the EDENCOM could be found throughout systems undergoing invasion.


*For a overview of NPCs and structures special to the Triglavian Invasion, [[Triglavian Invasion special NPCs|look here]].
*For an overview of NPCs and structures special to the Triglavian Invasion, [[Triglavian Invasion special NPCs|look here]].


*For a overview of the combat sites in these systems, [[Triglavian Invasion combat sites|look here]].
*For an overview of the combat sites in these systems, [[Triglavian Invasion combat sites|look here]].




=== Triglavian NPCs ===
=== Triglavian NPCs ===
The Triglavian Collective ships came in all sizes, from frigates, destroyers, cruisers, battlecruiser and battleships, with even Dreadnoughts being a rare sight in the advanced phases of the invasion.  
The Triglavian Collective ships came in all sizes, from frigates, destroyers, cruisers, battlecruisers and battleships, with even Dreadnoughts being a rare sight in the advanced phases of the invasion.  


Triglavian NPCs in the Triglavian Invasion systems comes in three tiers:  
Triglavian NPCs in the Triglavian Invasion systems come in three tiers:  
{| class="wikitable"
{| class="wikitable"
!
!
Line 72: Line 80:
|Raznaborg <role> <ship type>
|Raznaborg <role> <ship type>
|No prefix <role> <ship type>
|No prefix <role> <ship type>
|Hospidar <role> <ship type>
|Hospodar <role> <ship type>
|Zorya <ship type>
|Zorya <ship type>
|}
|}
Line 91: Line 99:


=== EDENCOM NPCs ===
=== EDENCOM NPCs ===
The EDENCOM forces found and fought depended on what empire space the invasion is taking place in. In Amarr space the EDENCOM forces comprise of Imperial Navy ships, in Minmatar space they comprise of Republic Fleet ships, in Caldari space of Federal Navy ships and in Gallente space of Federal Navy ships.
The EDENCOM forces found and fought depended on what empire space the invasion is taking place in. In Amarr space the EDENCOM forces comprise of Imperial Navy ships, in Minmatar space they comprise of Republic Fleet ships, in Caldari space of State Navy ships and in Gallente space of Federal Navy ships.
 
Note that all NPC ships are either T2 or Faction types (e.g Kirin or Raven Navy Issue).
{| class="wikitable"
{| class="wikitable"
!
!
Line 113: Line 121:
|-
|-
!Caldari
!Caldari
|
|Scout State Navy <ship type>
|
|State Navy <ship type>
|
|Elite State Navy <ship type>
|
|Executive State Navy <ship type>
|-
|-
!Gallente
!Gallente
|
|Scout Federal Navy <ship type>
|
|Federal Navy <ship type>
|
|Elite Federal Navy <ship type>
|
|Presiding Federal Navy <ship type>
|-
|-
!Minmatar
!Minmatar
|
|Scout Republic Fleet <ship type>
|
|Republic Fleet <ship type>
|
|Elite Republic Fleet <ship type>
|
|Chief Republic Fleet <ship type>
|}
|}


Line 138: Line 146:


The Stellar Reconnaissance was the first phase a system can be in, in the 3rd chapter of the Triglavian Invasion. In this phase, neither EDENCOM nor the Triglavian Collective had the upper hand, but  
The Stellar Reconnaissance was the first phase a system can be in, in the 3rd chapter of the Triglavian Invasion. In this phase, neither EDENCOM nor the Triglavian Collective had the upper hand, but  
capsuleers could join either side and help them establish a foothold. If either side succeeded in winning this phase, an industrial ship would spawn to anchor a Stellar Observatory Structure. The two sides then had to help either defeat or protect this industrial ship. If the anchoring was successful the system then escalated towards the next phase, being either a Redoubt or First Liminality.
capsuleers could join either side and help them establish a foothold. If either side succeeded in winning this phase, an industrial ship would spawn to anchor a Stellar Observatory Structure. The two sides then had to help either defeat or protect this industrial ship. If the anchoring was successful the system then escalated towards the next phase, being either a Redoubt or First Liminality.


* At 76% towards either side winning the invasion escalated. More roaming fleets and sites appeared . The additional sites contained both class 1 and 2 sites. If the system bounced from one side to the other, this happened twice.
If no capsuleers interfered with the invasion, left the system untouched, and did nothing to help either side, the system will slowly move towards EDENCOM victory.
 
* At 76% towards either side winning the invasion escalated. More roaming fleets and sites appeared. The additional sites contained both class 1 and 2 sites. If the system bounced from one side to the other, this happened twice.
* At 96% towards Triglavian victory the Stellar Fleet Deployment site spawned. This site contained Dazh Liminality Locus and applied a system wide Triglavian effect. The roaming Triglavian rats also became more intense. One Major Conduit will also opened.
* At 96% towards Triglavian victory the Stellar Fleet Deployment site spawned. This site contained Dazh Liminality Locus and applied a system wide Triglavian effect. The roaming Triglavian rats also became more intense. One Major Conduit will also opened.


Line 147: Line 157:
=== Redoubt ===
=== Redoubt ===
[[File:Redoubt.png|thumb|right|Ingame UI showing the progress on a EDENCOM Redoubt.]]   
[[File:Redoubt.png|thumb|right|Ingame UI showing the progress on a EDENCOM Redoubt.]]   
''This system has been fortified by EDENCOM to the degree that is serves as a redoubt against Triglavian invasion operations. The Triglavian Collective will continue to strike against EDENCOM targets in this system''.
''This system has been fortified by EDENCOM to the degree that it serves as a redoubt against Triglavian invasion operations. The Triglavian Collective will continue to strike against EDENCOM targets in this system''.


When a Stellar Reconnaissance system is won by the EDENCOM side, it escalated into the Redoubt phase. Here EDENCOM has the upper hand, but the Triglavian side could still easily turn the tide. The system would experience a system-wide effect, as well as harder combat anomalies.


Should the EDENCOM forces achieve victory in this phase, it would further escalate into the Bulwark phase.
When a Stellar Reconnaissance system is won by the EDENCOM side, it escalated into the Redoubt phase. Here EDENCOM has the upper hand, but the Triglavian side could still easily turn the tide. The system would experience a system-wide effect, as well as greatly escalated roaming fleets, EDENCOM GunStars on stations, gates, and belts, and harder combat anomalies.


=== Bulwark ===
=== Bulwark ===
[[File:EDENCOM Bulwark.png|thumb|right|EDENCOM Bulwark progressing towards Fortress phase.]]
[[File:EDENCOM Bulwark.png|thumb|right|EDENCOM Bulwark progressing towards Fortress phase.]]
''This system has been fortified by EDENCOM to the degree that is serves as a formidable bulwark from which Triglavian invasion operations can be resisted. The Triglavian Collective will continue to strike against EDENCOM targets in this system''.
''This system has been fortified by EDENCOM to the degree that it serves as a formidable bulwark from which Triglavian invasion operations can be resisted. The Triglavian Collective will continue to strike against EDENCOM targets in this system''.


The invasion had not yet failed for the Triglavian and a concerted effort can manage to turn the tide, at the same time the EDENCOM forces have not yet won final victory and must remain vigilant. Should the EDENCOM forces manage to win this phase, a Triglavian Dreadnought will spawn which must be destroyed. When this is done the system is turned into a EDENCOM Fortress.
When the progress bar in a Redoubt system reached 75%, the system escalated to the Bulwark state. Roaming fleets escalated even further to contain multiple Elite-level ships, and an Observatory Flashpoint combat site spawned. At this level of escalation, it was possible for any non-Caldari system to push itself to EDENCOM Fortress state by virtue of the roaming EDENCOM NPC fleets outclassing the roaming Triglavian NPC fleets.
 
No EDENCOM Redoubt or Bulwhark was ever turned back and conquered by the Triglavian Collective; all systems that reached Redoubt eventually became EDENCOM Fortresses.


== EDENCOM Fortress - EDENCOM Victory ==
== EDENCOM Fortress - EDENCOM Victory ==
Line 172: Line 183:


Should the Triglavian forces manage to win a blue or yellow star system, the system moves from the Stellar Reconnaisanse phase to the Escalating Liminality phase.  
Should the Triglavian forces manage to win a blue or yellow star system, the system moves from the Stellar Reconnaisanse phase to the Escalating Liminality phase.  
Throughout the invasion, only one system was ever pulled from Escalating Liminality to an EDENCOM Fortress: Arshat. All 27 other systems which reached First Liminality eventually also reached Final Liminality.
<br>
<br>
This phase can further be divided up into two sub-phases:
This phase can further be divided up into two sub-phases:
=== First Liminality ===
=== First Liminality ===
[[File:First Liminality.png|thumb|right|First Liminality progress.]]
[[File:First Liminality.png|thumb|right|First Liminality progress.]]
''The presence of Triglavian structures and forces in this system has built up to the point that it constitute a serious danger to the future of the system. EDENCOM forces will continue to strike against Triglavian targets in this system''.
''The presence of Triglavian structures and forces in this system has built up to the point that it constitutes a serious danger to the future of the system. EDENCOM forces will continue to strike against Triglavian targets in this system''.


When a Stellar Reconnaissance system was won by the Triglavian Collective, it escalated into the First Liminality phase. Here the Triglavians had the upper hand, but the EDENCOM side could still easily turn the tide. The system experienced a system-wide effect, as well as harder combat anomalies and roaming fleets.
When a Stellar Reconnaissance system was won by the Triglavian Collective, it escalated into the First Liminality phase. Here the Triglavians had the upper hand, but the EDENCOM side could still turn the tide. The system gained a system-wide effect, as well as greatly escalated roaming fleets, Extractive Super-Nexii belts, Entropic Disintegrator Werposts on stations, gates, and belts, and Observatory Flashpoint combat sites.


Reaching the First Liminality phase reduced the security status of a system by an unknown amount and changed the system to work as low-sec.
Reaching the First Liminality phase also reduced the security status of a system by an unknown amount, and changed the system to work as low-sec.


=== Second Liminality ===
=== Second Liminality ===
Line 186: Line 199:
''The presence of Triglavian structures and forces in this system has built up to the point that it constitutes a major threat of Triglavian conquest of this system. EDENCOM forces will continue to strike against Triglavian targets in this system''.
''The presence of Triglavian structures and forces in this system has built up to the point that it constitutes a major threat of Triglavian conquest of this system. EDENCOM forces will continue to strike against Triglavian targets in this system''.


The First Liminality further escalated into the Second Liminality phase. In this phase, the Triglavian Collective is close to achieving final victory. EDENCOM must double their efforts or risk losing the system.
When the progress bar in First Liminality reached 75%, the system escalated to Second Liminality. Roaming fleets escalated even further to contain multiple Hospodar and Zorya-level ships, and the World Ark Assault Flashpoint combat site spawned. At this level of escalation, it was possible for the system to push itself to Final Liminality by virtue of the roaming Triglavian NPC fleets so severely outclassing the roaming EDENCOM NPC fleets.
 
Tougher combat anomalies and enemy ships will be present in this system.


== Final Liminality ==
== Final Liminality ==
Line 197: Line 208:


This means the system resembles [[System_security#Null_security|Nullsec]] regarding [[CONCORD]] Response (there is none), [[Security_status#Sentry_guns|Sentry guns]] (aggressors are not shot) and [[Security Status]] (no reduction for aggressors). All other limitations stay as dictated by the systems original security status:
This means the system resembles [[System_security#Null_security|Nullsec]] regarding [[CONCORD]] Response (there is none), [[Security_status#Sentry_guns|Sentry guns]] (aggressors are not shot) and [[Security Status]] (no reduction for aggressors). All other limitations stay as dictated by the systems original security status:
* no [[Jump_drives#Cynosural_Fields|cynos]], [[Capital ships]] taking gates into the system or [[Propulsion_equipment#Micro_Jump_Field_Generator|Micro Jump Field Generators]] (aka booshs) if the system was originally [[System_security#High_security|Hisec]]
* no [[Tackling#Warp_disruption_fields|Warp Disruption Fields]] (aka bubbles) or [[Bombs]] (not to be confused with [[Smartbombs]]) if the system was originally [[System_security#Low_security|Lowsec]] or [[System_security#High_security|Hisec]].
== Massive EDENCOM Fortification and Massive Triglavian Invasion ==
''EDENCOM has committed a massive effort to the defense and fortification of this system. The Triglavian Collective may probe this system but will not attempt to conquer it.''


- no [[Jump_drives#Cynosural_Fields|cynos]], [[Capital ships]] taking gates into the system or [[Propulsion_equipment#Micro_Jump_Field_Generator|Micro Jump Field Generators]] (aka booshs) if the system was originally [[System_security#High_security|Hisec]]
''The Triglavian Collective has committed a massive invasion force to the conquest of this system. EDENCOM is conducting a rearguard evacuation action but considers the system lost to the enemy.''


- no [[Tackling#Warp_disruption_fields|Warp Disruption Fields]] (aka bubbles) or [[Bombs]] (not to be confused with [[Smartbombs]]) if the system was originally [[System_security#Low_security|Lowsec]] or [[System_security#High_security|Hisec]].
Massive EDENCOM Fortification and Massive Triglavian Invasion is a special stage for a system that can occur. Rather than beginning at Stellar Reconnaissance, the system starts with either Massive EDENCOM Fortification or Massive Triglavian Invasion instead, and after several days, transforming into EDENCOM Fortress or Final Liminality system.
 
During Massive Fortification/Invasion the system would contain combat sites and large roaming fleets. Unlike Escalating Liminality, Massive Triglavian Invasion does not reduce the security status of a system, until the ultimate Final Liminality take place.
 
There are no progress bar or influence values for Massive Fortification/Invasion system, as a result players cannot interfere this progress.


== System-wide effects ==
== System-wide effects ==
As a system beganto lean towards either the EDENCOM or the Triglavian Collective, industrial ships for that faction appeared in the system. One of such industrial ships would attempt to put up a structure that applies a buff to all ships in the system.  
[[File:Dazh Liminality Locus System-wide Effect.png|right|thumb|Dazh Liminality Locus is in effect throughout the whole System.]]
[[File:Federal Stellar Observatory System-wide Effect.png|right|thumb|Federal Stellar Observatory is in effect throughout the whole System.]]
As EDENCOM or the Triglavian Collective gain greater control over the System, the winning side's Industrial ships will begin to appear in the System.
 
These Industrial ships will attempt to construct a Structure that applies effects to all ships within the System.


{| class="wikitable"
{| class="wikitable"
!Faction
!Faction
!Name
!Structure Name
!Buff 1
!Effect 1
!Buff 2
!Effect 2
!Buff 3
!Effect 3
!Buff 4
!Effect 4
|-
|-
!Triglavian
!Triglavian
|Dazh Liminality Locus
|Dazh Liminality Locus
|25% bonus to remote armor repair
|{{co|lightgreen|25%}} bonus to remote armor repair
|25% bonus to remote shield boost
|{{co|lightgreen|25%}} bonus to remote shield boost
|30% penalty to warp speed
|{{co|red|30%}} penalty to warp speed
|50% penalty to maximum locked targets
|{{co|red|50%}} penalty to maximum locked targets
|-
|-
!Amarr
!Amarr
|Imperial Stellar Observatory
|Imperial Stellar Observatory
|10% bonus to armor
|{{co|lightgreen|10%}} bonus to armor capacity
|10% bonus to energy warfare capacitor drain
|{{co|lightgreen|10%}} bonus to energy warfare capacitor drain
|10% bonus to mining speed
|{{co|lightgreen|10%}} bonus to mining speed
|None
|
|-
|-
!Caldari
!Caldari
|State Stellar Observatory
|State Stellar Observatory
|10% bonus to shield capacity
|{{co|lightgreen|10%}} bonus to shield capacity
|10% bonus to ECM range
|{{co|lightgreen|10%}} bonus to ECM range
|10% bonus to mining speed
|{{co|lightgreen|10%}} bonus to mining speed
|None
|
|-
|-
!Gallente
!Gallente
|Federal Stellar Observatory
|{{co|lightgreen|10%}} bonus to armor capacity
|{{co|lightgreen|+1}} bonus to warp scramble strength
|{{co|lightgreen|10%}} bonus to mining speed
|
|
|10% bonus to armor capacity
| +1 bonus to warp scramble strength
|10% bonus to mining speed
|None
|-
|-
!Minmatar
!Minmatar
|Republic Stellar Observatory
|{{co|lightgreen|10%}} bonus to shield capacity
|{{co|lightgreen|10%}} bonus to stasis webifier strength
|{{co|lightgreen|10%}} bonus to mining speed
|
|
|10% bonus to shield capacity
|10% bonus to stasis webifier strength
|10% bonus to mining speed
|None
|}
|}
== Massive EDENCOM fortification ==
The invasion event occured simultaneously on the [[Tranquility]] and [[Serenity]] servers (chinese EVE server). The progress between the two is synchronized by bringing EDENCOM victories from Serenity to Tranquility in form of Massive EDENCOM Fortifications.
A system that EDENCOM won on Serentiy would become a Massive EDENCOM Fortification on Tranquility. EDENCOM forces would partrol the system and only EDENCOM anomalies spawn. After a few days the system turned into a normal EDENCOM Fortress.
Massive Triglavian Invasion was another way to sync the servers. But since the Triglavians did not win a single system on Serenity{{verify}}, this state was not observed.


== Standings ==
== Standings ==
Line 262: Line 278:
Triglavian and EDENCOM sides both had standings towards capsuleers.
Triglavian and EDENCOM sides both had standings towards capsuleers.


Killing Triglavian rats would increase EDENCOM standing while reducing Triglavian standing by same amount. The same happened in reverse when EDENCOM rats are killed.<br>
Killing Triglavian rats would increase EDENCOM standing while reducing Triglavian standing by the same amount. The same happened in reverse when EDENCOM rats are killed.<br>
Triglavian and EDENCOM standings did not get benefits from any standing related skill.
Triglavian and EDENCOM standings did not get benefits from any standing related skill.


Line 272: Line 288:


Aggressing a rat, using remote assistance on a player who aggresses a rat or using remote assistance on a player who is aggressed by a rat caused rats of that side to become hostile regardless of player standings.
Aggressing a rat, using remote assistance on a player who aggresses a rat or using remote assistance on a player who is aggressed by a rat caused rats of that side to become hostile regardless of player standings.
== Synchronization between Tranquility and Serenity ==
For database management reasons, the invasion results on [[Tranquility]] and [[Serenity]] needed to match. Each server had their own separate lists of viable invasion target systems, so there could be no cross-server conflicts over system ownership.
In order to enforce system synchronization, any time a system on either server reached either EDENCOM Fortress or Final Liminality, its state propagated to the other server as either a Massive EDENCOM Fortification or a Massive Triglavian Invasion.
In Serenity, players of almost the entire server are fighting for EDENCOM, as a result, there are no Massive Triglavian Invasion ever triggered on Tranquility, and creating a large amount of EDENCOM Fortress via Massive EDENCOM Fortification everywhere in Tranquility.
On the other side, all Final Liminality systems on Serenity are created by Massive Triglavian Invasion, as they fall to Final Liminality in Tranquility.


== Permanent changes to New Eden ==
== Permanent changes to New Eden ==
Line 277: Line 302:
[[File:System Security Changes.png|thumb|right|The first system to reach the Escalating Liminality phase. Raravoss changed to effective low-sec during First and Secondary Liminality, dropping to effective null-sec once it reached final liminality.]]
[[File:System Security Changes.png|thumb|right|The first system to reach the Escalating Liminality phase. Raravoss changed to effective low-sec during First and Secondary Liminality, dropping to effective null-sec once it reached final liminality.]]


During the Invasion, CCP stated that, should the Triglavian Collective succeed in their invasion of a system, it would have direct impact on that system and would have lasting consequences in New Eden.   
During the Invasion, CCP stated that should the Triglavian Collective succeed in their invasion of a system, it would have a direct impact on that system and would have lasting consequences in New Eden.   


If a system reached the Escalating Liminality phase, it reduces the system security by an unknown amount. This changed a high-sec system to function as low-sec.
If a system reached the Escalating Liminality phase, it reduces the system security by an unknown amount. This changed a high-sec system to function as low-sec.


When a system reached the Final Liminality phase, the system was abandoned by CONCORD and EDENCOM, and functioned as an empire null-sec system. This meant no CONCORD response, but also no cyno or warp bubbles.
When a system reached the Final Liminality phase, the system was abandoned by CONCORD and EDENCOM and functioned as an empire null-sec system. This meant no CONCORD response, but also no cyno or warp bubbles.


On August 18th, 2020, the Triglavian Collective and supporting capsuleers captured pushed the system of Niarja into Final Liminality, severing the "ring" of high-sec [[Topology]], and taking the two largest trade hubs, Jita and Amarr, from 10 jumps apart to 45.
On August 18th, 2020, the Triglavian Collective and supporting capsuleers captured pushed the system of Niarja into Final Liminality, severing the "ring" of high-sec [[Topology]], and taking the two largest trade hubs, Jita and Amarr, from 10 jumps apart to 45.


On October 13th, 2020, following a week of gate energy fluctutations and a day of gate network disruptions, all 27 Final Liminality systems had their gate connections severed, and linked together under a new region of Pochven. All stations were commandeered by the Triglavians, and their original agents removed. Station services and gate traversal require various levels of standing with the Triglavians, rewarding those who helped push the systems into their control. Access to and from the region was introduced through wormholes and special filaments.
On October 13th, 2020, following a week of gate energy fluctuations and a day of gate network disruptions, all 27 Final Liminality systems had their gate connections severed, and linked together under a new region of Pochven. All stations were commandeered by the Triglavians, and their original agents removed. Station services and gate traversal require various levels of standing with the Triglavians, rewarding those who helped push the systems into their control. Access to and from the region was introduced through wormholes and special filaments.


== Rewards ==
== Rewards ==
Line 296: Line 321:
** Empire rats drop a stack of 1k faction ammo, random meta modules and salvage into T2 salvage.
** Empire rats drop a stack of 1k faction ammo, random meta modules and salvage into T2 salvage.


Figthing for the EDENCOM forces would reward the capsuleer with ISK and DED loyalty points when a combat anomaly is cleared. Figthing for the Triglavian Collective gave slightly more ISK, but no loyalty points. Both gave a small standing increase with their faction and a standing decrease with the opposing. The standing gain depended on the invasion stage and site. In the reconnaissance phase, standings moved by 0.01% per anomaly, while in First Liminality the standing moved by 0.24% per observatory flashpoint.
Figthing for the EDENCOM forces would reward the capsuleer with ISK and DED loyalty points when a combat anomaly is cleared. Fighting for the Triglavian Collective gave slightly more ISK, but no loyalty points. Both gave a small standing increase with their faction and a standing decrease with the opposing. The standing gain depended on the invasion stage and site. In the reconnaissance phase, standings moved by 0.01% per anomaly, while in First Liminality the standing moved by 0.24% per observatory flashpoint.


== External links ==
== External links ==
* [https://support.eveonline.com/hc/en-us/articles/360005796699-Triglavian-Invasion Helpdesk Article: Triglavian Invasion]
* [https://support.eveonline.com/hc/en-us/articles/360005796699-Triglavian-Invasion Helpdesk Article: Triglavian Invasion]
* [https://www.eveonline.com/article/qaxqky/invasion-chapter-3-now-live Invasion Chapter 3 introduction]
* [https://www.eveonline.com/news/view/invasion-chapter-3-now-live Invasion Chapter 3 introduction]
* [https://support.eveonline.com/hc/en-us/articles/360013963260-Effective-security-response-with-heightened-Triglavian-presence- Effective Security Response with hightened Triglavian presence.]
* [https://support.eveonline.com/hc/en-us/articles/360013963260-Effective-security-response-with-heightened-Triglavian-presence- Effective Security Response with heightened Triglavian presence.]
* [https://www.youtube.com/watch?v=BzFe0a0gx1E The Scope on The Fall of Raravoss]
* [https://www.youtube.com/watch?v=BzFe0a0gx1E The Scope on The Fall of Raravoss]
* [https://www.youtube.com/watch?v=H5WkXGdmM_s Reload on the Liminality changes]
* [https://www.youtube.com/watch?v=H5WkXGdmM_s Reload on the Liminality changes]