Difference between revisions of "Triglavian Invasion (Chapter 3)"
Ramong Pares (talk | contribs) |
Salartarium (talk | contribs) m (proofreading, link maintenance) |
||
(60 intermediate revisions by 15 users not shown) | |||
Line 1: | Line 1: | ||
− | {{ | + | {{Past content}} |
+ | {{Triglavian links}} | ||
+ | [[File:Invasion_Ch3_Keyart.jpg|400px|thumb|right|Chapter 3 keyart]] | ||
− | The 3rd and final chapter of the Triglavian | + | 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. |
− | Triglavian Invasions | + | 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. |
− | The invaded systems | + | The invaded systems had roaming fleets of EDENCOM and Triglavian ships trying to establish superiority. These ships were present on gates, stations, in asteroid belts and in safe spots in space. They were also present in a number of [[Triglavian Invasion combat sites|Triglavian invasion combat anomalies]] only present in the invaded systems. Systems could be secured for either EDENCOM or the Triglavian Collective through fighting the opposite faction. |
− | + | The Triglavian Collective's goals were initially unknown. Systems with blue or certain yellow stars captured by the Triglavians were abandoned by CONCORD, and had large [[Triglavian Invasion special NPCs#Triglavian Transmuters|Triglavian Porevitium Transmuter]] installed around the star, transmuting them to a dark red color. Towards the end of the Invasion, said stars also started exhibiting [[Wormhole]]-esque animations. | |
− | [[ | + | Chapter 3 concluded on October 13th, 2020, with the 27 Final Liminality systems captured by the Triglavians torn from the regular gate network and reformed together as the region of [[Pochven]]. The Invasion tab was subsequently removed from [[The Agency]] and replaced with a link to the [[Corporation]] dashboard. As of October 13th, former Minor Victory systems maintain EDENCOM or Triglavian presence as they did during the Invasion, but are not marked on the route planner or in system. |
+ | == Introduction == | ||
− | + | [[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. | |
− | + | The invasion took place in High-Sec and Low-Sec Empire space, with systems undergoing invasion experiencing a temporary disruption. | |
− | + | To help either side, capsuleers had to engage and destroy either the Triglavian NPCs or the EDENCOM NPCs. These could be found primarily in [[Triglavian Invasion combat sites|combat anomalies]] or in safespots that had to be scanned down. They could also be found on stargates, in asteroid belts and at stations. | |
+ | As players managed to help either the Triglavian Collective or EDENCOM get the upper hand, they could move the system towards either EDENCOM or Triglavian victory, with the invasion in that system entering a new phase. This was done until either EDENCOM achieved final victory with the 'EDENCOM Fortress' phase or the Triglavians took over the system in the 'Final Liminality' phase. | ||
It can as such essentially be seen as a tug-of-war between the opposing sides: | It can as such essentially be seen as a tug-of-war between the opposing sides: | ||
Final Liminality <-- Escalating Liminality <-- Stellar Reconnaissance --> Redoubts & Bulwarks --> EDENCOM Fortress | Final Liminality <-- Escalating Liminality <-- Stellar Reconnaissance --> Redoubts & Bulwarks --> EDENCOM Fortress | ||
+ | |||
+ | Both EDENCOM and Triglavian ships could appear in cosmic signatures, caution was recommended if doing exploration in an invaded system. | ||
+ | |||
+ | |||
+ | ==== Minor Victories ==== | ||
+ | |||
+ | For systems without blue or yellow stars, player influence could only push the system into a Minor Victory status for EDENCOM or the Triglavians. At either victory stage, the system would no longer appear in The Agency, but would still impart system-wide effects based on the victor's observatory or locus. For these systems, the tug-of-war is instead: | ||
+ | |||
+ | Triglavian Minor Victory <-- Stellar Reconnaissance --> EDENCOM Minor Victory | ||
+ | |||
+ | 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, 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 | + | Forces for the Triglavian Collective and the EDENCOM could be found throughout systems undergoing invasion. |
− | *For | + | *For an overview of NPCs and structures special to the Triglavian Invasion, [[Triglavian Invasion special NPCs|look here]]. |
− | *For | + | *For an overview of the combat sites in these systems, [[Triglavian Invasion combat sites|look here]]. |
=== Triglavian NPCs === | === Triglavian NPCs === | ||
− | The Triglavian Collective ships | + | 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 | + | Triglavian NPCs in the Triglavian Invasion systems come in three tiers: |
{| class="wikitable" | {| class="wikitable" | ||
! | ! | ||
Line 54: | Line 80: | ||
|Raznaborg <role> <ship type> | |Raznaborg <role> <ship type> | ||
|No prefix <role> <ship type> | |No prefix <role> <ship type> | ||
− | | | + | |Hospodar <role> <ship type> |
|Zorya <ship type> | |Zorya <ship type> | ||
|} | |} | ||
− | They follow the traditional Triglavian naming scheme, with their secondary | + | They follow the traditional Triglavian naming scheme, with their secondary prefix defining their role: |
* Anchoring - Warp scrambling | * Anchoring - Warp scrambling | ||
* Tangling - Stasis webifying | * Tangling - Stasis webifying | ||
Line 68: | Line 94: | ||
* Blinding - Sensor dampening | * Blinding - Sensor dampening | ||
− | + | There also existed "Raznaborg <ship type>" with no secondary prefix. These ships had the abilities of Raznaborg Liminal <ship type>s. | |
+ | With the three tiers, many hull-sizes and ewar-types, the Triglavian forces found could come in many variations. | ||
=== EDENCOM NPCs === | === EDENCOM NPCs === | ||
− | The EDENCOM forces found and fought | + | 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 94: | 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> |
|} | |} | ||
− | As either the Triglavian or EDENCOM | + | As either the Triglavian or EDENCOM progressed towards the next phase, other sites such as the Minor Conduits and Stellar Fleet Deployment Sites appeared. |
== Stellar Reconnaissance - First Phase == | == Stellar Reconnaissance - First Phase == | ||
Line 118: | Line 145: | ||
''Scouting forces belonging to both EDENCOM and the Triglavian Collective are conducting recon operations focused on the central star of this system but roaming widely across the system. Both sides are seeking to establish stellar observatory structures''. | ''Scouting forces belonging to both EDENCOM and the Triglavian Collective are conducting recon operations focused on the central star of this system but roaming widely across the system. Both sides are seeking to establish stellar observatory structures''. | ||
− | The Stellar Reconnaissance | + | 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 | + | 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. |
− | + | 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. | ||
== Redoubts & Bulwarks - Towards EDENCOM Victory == | == Redoubts & Bulwarks - Towards EDENCOM Victory == | ||
− | Should the EDENCOM forces manage to win the opening phase of a Triglavian invasion, it | + | Should the EDENCOM forces manage to win the opening phase of a Triglavian invasion, it moved the system to the Redoubt & Bulwarks phase. Like the Escalating Liminality phase, this could further be divided up into two phases: |
=== 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 | + | ''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 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 | + | ''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''. |
− | + | 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 == | ||
[[File:EDENCOM Fortress.png|thumb|right|The ingame UI for the EDENCOM Fortress]] | [[File:EDENCOM Fortress.png|thumb|right|The ingame UI for the EDENCOM Fortress]] | ||
− | ''This system has been fortified by EDENCOM to the point that it is now an unbreakable fortress that the Triglavians will find far | + | ''This system has been fortified by EDENCOM to the point that it is now an unbreakable fortress that the Triglavians will find far too hard a target to conquer. Ongoing Triglavian invasion efforts will move to more vulnerable targets.'' |
− | When the EDENCOM forces manage to exert complete control over a bulwark system it changes it to | + | When the EDENCOM forces manage to exert complete control over a bulwark system it changes it to an EDENCOM Fortress. In this phase the Triglavian Collective deemed the system too hard to conquer and moved their invasion efforts to other systems. |
− | + | Upon reaching this phase, the EDENCOM side achieved a complete and final victory over the system. | |
+ | EDENCOM fortress systems do not spawn any invasion sites or Triglavian rats. One fleet of EDENCOM rats will roam the system. | ||
== Escalating Liminality - Towards Triglavian Victory == | == Escalating Liminality - Towards Triglavian Victory == | ||
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 | + | ''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 | + | 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 | + | 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 166: | 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''. | ||
− | + | 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. | |
− | |||
− | |||
== Final Liminality == | == Final Liminality == | ||
Line 174: | Line 205: | ||
''The Triglavian stellar harvesting and manipulation efforts have reached their peak, and the Triglavian Collective has conquered the system. EDENCOM considers this system lost to the Triglavian Collective and will redeploy defensive efforts to systems that can still be saved.'' | ''The Triglavian stellar harvesting and manipulation efforts have reached their peak, and the Triglavian Collective has conquered the system. EDENCOM considers this system lost to the Triglavian Collective and will redeploy defensive efforts to systems that can still be saved.'' | ||
− | When the Triglavian forces | + | When the Triglavian forces have managed to push a system through the First and Second Liminality phases, it escalated into the Final Liminality phase. This was a complete victory for the Triglavian forces in the system and was irreversible. The Triglavian [[Triglavian Invasion special NPCs#Triglavian Transmuters|stellar manipulator]] continued, but was also joined by Triglavian mining operations in the system. EDENCOM and CONCORD have abandoned the system and it effectively works as a null-security system. |
+ | |||
+ | 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.'' | ||
+ | |||
+ | ''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.'' | ||
+ | |||
+ | 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 | + | [[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 |
− | ! | + | !Effect 1 |
− | ! | + | !Effect 2 |
− | ! | + | !Effect 3 |
− | ! | + | !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 |
− | | | + | | |
|- | |- | ||
!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 |
− | | | + | | |
|- | |- | ||
!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 |
| | | | ||
|- | |- | ||
!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 |
| | | | ||
|} | |} | ||
+ | |||
+ | == Standings == | ||
+ | {{Note|During the Invasion, shooting the opposite faction was the only way to gain standings. Since the Invasion, derived standings with [[Rogue Drones]] and [[Drifters]] were introduced, benefiting both factions.}} | ||
+ | |||
+ | Triglavian and EDENCOM sides both had standings towards capsuleers. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | * At 0.00 and below Triglavian rats were hostile. | ||
+ | * At below 0.00 EDENCOM rats were hostile. | ||
+ | * At +5.00 and above the rats started supporting players by remote repairing them. | ||
+ | |||
+ | There was a very small range of standings which made both factions neutral. Initially a range of -2.0 to <0.0 standings with the Triglavian Collective, it was later reduced to a very tiny window. The exact values are not known, but it appeared that if your EDENCOM standing is around -0.001 and Triglavian standing is around 0.001, both sides were neutral. Whether this was working as intended is uncertain. | ||
+ | |||
+ | 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 == | ||
− | [[File:System Security Changes.png|thumb|right|The first system to reach the Escalating Liminality phase. Raravoss changed to | + | {{Main|Pochven}} |
+ | [[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 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. | ||
− | + | 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 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 == | ||
The rewards can be divided up into two categories: | The rewards can be divided up into two categories: | ||
− | * Advancing or repulsing the Triglavian | + | * Advancing or repulsing the Triglavian Collective's goals. |
* ISK reward for clearing the sites, DED loyalty points for clearing the sites, loot and salvage from the ships destroyed, standings with either side. | * ISK reward for clearing the sites, DED loyalty points for clearing the sites, loot and salvage from the ships destroyed, standings with either side. | ||
− | * | + | * Zirnitra Blueprint Data Vault |
− | ** | + | ** Zirnitra BPCs |
* Salvage and module drops from killed rats. | * Salvage and module drops from killed rats. | ||
** 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 | + | 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/ | + | * [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 | + | * [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=H5WkXGdmM_s Reload on the Liminality changes] | * [https://www.youtube.com/watch?v=H5WkXGdmM_s Reload on the Liminality changes] | ||
+ | * [https://docs.google.com/spreadsheets/d/1Nj_SlLzc8Rz4iW7iSqZ4ZZMgr1w0FkOYb3SS-BwQVSA/ Chapter 3 Invasion info spreadsheet by Neugeniko] | ||
+ | * [https://kybernaut.space/guide Kybernaut guide] | ||
+ | * [https://docs.google.com/document/d/1k6fDaxtfSUw4STVXavw4M-IXIODozVzAA1n0gFQzrUk/edit?usp=drivesdk EDENCOM Defense Initiative guide] | ||
[[Category:PvE]] | [[Category:PvE]] |
Latest revision as of 08:02, 28 August 2023
Triglavian links |
Triglavian Collective |
---|
Triglavian collective |
Past operations |
The 3rd and final chapter of the Triglavian Invasion was introduced on May 26th. 2020. It was a continuation of 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.
The invaded systems had roaming fleets of EDENCOM and Triglavian ships trying to establish superiority. These ships were present on gates, stations, in asteroid belts and in safe spots in space. They were also present in a number of Triglavian invasion combat anomalies only present in the invaded systems. Systems could be secured for either EDENCOM or the Triglavian Collective through fighting the opposite faction.
The Triglavian Collective's goals were initially unknown. Systems with blue or certain yellow stars captured by the Triglavians were abandoned by CONCORD, and had large Triglavian Porevitium Transmuter installed around the star, transmuting them to a dark red color. Towards the end of the Invasion, said stars also started exhibiting Wormhole-esque animations.
Chapter 3 concluded on October 13th, 2020, with the 27 Final Liminality systems captured by the Triglavians torn from the regular gate network and reformed together as the region of Pochven. The Invasion tab was subsequently removed from The Agency and replaced with a link to the Corporation dashboard. As of October 13th, former Minor Victory systems maintain EDENCOM or Triglavian presence as they did during the Invasion, but are not marked on the route planner or in system.
Introduction
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.
To help either side, capsuleers had to engage and destroy either the Triglavian NPCs or the EDENCOM NPCs. These could be found primarily in combat anomalies or in safespots that had to be scanned down. They could also be found on stargates, in asteroid belts and at stations.
As players managed to help either the Triglavian Collective or EDENCOM get the upper hand, they could move the system towards either EDENCOM or Triglavian victory, with the invasion in that system entering a new phase. This was done until either EDENCOM achieved final victory with the 'EDENCOM Fortress' phase or the Triglavians took over the system in the 'Final Liminality' phase.
It can as such essentially be seen as a tug-of-war between the opposing sides:
Final Liminality <-- Escalating Liminality <-- Stellar Reconnaissance --> Redoubts & Bulwarks --> EDENCOM Fortress
Both EDENCOM and Triglavian ships could appear in cosmic signatures, caution was recommended if doing exploration in an invaded system.
Minor Victories
For systems without blue or yellow stars, player influence could only push the system into a Minor Victory status for EDENCOM or the Triglavians. At either victory stage, the system would no longer appear in The Agency, but would still impart system-wide effects based on the victor's observatory or locus. For these systems, the tug-of-war is instead:
Triglavian Minor Victory <-- Stellar Reconnaissance --> EDENCOM Minor Victory
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, 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
Forces for the Triglavian Collective and the EDENCOM could be found throughout systems undergoing invasion.
- For an overview of NPCs and structures special to the Triglavian Invasion, look here.
- For an overview of the combat sites in these systems, look here.
Triglavian NPCs
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 come in three tiers:
Weakest | Weaker | Stronger | Strongest | |
---|---|---|---|---|
Scout | Normal | Elite | Officer | |
Triglavian | Raznaborg <role> <ship type> | No prefix <role> <ship type> | Hospodar <role> <ship type> | Zorya <ship type> |
They follow the traditional Triglavian naming scheme, with their secondary prefix defining their role:
- Anchoring - Warp scrambling
- Tangling - Stasis webifying
- Starving - Energy neutralizing
- Ghosting - Tracking/guidance disruption
- Renewing - Stronger remote repairs, lower DPS
- Liminal - Additional high-damage EM/Kinetic missile attack. These missiles are more powerful than their disintegrators, and mean that invasions deal omni damage.
- Harrowing - Target painting
- Blinding - Sensor dampening
There also existed "Raznaborg <ship type>" with no secondary prefix. These ships had the abilities of Raznaborg Liminal <ship type>s.
With the three tiers, many hull-sizes and ewar-types, the Triglavian forces found could come in many variations.
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 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).
Weakest | Weaker | Stronger | Strongest | |
---|---|---|---|---|
Scout | Normal | Elite | Officer | |
Amarr | Scout Imperial Navy <ship type> | Imperial Navy <ship type> | Elite Imperial Navy <ship type> | Exalted Imperial Navy <ship type> |
Caldari | Scout State Navy <ship type> | State Navy <ship type> | Elite State Navy <ship type> | Executive State Navy <ship type> |
Gallente | Scout Federal Navy <ship type> | Federal Navy <ship type> | Elite Federal Navy <ship type> | Presiding Federal Navy <ship type> |
Minmatar | Scout Republic Fleet <ship type> | Republic Fleet <ship type> | Elite Republic Fleet <ship type> | Chief Republic Fleet <ship type> |
As either the Triglavian or EDENCOM progressed towards the next phase, other sites such as the Minor Conduits and Stellar Fleet Deployment Sites appeared.
Stellar Reconnaissance - First Phase
Scouting forces belonging to both EDENCOM and the Triglavian Collective are conducting recon operations focused on the central star of this system but roaming widely across the system. Both sides are seeking to establish stellar observatory structures.
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.
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.
Redoubts & Bulwarks - Towards EDENCOM Victory
Should the EDENCOM forces manage to win the opening phase of a Triglavian invasion, it moved the system to the Redoubt & Bulwarks phase. Like the Escalating Liminality phase, this could further be divided up into two phases:
Redoubt
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 greatly escalated roaming fleets, EDENCOM GunStars on stations, gates, and belts, and harder combat anomalies.
Bulwark
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.
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
This system has been fortified by EDENCOM to the point that it is now an unbreakable fortress that the Triglavians will find far too hard a target to conquer. Ongoing Triglavian invasion efforts will move to more vulnerable targets.
When the EDENCOM forces manage to exert complete control over a bulwark system it changes it to an EDENCOM Fortress. In this phase the Triglavian Collective deemed the system too hard to conquer and moved their invasion efforts to other systems.
Upon reaching this phase, the EDENCOM side achieved a complete and final victory over the system.
EDENCOM fortress systems do not spawn any invasion sites or Triglavian rats. One fleet of EDENCOM rats will roam the system.
Escalating Liminality - Towards Triglavian Victory
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.
This phase can further be divided up into two sub-phases:
First Liminality
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 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 also reduced the security status of a system by an unknown amount, and changed the system to work as low-sec.
Second Liminality
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.
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.
Final Liminality
The Triglavian stellar harvesting and manipulation efforts have reached their peak, and the Triglavian Collective has conquered the system. EDENCOM considers this system lost to the Triglavian Collective and will redeploy defensive efforts to systems that can still be saved.
When the Triglavian forces have managed to push a system through the First and Second Liminality phases, it escalated into the Final Liminality phase. This was a complete victory for the Triglavian forces in the system and was irreversible. The Triglavian stellar manipulator continued, but was also joined by Triglavian mining operations in the system. EDENCOM and CONCORD have abandoned the system and it effectively works as a null-security system.
This means the system resembles Nullsec regarding CONCORD Response (there is none), 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 cynos, Capital ships taking gates into the system or Micro Jump Field Generators (aka booshs) if the system was originally Hisec
- no Warp Disruption Fields (aka bubbles) or Bombs (not to be confused with Smartbombs) if the system was originally Lowsec or 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.
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.
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
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.
Faction | Structure Name | Effect 1 | Effect 2 | Effect 3 | Effect 4 |
---|---|---|---|---|---|
Triglavian | Dazh Liminality Locus | 25% bonus to remote armor repair | 25% bonus to remote shield boost | 30% penalty to warp speed | 50% penalty to maximum locked targets |
Amarr | Imperial Stellar Observatory | 10% bonus to armor capacity | 10% bonus to energy warfare capacitor drain | 10% bonus to mining speed | |
Caldari | State Stellar Observatory | 10% bonus to shield capacity | 10% bonus to ECM range | 10% bonus to mining speed | |
Gallente | Federal Stellar Observatory | 10% bonus to armor capacity | +1 bonus to warp scramble strength | 10% bonus to mining speed | |
Minmatar | Republic Stellar Observatory | 10% bonus to shield capacity | 10% bonus to stasis webifier strength | 10% bonus to mining speed |
Standings
Note: | During the Invasion, shooting the opposite faction was the only way to gain standings. Since the Invasion, derived standings with Rogue Drones and Drifters were introduced, benefiting both factions. |
Triglavian and EDENCOM sides both had standings towards capsuleers.
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.
Triglavian and EDENCOM standings did not get benefits from any standing related skill.
- At 0.00 and below Triglavian rats were hostile.
- At below 0.00 EDENCOM rats were hostile.
- At +5.00 and above the rats started supporting players by remote repairing them.
There was a very small range of standings which made both factions neutral. Initially a range of -2.0 to <0.0 standings with the Triglavian Collective, it was later reduced to a very tiny window. The exact values are not known, but it appeared that if your EDENCOM standing is around -0.001 and Triglavian standing is around 0.001, both sides were neutral. Whether this was working as intended is uncertain.
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
- Main article: Pochven
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.
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 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
The rewards can be divided up into two categories:
- Advancing or repulsing the Triglavian Collective's goals.
- ISK reward for clearing the sites, DED loyalty points for clearing the sites, loot and salvage from the ships destroyed, standings with either side.
- Zirnitra Blueprint Data Vault
- Zirnitra BPCs
- Salvage and module drops from killed rats.
- 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. 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.